Mikasa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
plasmashell crashes on login - so I can't use my desktop system.
To manage notifications about this bug go to:
Mikasa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
plasmashell crashes on login - so I can't use my desktop system.
To manage notifications about this bug go to:
I'm sorry, i misunderstood the text box "comment" as an internal comment
for myself. Can i delete it somehow?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
For what it's worth, this bug is still present in Kubuntu 20.04.
Deleting Print-Manager and reinstalling after reboot (and deleting
printers) ---as advised above--- seems to have solved the problem---for
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: print-manager (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: print-manager (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
>>> This is incorrect, as I've just had it happen to me (again) and I'm
using Eoan.
Although if that actually meant the problem wasn't with plasma-workspace but
rather with print-manager then I disagree.
Clearly plasma-workspace has the ability to crash when presented with incorrect
data. That
>>> no longer affects: plasma-workspace (Ubuntu Eoan)
This is incorrect, as I've just had it happen to me (again) and I;m
using Eoan.
Here is my print queue:
[gmllaptop]: lpstat -R
0 MFCJ6930DW-111gml4410 1024 Fri 24 Jan 2020 17:14:13 GMT
1 MFCJ6930DW-111gml4410
** Changed in: plasma-workspace (Ubuntu)
Status: Confirmed => Invalid
** Also affects: print-manager (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Also affects: plasma-workspace (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects:
** Changed in: print-manager
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
plasmashell crashes on login - so I can't use my desktop system.
The bug is still present in Kubuntu 19.10 (KDE Plasma 5.16.5), and it
appeared two years ago in Kubuntu 17.10.
I have reinstalled the package print-manager on my notebook to install a
new printer, but I was obliged to remove print-manager after plasma
crashed when trying to print as the Wi-Fi was
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: print-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Launchpad has imported 32 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=326289.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: print-manager (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: KDE Bug Tracking System #326289
https://bugs.kde.org/show_bug.cgi?id=326289
** Also affects: print-manager via
https://bugs.kde.org/show_bug.cgi?id=326289
Importance: Unknown
Confirmed on KDE Neon 5.15.1. Might be due to a network printer which
was recognized automatically but now no longer exists. The fixes
mentioned above (uninstalling the print-manager) appears to work.
[ 5748.844786] plasmashell[10378]: segfault at 0 ip 7f9c5c597a50 sp
7ffd24d6a2f0 error
Same here (Kubuntu 18.04.01) - after removing blocked print jobs in CUPS
service UI (http://localhost:631/) plasmashell started. Here is my gdb
backtrace from the crash before:
cl@supertux:~$ gdb /usr/bin/plasmashell
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free
I confirm the error (segfault in dmesg) on kubuntu 18.10. Removing the
printer spool (/var/spool/cups/*) temporarily fixes the problem.
Removing print-manager solved the problem (with the caveats mentioned
above - no notify etc.)
--
You received this bug notification because you are a member of
As suggested by @GordonLack I observe that also in a desktop pc it had
happened an operation like this immediately before the manifestation of
the symptom, precisely the request for a print preview from an
application which, however, had not set a program to be used to manage
the display. This
The same at me:
plasmashell[2492]: segfault at 0 ip 7ff4d97b4556 sp 7ffc42745ad0 error
4 in libkcupslib.so[7ff4d9778000+55000]
4.15.0-43-generic
It seems the bug is unresolved since a half year.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Correction to comment #17 - the "vanishing" printer was due to something
else, please disregard that part.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
plasmashell crashes on login
Another +1
In my case, plasmashell started crashing like this after I had some
problems with printing a document two days back. When I started the PC
today (Kubuntu 18.04), plasmashell would keep crashing with the error
messages outlined above.
After reading this bug report, I did some digging
+1 from me.
I sopped cups via systemctl, then the plasmashell and the taskbar came
up again. I disabled the printer status notification in system settings,
now plasmashell and printing is working (but without notifiy).
--
You received this bug notification because you are a member of Ubuntu
Similar behavior in Kubuntu 18.04. Today I sent a print job to a non existing
printer and in the next reboot, plasmashell did not start, I only got a black
screen.
Removing print-manager fixed the issue for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Btw. I was shocked that a bug in a component could bring down the whole plasma
shell. Where is the
design goal of decoupling of components? I mean, I love KDE, but KDEs quality
seems to be dependent
on every little app running there? Oh my goodness I would have expected a
list of components
Yes, Zaur's post is interesting: it explains why I encountered that
problem only on my laptop (which I use at home and at work with several
printers), and not on my desktop machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>> In case it helps, I printed today to a non-existing printer. (Or not
>> connected now)
>> This might be the reason.
That's interesting. The system on which I had the problem also had an "unusual"
printer defined.
I have a Brother printer/scanner, so add the Brother-supplied driver (more
Deleting the non-existing printer from printers helped:
1) Delete print-manager
$ apt-get remove print-manager
2) Start plasma
sudo service sddm restart
or
kstart plasmashell
3) Install print-manager back again
$ apt-get install print-manager
4) Open Printers
Alt-F2 -> Printers
Remove the not
Hello.
I have encoutered this bug today.
Confirming that the removing of print-manager solves it.
In case it helps, I printed today to a non-existing printer. (Or not connected
now)
This might be the reason.
System info:
===
$ uname -a
Linux xx
I can confirm same exact problems as Sergey on a computer that was once
a Dell XPS, but has been through so many upgrades, the only original
part may now be the power cord!
Uninstalling the print-manager fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Same issue here with Kubuntu 18.04 on an HP EliteBook.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
Title:
plasmashell crashes on login - so I can't use my desktop system.
To manage
Exactly the same issue. Plasmashell segfault with "error 4 in
libkcupslib.so". Black screen after login, all hot keys work, ALT+F2
works, but no desktop GUI. Removing "print-manager" fixed issue, but
this is a hotfix.
My system (if helps):
- Dell XPS 2-in-1
- Kubuntu 17.10 that was staying in my
I first encountered that bug when installing Kubuntu 17.10 on my HP
Zbook. I found a turnaround (see below) but the bug reappeared today
after upgrading to Kubuntu 18.04.
The segfault appears in libkcupslib.so, which is in the print-manager package:
$ apt-file search libkcupslib.so
print-manager:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plasma-workspace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770044
I've had to reinstall 18.04 on this system to make it usable.
It now works - with (essentially) the same configuration and with no change to
my $HOME files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've found the two attached crash files for this issue in /var/crash/
** Attachment added: "crashes.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+attachment/5136461/+files/crashes.tar.gz
--
You received this bug notification because you are a member of
A few other things.
The affect system has these cups processes running:
root@parent:/local/configs/packages# ps -ef | grep cups
root 3421 1 0 01:49 ?00:00:00 /usr/sbin/cupsd -l
lp3423 3421 0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus
dbus://
lp3424
36 matches
Mail list logo
