Siduction Forum
Siduction Forum => Software - Support => Topic started by: jyp on 2019/02/05, 04:38:03
-
Hi
First kudos to all the people maintaining siduction. Have been forced away from maintaining my computers for a long time and in spite of that, today the full-upgrade went without a hitch with more than 1,500 packages to upgrade. I know this is not the proper way but sometimes life is life.
But, prior to the upgrade I had lost plasmashell; if I can recall, it happened after locking the desktop. Now, after login, wallpaper shows for a second or two and we can see the panel trying to load but then the screen turns black. Otherwise, the computer is fully functional. This behaviour has been recorded by others (superuser / stackoverflow) but none of the solutions appearing there worked for me.
So if someone has a clue it would be most welcome.
Here is the output of inxi -F: http://paste.debian.net/1065295/ (http://paste.debian.net/1065295/)
Here is the ouput of issuing <plasmashell> command: https://pastebin.com/NWZXqPvc (https://pastebin.com/NWZXqPvc)
Thanks a lot again.
-
Can you please try
killall plasmashell && kstart plasmashell
and tell us what it's got to say if it fails.
-
I have tried that before.
Here is the result.$ killall plasmashell && kstart plasmashell
plasmashell: no process found
There is no process associated with _/usr/bin/plasmashell_ (from htop)
-
I also get, after a minute or so of issuing <plasmashell>, the following
...$ Unable to start Dr. Konqi
Re-raising signal for core dump handling.
...$ ^C
[1]+ Segmentation fault (core dumped) plasmashell
...$
-
Could I see the output of
ldd /usr/bin/plasmashell
and
sddm-greeter --test-mode
then
gdb plasmashell
(gdb) bt
(gdb) set detach-on-fork off
(gdb) run
-
@piper
Here is the output : https://pastebin.com/uzBCqfaP (https://pastebin.com/uzBCqfaP)
Thank you
-
Can I see
apt policy print-manager
-
@piper
$ apt policy print-manager
print-manager:
Installed: 4:18.12.1-2
Candidate: 4:18.12.1-2
Version table:
*** 4:18.12.1-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-
For shits && giggles on this, lets try
apt purge print-manager
Reboot
It's a long shot, but, more than one red hat user found this to work for them.
This was the key for me
0x00007fffc8eee768 in JobModel::updateJob(int, KCupsJob const&) () from /usr/lib/x86_64-linux-gnu/libkcupslib.so
I could also be dead wrong, if so, it can be easily reinstalled.
I don't mind being wrong, it's how we learn.
-
@piper
It ... worked!
Thanks a lot.
Of course, it's out of my realm to understand how you got to that conclusion. I read that cups could have been the culprit but... nowhere I could find a simple and direct move like purging print-manager.
siduction team, you are quite a team!
Thanks again.
-
I was 98% sure that was going to work ;)
Glad it solved your problem :)
After doing some debugging, searching, searching again, some more searching, building iso's, failed building iso's, you learn a little bit over the years (wish my german improved over the years).
-
From my own searching, mention of a bug in cups went by my eyes but I had no clue how to resolve that. So thanks again.
I had a note on my desk not to forget to make a donation to the siduction project; it has been done.
So have a nice day.