Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  To du or not to du?  (Read 4871 times)

Offline GoinEasy9

  • User
  • Posts: 560
To du or not to du?
« on: 2014/08/28, 04:24:44 »
The last few days have seen quite a few problems.  I'm still getting the:
keys on reference is experimental at /usr/bin/apt-show-versions line 264.     
keys on reference is experimental at /usr/bin/apt-show-versions line 359 error.  I know there's a patch, but I stopped du'ing when this first appeared.  Not just because of this error, but because of the number of problems I see posted to upgrade warnings.

I've been waiting for the go ahead from santa concerning the kde 4.14 transition, specifically the kdepim problem, but, I still get the feeling 4.14 still has problems.  Usually, santa will post when things are safe, but I haven't seen him give the ok.

Right now I I have 366 to be upgraded, 32 newly installed and 1 to remove if I du, and, tonight I see dibl reported a problem with pulseaudio.  So, I'm holding off another day.  I'm hoping someone will post a "safe to du" statement.  Going through all the posts in upgrade warnings, I get the feeling that waiting is the prudent thing to do. 
Linux Counter number 348347

Offline Jörg

  • User
  • Posts: 95
Re: To du or not to du?
« Reply #1 on: 2014/08/28, 10:40:20 »
Did a DU (with comparable amount of newly installed and 2 removed packages) about 2 hours ago. After an "apt-get -f install" everything works fine!

Greetings,
Jörg

Offline rueX

  • User
  • Posts: 135
Re: To du or not to du?
« Reply #2 on: 2014/08/28, 11:32:07 »
Last d-u  15min. ago - 32-bit - works fine

Last 7 days and nights
i had much doubts about my hardware, ram etc.
no clue what happened - freece, reboot, flashes, iceweasel....you read it in Upgrade Warnings...

But: Best title ever posted ! to be or not to be ..great idioms for my private dictionary  ;)
..ein wirklich leidgeplagter Titel...mit Augenzwinkern.

+1

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye
Re: To du or not to du?
« Reply #3 on: 2014/08/28, 14:01:46 »
I just finished running d-u on three 64-bit KDE systems and one 32-bit LXDE system.  As far as I can tell from a quick check, they are all working as expected, including X and audio.  The KDE systems seem to need a reboot after the 4.14 upgrade.  The one I had the pulseaudio problem with last night had an uptime of 8 days.  After running another d-u this morning and rebooting it, I don't see any issues.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline GoinEasy9

  • User
  • Posts: 560
Re: To du or not to du?
« Reply #4 on: 2014/08/28, 16:40:35 »
Thanks for all the responses.  I will now dive in to a du.

Edit:  It took awhile, but du completed successfully, and, it seems everything is working.  Thanks again.
« Last Edit: 2014/08/28, 17:29:57 by GoinEasy9 »
Linux Counter number 348347

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye
Re: To du or not to du?
« Reply #5 on: 2014/08/28, 23:08:27 »
The /run/user/1000/pulse permissions issue has recurred on my desktop rig.  I haven't checked any of the others.  I don't see any other posts about it, so it may be something unique about this system, which is 3 years old and has been beat upon fairly hard sometimes.  It prevents skype from using pulseaudio, but other multimedia packages work correctly, AFAICT.

System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline rueX

  • User
  • Posts: 135
Re: To du or not to du?
« Reply #6 on: 2014/08/29, 00:35:42 »
runs fine after fresh d-u

but suddenly:

kde shutdown / poweroff not possible via icon-control-panel (32-bit) . . . cursor freece at black screen. (my radeon...or kde?)

Offline GoinEasy9

  • User
  • Posts: 560
Re: To du or not to du?
« Reply #7 on: 2014/08/29, 01:55:58 »
The first time, after the upgrade, I had to manually poweroff.  I also got stuck with a black screen and a blinking cursor, but, it only happened that one time.
Linux Counter number 348347

Offline vayu

  • User
  • Posts: 232
Re: To du or not to du?
« Reply #8 on: 2014/09/02, 18:31:31 »
Thanks for all the responses.  I will now dive in to a du.

Edit:  It took awhile, but du completed successfully, and, it seems everything is working.  Thanks again.

Are you using kdepim-ng with kmail2?  I still have 11 packages du wants to remove. I'm a little anxious.  While waiting I've seen the number of packages to upgrade go from 300 to over 500.

Offline GoinEasy9

  • User
  • Posts: 560
Re: To du or not to du?
« Reply #9 on: 2014/09/02, 19:34:19 »
@vayu  I do not use kmail, and, have neither kdepim-ng or kmail2 on my machine.  I do have:

$ apt-cache policy kmail
kmail:
  Installed: 4:4.14.5+really4.4.11.1+l10n-0r2
  Candidate: 4:4.14.5+really4.4.11.1+l10n-0r2
  Version table:
 *** 4:4.14.5+really4.4.11.1+l10n-0r2 0
        500 ftp://ftp.gtlib.gatech.edu/pub/siduction/extra/ unstable/main amd64 Packages
        500 ftp://ftp.gtlib.gatech.edu/pub/siduction/kdenext/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     4:4.14.0-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages

and

$ apt-cache policy kdepim
kdepim:
  Installed: 4:4.14.5+really4.4.11.1+l10n-0r2
  Candidate: 4:4.14.5+really4.4.11.1+l10n-0r2
  Version table:
 *** 4:4.14.5+really4.4.11.1+l10n-0r2 0
        500 ftp://ftp.gtlib.gatech.edu/pub/siduction/extra/ unstable/main amd64 Packages
        500 ftp://ftp.gtlib.gatech.edu/pub/siduction/kdenext/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     4:4.14.0-1 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages

and have no trouble with my upgrades.
Linux Counter number 348347

Offline michaa7

  • User
  • Posts: 2.295
Re: To du or not to du?
« Reply #10 on: 2014/09/02, 19:50:34 »
...I still have 11 packages du wants to remove.
Which?

And have you packages on hold?
Code: [Select]
apt-mark showhold
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Offline vayu

  • User
  • Posts: 232
Re: To du or not to du?
« Reply #11 on: 2014/09/02, 19:59:39 »
Code: [Select]
The following packages will be REMOVED:
  libeventviews4 libincidenceeditorsng4 libksieveui4 libmailcommon4 libmailimporter4 libmarblewidget18
  libmessagecomposer4 libmessageviewer4 libnoteshared4 libpimcommon4 libtemplateparser4 libvlccore7
The following NEW packages will be installed:
  libavcodec56 libavdevice55 libavfilter5 libavformat56 libavresample-dev libavresample2 libavutil54
  libgltf-0.0-0 libkeybinder0 libmarblewidget19 libokularcore5 libshine3 libswscale3 libupower-glib3
  libva-drm1 libvlccore8 python-keybinder
The following packages have been kept back:
  jitsi
The following packages will be upgraded:
There's only one on hold that I put there.

I believe the ones up for removal are all from kmail2.
Maybe I should uninstall kmail, do the upgrade and wait till kmail is ready.  I don't want to go through figuring out which settings to save from my .kde directory so I don't have to do kmail settings it all over again.  I have several email accounts.

Offline michaa7

  • User
  • Posts: 2.295
Re: To du or not to du?
« Reply #12 on: 2014/09/02, 22:35:12 »
Is  jitsi the package you held back?

Whatever, libvlcore7 is replaced by libvlcore8, most others are kdepim related, others mayby kmail, I didn't search for all packages.

So simply wait until the all needed versions are availabe. You may check the situation issuing:
Code: [Select]
apt-get update && apt-get dist-upgrade --ignore-hold -d
This way you don't have to revert your holds but nontheless you'll get an complete overview. The "-d" only downloads all packages, but does not install them. So do not omit the "-d" option while using the "--ignore-hold" option unless you want to install regardless of your held back packages.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

belze

  • Guest
Re: To du or not to du?
« Reply #13 on: 2014/09/03, 00:22:08 »
thank you michaa7 (karma!!!!)
I have kdepim on hold because i upgraded to sid's 4.14 and i feel very comfortable with it (and i have l10n working again!)