[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-12-21 Thread Timon Michel
Mikasa

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-12-21 Thread Timon Michel
Mikasa

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-04-21 Thread Launchpad Bug Tracker
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-04-21 Thread Launchpad Bug Tracker
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-02-02 Thread Gordon Lack
>>> 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 itself is a bug! Applications should validate their input and handle 
errors appropriately. A crash is not an appropriate handling.

Also, will the Focal fix be backported to the earlier, still suffering
releases?

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-02-02 Thread Gordon Lack
>>> 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   1024 Fri 24 Jan 2020 17:14:13 GMT
  2 MFCJ6930DW-111gml4410   1024 Fri 24 Jan 2020 17:14:13 GMT

Note that despite the time (>9 days ago) it only caused the problem just
now (I suspect at approximately the midnight rollover from Sunday Feb
2nd to Monday 3rd).

A "cancel -x -a" has removed these records and my laptop is now OK
again.

Attached is the saved crash text file.

** Attachment added: "plasmashell-20200203-000819.kcrash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+attachment/5324881/+files/plasmashell-20200203-000819.kcrash.txt

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2020-01-09 Thread Rik Mills
** 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: print-manager (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: plasma-workspace (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: print-manager (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: plasma-workspace (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** No longer affects: plasma-workspace (Ubuntu Bionic)

** No longer affects: plasma-workspace (Ubuntu Eoan)

** No longer affects: plasma-workspace (Ubuntu Focal)

** Changed in: print-manager (Ubuntu Focal)
   Status: Confirmed => Fix Released

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2019-12-03 Thread Bug Watch Updater
** Changed in: print-manager
   Status: Confirmed => Fix Released

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2019-11-15 Thread vmagnin
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 off.

Note that without the print-manager, I can not add printers but I can
still print on already installed printers. So you can install print-
manager each time you need to manage a new printer then uninstall the
package.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2019-07-08 Thread Bug Watch Updater
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
https://help.launchpad.net/InterBugTracking.


On 2013-10-19T20:07:38+00:00 Piotr Kęplicz wrote:

Application: plasma-desktop (4.11.2)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:

I started printing some documents and before the printing job finished,
I modified printer applet settings so that it would show finished jobs
also. It crashed plasma-desktop, restarting it causes crash again.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Powłoka pulpitu Plazmy (plasma-desktop), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1277740 (LWP 5114))]

Thread 5 (Thread 0xad787b40 (LWP 5115)):
#0  0xb772a424 in __kernel_vsyscall ()
#1  0xb20e184b in pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb75de9bc in __pthread_cond_wait (cond=0xb31e38d0, mutex=0xb31e38b8) at 
forward.c:149
#3  0xb30e0ef2 in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#4  0xb30e0f3f in ?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
#5  0xb20ddd78 in start_thread (arg=0xad787b40) at pthread_create.c:311
#6  0xb75d101e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 4 (Thread 0xa6a9db40 (LWP 5116)):
#0  0xb75deba7 in pthread_mutex_lock (mutex=0xa6100558) at forward.c:192
#1  0xb200bba0 in g_mutex_lock (mutex=mutex@entry=0xa61004e0) at 
/build/buildd/glib2.0-2.38.0/./glib/gthread-posix.c:213
#2  0xb1fc858b in g_main_context_check (context=context@entry=0xa61004e0, 
max_priority=2147483647, fds=fds@entry=0xa6102288, n_fds=n_fds@entry=1) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3558
#3  0xb1fc8aea in g_main_context_iterate (context=context@entry=0xa61004e0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3709
#4  0xb1fc8c98 in g_main_context_iteration (context=0xa61004e0, may_block=1) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3773
#5  0xb603a8df in QEventDispatcherGlib::processEvents (this=0xa6100468, 
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb60099f3 in QEventLoop::processEvents (this=this@entry=0xa6a9d228, 
flags=...) at kernel/qeventloop.cpp:149
#7  0xb6009d19 in QEventLoop::exec (this=this@entry=0xa6a9d228, flags=...) at 
kernel/qeventloop.cpp:204
#8  0xb5ef8e3d in QThread::exec (this=this@entry=0xa831688) at 
thread/qthread.cpp:542
#9  0xb5fe9e14 in QInotifyFileSystemWatcherEngine::run (this=0xa831688) at 
io/qfilesystemwatcher_inotify.cpp:265
#10 0xb5efb72f in QThreadPrivate::start (arg=0xa831688) at 
thread/qthread_unix.cpp:338
#11 0xb20ddd78 in start_thread (arg=0xa6a9db40) at pthread_create.c:311
#12 0xb75d101e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 3 (Thread 0xa53ffb40 (LWP 5118)):
#0  0xb772a424 in __kernel_vsyscall ()
#1  0xb75c1a0b in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb1fd7a3b in poll (__timeout=__timeout@entry=-1, __nfds=__nfds@entry=1, 
__fds=__fds@entry=0xa4a023a0) at /usr/include/i386-linux-gnu/bits/poll2.h:46
#3  g_poll (fds=fds@entry=0xa4a023a0, nfds=nfds@entry=1, 
timeout=timeout@entry=-1) at /build/buildd/glib2.0-2.38.0/./glib/gpoll.c:132
#4  0xb1fc8b58 in g_main_context_poll (priority=2147483647, n_fds=1, 
fds=0xa4a023a0, timeout=-1, context=0xa5408d10) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:4006
#5  g_main_context_iterate (context=0xa5408d10, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3707
#6  0xb1fc903b in g_main_loop_run (loop=0xa5408cd8) at 
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3906
#7  0xa5e1a0ea in gdbus_shared_thread_func (user_data=0xa5408cf8) at 
/build/buildd/glib2.0-2.38.0/./gio/gdbusprivate.c:278
#8  0xb1feec3a in g_thread_proxy (data=0xa8affb0) at 
/build/buildd/glib2.0-2.38.0/./glib/gthread.c:798
#9  0xb20ddd78 in start_thread (arg=0xa53ffb40) at pthread_create.c:311
#10 0xb75d101e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 2 (Thread 0xa1135b40 (LWP 5121)):
#0  0xb772a424 in __kernel_vsyscall ()
#1  0xb75bf8db in read () at ../sysdeps/unix/syscall-template.S:81
#2  0xb200ad3e in read (__nbytes=16, __buf=0xa113507c, __fd=) at 
/usr/include/i386-linux-gnu/bits/unistd.h:44
#3  g_wakeup_acknowledge (wakeup=0xa4a051b0) at 
/build/buildd/glib2.0-2.38.0/./glib/gwakeup.c:212
#4  0xb1fc864b in g_main_context_check (context=context@entry=0xa540a230, 
max_priority=2147483647, 

[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2019-02-26 Thread Matthias Hadlich
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 4 in libkcupslib.so[7f9c5c557000+56000]


Also my logs indicate that this might be related to an AppArmor issue with the 
/usr/sbin/cupsd profile. There are multiple denied entries in the logs whichof 
I have appended one. Afterwards there is the segfault in libkcupslib. 


syslog:Feb 26 18:55:13 matteo-whatever kernel: [ 5090.165402] audit: type=1400 
audit(1551203713.010:42): apparmor="DENIED" operation="file_lock" 
profile="/usr/sbin/cupsd" name="/run/utmp" pid=1420 comm="cupsd" 
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
syslog:Feb 26 18:58:11 matteo-whatever kernel: [ 5268.663312] 
plasmashell[4392]: segfault at 0 ip 7f1ee3c3ea50 sp 7ffdafee0690 error 
4 in libkcupslib.so[7f1ee3bfe000+56000]

After reinstalling the logs have changed and the "denied" entries have been 
changed into "allowed":
syslog:Feb 26 19:06:11 matteo-whatever kernel: [ 5748.809771] audit: type=1400 
audit(1551204371.662:52): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=1420 comm="cupsd" capability=12  
capname="net_admin"


My system: 
Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.1
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.0
Kernel Version: 4.15.12-041512-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 15.5 GiB of RAM

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2019-01-09 Thread Hummel, Martin
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-11-17 Thread Thomas Ribbrock
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-11-17 Thread Thomas Ribbrock
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 and found the
following:

- One of the attempts of printing the document apparently resulted in a "stuck" 
print job in CUPS
- That job was listed twice with the same ID
- I could cancel one of them, but not the other one, as it had the same ID
- After manually removing the stuck job from /var/spool/cups and rebooting the 
PC, everything worked again
- Strangely enough, one of the two printers I had previously configured has now 
vanished completely from CUPS

So, the root cause seems to lie in CUPS rather than KDE, but I find it
extremely puzzling that an error in CUPS keeps KDE from starting
properly - this seems to be a bug in itself.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-11-02 Thread Andreas John
+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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-10-02 Thread Cristian Arteaga
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-09-26 Thread Buddy Butterfly
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 with its status. Something like (unloaded, loaded, active, 
broken, etc.), but KDE running up and being stable. Something like osgi for 
KDE? ;-)

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-08-13 Thread Steve Baker
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-08-07 Thread Luca Morandini
Same issue here with Kubuntu 18.04 on an HP EliteBook.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-06-04 Thread Sergey Tryuber
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 PC for last few months and that was 
initially grown up from Kubuntu 16.04. 
- Looks like the bug came in one of last updates.
- First that I did when saw no GUI after reboot - upgraded to 18.04 with a 
hope, that upgrade will overwrite buggy pages. But the issue remained.
- Cleaning up ".config" directory or creation of a new user does not work. New 
user accounts do not have GUI either.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-05-30 Thread vmagnin
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: /usr/lib/x86_64-linux-gnu/libkcupslib.so

So I removed it:
$ sudo apt-get remove print-manager

After reboot or relogging, plasma is now working.
The problem is that I can't print anymore. And if I reinstall print-manager the 
bug is back.

Note that I installed Kubuntu 17.10 & 18.04 on 5 machines, and the bug
appears only on my HP Zbook.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-05-20 Thread Gordon Lack
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 Kubuntu
Bugs, which is subscribed to plasma-workspace in 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:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.

2018-05-08 Thread Gordon Lack
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  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3425  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3426  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3427  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3428  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3429  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3430  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3431  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3432  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
root  3434  2860  0 01:49 pts/100:00:00 grep 
cupsroot@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  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3425  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3426  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3427  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3428  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3429  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3430  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3431  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
lp3432  3421  0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus 
dbus://
root  3434  2860  0 01:49 pts/100:00:00 grep cups

My laptop (the one I'm reporting from) which should be configured the
same) has:

[gmllaptop]: ps -ef | grep cups
root   984 1  0 01:07 ?00:00:00 /usr/sbin/cupsd -l
root  1032 1  0 01:08 ?00:00:00 /usr/sbin/cups-browsed
gml4410   7966  4133  0 01:45 pts/200:00:00 grep cups

My (failing) desktop is also reporting:

root@parent:/var/log# grep cups-browsed syslog | grep DENIED
May  9 00:58:44 parent kernel: [   39.940369] audit: type=1400 
audit(1525823924.302:22): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cups-browsed" name="/local/lib/libunistring.so.2.0.0" 
pid=1133 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
May  9 01:11:30 parent kernel: [   39.218176] audit: type=1400 
audit(1525824690.582:22): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cups-browsed" name="/local/lib/libunistring.so.2.0.0" 
pid=1144 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
May  9 01:24:22 parent kernel: [   40.002547] audit: type=1400 
audit(1525825462.362:22): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cups-browsed" name="/local/lib/libunistring.so.2.0.0" 
pid=1158 comm="cups-browsed" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

(which my laptop does not) - but it has been reporting this for a long
time.

-- 
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:
  plasmashell crashes on login - so I can't use my desktop system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs