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

Author Topic:  after du (12.10.) plasma-desktop won´t start  (Read 7879 times)

delta9

  • Guest
Re: after du (12.10.) plasma-desktop won´t start
« Reply #15 on: 2013/11/17, 17:49:01 »
Any news about this issue. I still have a black screen

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: after du (12.10.) plasma-desktop won´t start
« Reply #16 on: 2013/11/17, 18:36:07 »
I have not seen anything about a recent issue with plasma-desktop.  Here it works fine:


Code: [Select]
root@imerabox:/# apt-cache policy plasma-desktop
plasma-desktop:
  Installed: 4:4.11.3-90r3
  Candidate: 4:4.11.3-90r3
  Version table:
 *** 4:4.11.3-90r3 0
        500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
        500 http://packages.siduction.org/kdenext/ experimental-snapshots/main amd64 Packages
        100 /var/lib/dpkg/status
     4:4.11.3-2 0
        500 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
        500 http://http.debian.net/debian/ unstable/main amd64 Packages


Do you get a KDM login?  What happens after you log in?  Can you open a user terminal, and try to start plasma-desktop from there?
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

delta9

  • Guest
Re: after du (12.10.) plasma-desktop won´t start
« Reply #17 on: 2013/11/17, 22:52:36 »
Hello dibl,

after today's d-u i have a working kde desktop again.

Thanks a lot for your time,

Cheers

Offline vayu

  • User
  • Posts: 232
Re: after du (12.10.) plasma-desktop won´t start
« Reply #18 on: 2013/11/21, 18:45:48 »
Any other ideas?  I just did a du today and now have a plasma crash dialog and a black screen.  I've tried renaming plasma-desktop-appletsrc but that did not help. (Edit) Renaming .kde/share/config brings back kde, I haven't found which files have the problem but it was not any of the plasmarc files.

After copying some files over bit by bit and trying to keep track of them, I have some instability with plasma crashing periodically but recovering. I can't tell which files were the ones that introduced the instability.

« Last Edit: 2013/11/21, 19:55:43 by vayu »

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: after du (12.10.) plasma-desktop won´t start
« Reply #19 on: 2013/11/21, 20:11:46 »
Quote from: vayu
Any other ideas?  I just did a du today and now have a plasma crash dialog and a black screen.  I've tried renaming plasma-desktop-appletsrc but that did not help. (Edit) Renaming .kde/share/config brings back kde, I haven't found which files have the problem but it was not any of the plasmarc files.

After copying some files over bit by bit and trying to keep track of them, I have some instability with plasma crashing periodically but recovering. I can't tell which files were the ones that introduced the instability.

You could try in a terminal
Code: [Select]
kquitapp plasma-desktop 
then delete .kde/share/config/plasma-desktop-appletsrc (make sure you back it up first)

then in a terminal, execute plasma-desktop
Code: [Select]
kshell4 plasma-desktop
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline vayu

  • User
  • Posts: 232
Re: after du (12.10.) plasma-desktop won´t start
« Reply #20 on: 2013/11/21, 21:21:24 »
Seems to be some combination in systemsettings and kwinrc.  I haven't isolated it yet.  But even with everything working, systemsettings crashes when going to workspace appearance.


Dieter-MZ

  • Guest
Re: after du (12.10.) plasma-desktop won´t start
« Reply #21 on: 2013/11/22, 08:28:12 »
Hi vayu, that's, what I was facing after a DU a last friday. Workspace appearance crashed. But after a DU last sunday everything is working fine now. Without changing or deleting any *rc-files. So I think there was a temporary missmatch between some files and repositories as mentioned in an other thread here.