Update error

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
User avatar
xendistar
Posts: 510
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Update error

Postby xendistar » 06 Apr 2019 21:20

Running SolydX EE

Did my normal

Code: Select all

$ sudo apt-get update && sudo apt-get dist-upgrade 
to night

41 packages to update 7 were just your normal file update the remainder were LibreOffice updates, looks like they are moving to version 1:6.1.5-2. ( I have attached a full txt file of the full process and all the errors)

The 7 odd files seem to unpack ok but when it started the unpacking the Libre offices I got the following (this is just a couple of lines of the error)

Code: Select all

Unpacking libreoffice-help-common (1:6.1.5-2) over (1:6.1.5-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-bb46wl/19-libreoffice-help-common_1%3a6.1.5-2_all.deb (--unpack):
 unable to securely remove '/usr/share/libreoffice/help/media/icon-themes/svx/res/marker-rect13-4.png.dpkg-tmp': Read-only file system
Preparing to unpack .../20-libreoffice-style-tango_1%3a6.1.5-2_all.deb ...
Unpacking libreoffice-style-tango (1:6.1.5-2) over (1:6.1.5-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-bb46wl/20-libreoffice-style-tango_1%3a6.1.5-2_all.deb (--unpack):
 unable to create '/usr/share/bug/libreoffice-style-tango/presubj.dpkg-new' (while processing './usr/share/bug/libreoffice-style-tango/presubj'): Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/usr/share/bug/libreoffice-style-tango/presubj': Read-only file system
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
It looks as though nothing was installed as further down I got the following:

Code: Select all

Preparing to unpack .../39-python-sip_4.19.14+dfsg-2_amd64.deb ...
E: pyclean:64: cannot remove /usr/lib/python2.7/dist-packages/sipconfig_nd.pyc
E: pyclean:64: cannot remove /usr/lib/python2.7/dist-packages/sipconfig.pyc
Unpacking python-sip (4.19.14+dfsg-2) over (4.19.14+dfsg-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-bb46wl/39-python-sip_4.19.14+dfsg-2_amd64.deb (--unpack):
 unable to create '/usr/lib/python2.7/dist-packages/sip.pyi.dpkg-new' (while processing './usr/lib/python2.7/dist-packages/sip.pyi'): Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/usr/lib/python2.7/dist-packages/sip.pyi': Read-only file system
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Has anybody else had this issue, LibreOffice is running OK on my PC

update-error.txt
(25 KiB) Downloaded 14 times

User avatar
grizzler
Posts: 2171
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Update error

Postby grizzler » 07 Apr 2019 06:35

Not seeing anything like that here. The entire update went without a hitch.

I notice 'Read only file system' in your error messages. Could the drive have developed some kind of fault? Or a mount error?
Frank

SolydX EE 64 - tracking Debian Testing

User avatar
xendistar
Posts: 510
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: Update error

Postby xendistar » 07 Apr 2019 10:11

This is becoming a bit strange, came to my PC this morning, completely black unresponsive, pc box lights were as was the monitor lights but that was it.

Ended up pressing the reset switch on the PC, PC rebooted and came up with file system errors telling me to run fsck manually, which I did. FSCK came up with a host of issue which were fixed and then the PC rebooted and I logged in OK.

I checked the S.M.A.R.T. for the hard disk (SSD in this case) and ran two extended tests on the two partition (root and home) and both came back ok.

Saw Grizzler's reply so I thought I would run the update again, here is the output (sorry a bit large)

Code: Select all

mit@andora:~$ sudo apt-get update && sudo apt-get dist-upgrade
[sudo] password for mit: 
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://security.debian.org testing/updates InRelease                                         
Get:3 http://ftp.uk.debian.org/debian testing InRelease [158 kB]                                   
Hit:4 http://dl.google.com/linux/chrome/deb stable Release                                         
Hit:5 https://deb.opera.com/opera-stable stable InRelease                                          
Hit:6 https://repository.solydxk.com solydxk-ee InRelease                                          
Fetched 158 kB in 1s (218 kB/s)                          
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  dconf-cli python-matplotlib-data python3-cycler python3-gst-1.0 python3-kiwisolver
  python3-matplotlib python3-numpy python3-pyparsing python3-xdg
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  cron libmysofa0 libxml-twig-perl
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 316 kB/2,957 kB of archives.
After this operation, 13.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.uk.debian.org/debian testing/main amd64 cron amd64 3.0pl1-133 [98.7 kB]
Get:2 http://ftp.uk.debian.org/debian testing/main amd64 libmysofa0 amd64 0.6~dfsg0-3 [38.0 kB]
Get:3 http://ftp.uk.debian.org/debian testing/main amd64 libxml-twig-perl all 1:3.50-1.1 [179 kB]
Fetched 316 kB in 0s (1,936 kB/s)         
(Reading database ... 341193 files and directories currently installed.)
Preparing to unpack .../cron_3.0pl1-133_amd64.deb ...
Unpacking cron (3.0pl1-133) over (3.0pl1-132) ...
Preparing to unpack .../libmysofa0_0.6~dfsg0-3_amd64.deb ...
Unpacking libmysofa0:amd64 (0.6~dfsg0-3) over (0.6~dfsg0-2) ...
Preparing to unpack .../libxml-twig-perl_1%3a3.50-1.1_all.deb ...
Unpacking libxml-twig-perl (1:3.50-1.1) over (1:3.50-1) ...
Setting up cron (3.0pl1-133) ...
Setting up libxml-twig-perl (1:3.50-1.1) ...
Setting up libmysofa0:amd64 (0.6~dfsg0-3) ...
dpkg: error processing package libreoffice-help-common (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
dpkg: dependency problems prevent configuration of libreoffice-help-en-gb:
 libreoffice-help-en-gb depends on libreoffice-help-common (= 1:6.1.5-2); however:
  Package libreoffice-help-common is not configured yet.

dpkg: error processing package libreoffice-help-en-gb (--configure):
 dependency problems - leaving unconfigured
Processing triggers for systemd (241-1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-8) ...
Errors were encountered while processing:
 libreoffice-help-common
 libreoffice-help-en-gb
E: Sub-process /usr/bin/dpkg returned an error code (1)
So all of the Libreoffice updates (with the exception of the two noted files) was installed OK last night, I also checked Libreoffice and it states its version as 6.1.5-2 (build 1:6.1.5-2).

I individually reinstalled the two libreoffice files with no issue, so I am not quite sure what went wrong last night, the PC was operating OK up until I went to bed and it was dead this morning. Seems to operating perfectly at the moment. I will continue to keep an eye on the SSD just encase but other than that I am not sure what went wrong.

User avatar
Arjen Balfoort
Site Admin
Posts: 9282
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Update error

Postby Arjen Balfoort » 07 Apr 2019 10:13

Yes, I think grizzler is right.

You could try to boot a live ISO and check the root partition with GParted.


SolydXK needs you!
Development | Testing | Translations

User avatar
xendistar
Posts: 510
Joined: 08 Jun 2014 08:17
Location: Bournemouth, UK

Re: Update error

Postby xendistar » 07 Apr 2019 15:36

Cheers Guys, Well I rebooted the PC to an install disk and ran a check on my boot, root and home partitions and gparted did not find anything wrong, so I am not sure what happened.

I guess the install could of gone a bit wayward for some reason hence the messages after the install and then completely locked up overnight. Everything seem to be OK at present, I will keep watching things and hopefully it will not happen again.


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 4 guests