Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #159902 > unrolled thread

after update kde (plasma) will not start any more

Back to article view | Back to linux.debian.user

Contents

  after update kde (plasma) will not start any more Hans <hans.ullrich@loop.de> - 2015-10-28 15:20 +0100
    Re: after update kde (plasma) will not start any more Bob Weber <bobrweber@gmail.com> - 2015-10-28 18:00 +0100
      Re: after update kde (plasma) will not start any more Hans <hans.ullrich@loop.de> - 2015-10-28 20:50 +0100
        Re: after update kde (plasma) will not start any more Bob Weber <bobrweber@gmail.com> - 2015-10-29 01:50 +0100

#159902 — after update kde (plasma) will not start any more

[Multipart message — attachments visible in raw view] — view raw

Dear list,

after the last update, kde will not start any more (debian/testing).

I believe, it is related to one or more libs, so I send the log of my latest update:

=====================================================================
==========
[UPGRADE] at-spi2-core:i386 2.18.0-1 -> 2.18.1-1
[UPGRADE] chkrootkit:i386 0.50-3.1 -> 0.50-3.2
[UPGRADE] distro-info-data:i386 0.27 -> 0.28
[UPGRADE] evince:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] evince-common:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] gir1.2-evince-3.0:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] gir1.2-pango-1.0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] gnome-session-bin:i386 3.18.0-1+b1 -> 3.18.1.2-1
[UPGRADE] gsettings-desktop-schemas:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] irqbalance:i386 1.0.6-3 -> 1.0.9-1
[UPGRADE] libatk-bridge2.0-0:i386 2.18.0-1 -> 2.18.1-1
[UPGRADE] libatspi2.0-0:i386 2.18.0-1 -> 2.18.1-1
[UPGRADE] libccid:i386 1.4.20-1 -> 1.4.21-1
[UPGRADE] libdatetime-timezone-perl:i386 1:1.93-1+2015f -> 1:1.94-1+2015g
[UPGRADE] libebml4v5:i386 1.3.1-5 -> 1.3.3-1
[UPGRADE] libevdocument3-4:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] libevview3-3:i386 3.18.0-1 -> 3.18.1-1
[UPGRADE] libgcrypt20:i386 1.6.3-2 -> 1.6.4-3
[UPGRADE] libnautilus-extension1a:i386 3.18.0-2+b1 -> 3.18.1-1
[UPGRADE] libnetaddr-ip-perl:i386 4.075+dfsg-1+b1 -> 4.078+dfsg-1
[UPGRADE] libpango-1.0-0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpango1.0-0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpango1.0-doc:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpangocairo-1.0-0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpangoft2-1.0-0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpangoxft-1.0-0:i386 1.38.0-3 -> 1.38.1-1
[UPGRADE] libpod-markdown-perl:i386 3.002000-2 -> 3.003000-1
[UPGRADE] libqt5x11extras5:i386 5.4.2-2+b1 -> 5.5.1-2
[UPGRADE] libsigc++-2.0-0v5:i386 2.6.1-2 -> 2.6.1-3
[UPGRADE] libsoap-lite-perl:i386 1.11-1 -> 1.19-1
[UPGRADE] libtext-csv-xs-perl:i386 1.19-1 -> 1.20-1
[UPGRADE] mkvtoolnix:i386 8.4.0-2 -> 8.5.1-1
[UPGRADE] nautilus:i386 3.18.0-2+b1 -> 3.18.1-1
[UPGRADE] nautilus-data:i386 3.18.0-2 -> 3.18.1-1
[UPGRADE] python-bs4:i386 4.4.0-1 -> 4.4.1-1
[UPGRADE] qml-module-qtgraphicaleffects:i386 5.4.2-2+b1 -> 5.5.1-2
[UPGRADE] qttranslations5-l10n:i386 5.4.2-2 -> 5.5.1-2
=====================================================================
==========

Maybe someone knows exactly, which lib might be related to this bug.

There is a point, which I want to suggest for discussion. IMO, when a new version was added to 
the repo, the last version should be hold back for some time, so it is possible to get easily back 
to the further version. This is often not the case, as packages are put too soon off. For example
take a look at   libqt5x11extras5:i386 5.4.2-2+b1 -> 5.5.1-2, where only the latest and a 
very old 5.3 version is in the repo. 

IMO there should be discussed a better strategy, so that the preversion is always available for 
some time (i.e 3-4 weeks, related to the change cicle somehow).

Thank you for reading. Any help is welcome.

Best 

Hans

[toc] | [next] | [standalone]

#159916

[Multipart message — attachments visible in raw view] — view raw

Try this to see if it works:

The solution is to downgrade libqt5x11extras5 to
libqt5x11extras5_5.4.2-2+b1_amd64 (or 385 if your system is 32bit).

You should find libqt5x11extras5_5.4.2-2+b1_amd64.deb in the
/var/cache/apt/archives directory if you haven't run "apt-get clean" recently.  
Mine was dated Aug 9.  Use "dpkg -i libqt5x11extras5_5.4.2-2+b1_amd64.deb" to
install it.  dpkg will notify you that it is downgrading the package.



*...Bob*

[toc] | [prev] | [next] | [standalone]

#159924

Am Mittwoch, 28. Oktober 2015, 12:53:05 schrieb Bob Weber:
> Try this to see if it works:
Hi Bob,
> 
> The solution is to downgrade libqt5x11extras5 to
> libqt5x11extras5_5.4.2-2+b1_amd64 (or 385 if your system is 32bit).
> 
> You should find libqt5x11extras5_5.4.2-2+b1_amd64.deb in the
> /var/cache/apt/archives directory if you haven't run "apt-get clean"
> recently. Mine was dated Aug 9.  Use "dpkg -i
> libqt5x11extras5_5.4.2-2+b1_amd64.deb" to install it.  dpkg will notify you
> that it is downgrading the package.
yes, I already suspected this lib, but that version disappeared from the 
official repo. However, I found it in the internet. Installed, worked.

But as I suggested: latest prior version should stay in the official repo for 
some time, just to be able to revert back.

> 
> 
> 
> *...Bob*
Thanks anyway

Best 

Hans

[toc] | [prev] | [next] | [standalone]

#159937

On 10/28/2015 03:46 PM, Hans wrote:
> Am Mittwoch, 28. Oktober 2015, 12:53:05 schrieb Bob Weber:
>> Try this to see if it works:
> Hi Bob,
>> The solution is to downgrade libqt5x11extras5 to
>> libqt5x11extras5_5.4.2-2+b1_amd64 (or 385 if your system is 32bit).
>>
>> You should find libqt5x11extras5_5.4.2-2+b1_amd64.deb in the
>> /var/cache/apt/archives directory if you haven't run "apt-get clean"
>> recently. Mine was dated Aug 9.  Use "dpkg -i
>> libqt5x11extras5_5.4.2-2+b1_amd64.deb" to install it.  dpkg will notify you
>> that it is downgrading the package.
> yes, I already suspected this lib, but that version disappeared from the 
> official repo. However, I found it in the internet. Installed, worked.
>
> But as I suggested: latest prior version should stay in the official repo for 
> some time, just to be able to revert back.
>
>>
>>
>> *...Bob*
> Thanks anyway
>
> Best 
>
> Hans


I have been burned too many times running testing so I have developed the
following procedures to make things a little safer.

I use approx on my internet router/server machine to serve debian packages to
all the other machines on my network.  That way I have all the packages that
have been installed since I started using approx.  I have disabled the cron job
for approx that cleans out the older packages approx retrieves so I don't have
to worry that I will lose any needed packages.  I can use "apt-get clean" on
each machine without worrying that I will lose older needed packages.

Besides daily backups using backuppc on a dedicated server I also use rsnapshot
to make a snapshot of my root file system (home is on another file system where
these backups go)  before I do an upgrade ... just in case.  If I miss some
problem a quick reboot into sysrescucd and I copy the snapshot back to the root
file system so I can get going again!

I also first upgrade 3 VM's running testing also so I will know of any problems
before I upgrade my main machine.  I caught the libqt5x11extras5 problem that
way.  I had the black screen of death on a VM.  I googled for a solution to the
problem after seeing sddm crashing with a segfault in libxcb.so in syslog.

...Bob

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web