[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kubuntu plasma 5 login error
From:       Kevin Funk <kfunk () kde ! org>
Date:       2014-12-18 8:30:49
Message-ID: 1865284.ahEfI3hZTP () kerberos
[Download RAW message or body]

On Thursday 18 December 2014 09:15:14 Kevin Funk wrote:
> On Thursday 18 December 2014 05:12:10 anu mittal wrote:
> > Okay I will give it a try. Thanks.
> > 
> > On Thu, Dec 18, 2014, 6:43 AM Aleix Pol <aleixpol@kde.org> wrote:
> > > On Wed, Dec 17, 2014 at 7:35 PM, anu mittal <anu22mittal@gmail.com> 
wrote:
> > > > Hi everyone,
> > > > I have been using kubuntu plasma 5 via VMware Workstation 9.0 for
> > > 
> > > porting an
> > > 
> > > > application to kf5,everything was working perfectly but when i tried
> > > 
> > > logging
> > > 
> > > > in kubuntu today via same vmware, after accepting the login password
> > > > and
> > > > loading the system the screen faded and turned blank.
> > > > The error message which i got from .xsession-error was:
> > > > 
> > > > kded5 : org.kde.powerdevil.backlighthelper.brightnessvaluemax failed
> > > > list is empty
> > > > lock called
> > > > 
> > > > I would like to know if there any solution for it or should i dual
> > > > boot
> > > 
> > > my
> > > 
> > > > laptops's main memory and try working on kubuntu from there.?
> > > > --
> > > > Regards,
> > > > Anu.
> > > > 
> > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> > > 
> > > unsubscribe
> > > 
> > > >>> <<
> > > 
> > > Something I've seen doing a plasma 5 kubuntu user today is:
> > > - getting the blank screen.
> > > - opening a konsole
> > > - killall plasmashell
> > > - plasmashell
> > > 
> > > It worked for him, still it seems to be a downstream problem.
> > > 
> > > Aleix
> > > 
> > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> > > 
> > > unsubscribe <<
> 
> Heya, I'm also having issues with Plasma 5 from Kubuntu PPA's packages.
> 
> Seems related to this one. After some suspend/resumes cycles it seems that
> something in in the kded+powerdevil integration breaks and I can no longer
> use any Power Management related features.
> 
> One issue: Clicking on "Power Management" in system settings just freezes
> the application. Suspending no longer works.
> 
> Attaching GDB to kded5 brings the following backtrace, which seems to
> indicate some issue with Polkit, it hangs in
> 'polkit_authority_check_authorization'. Did anyone else see this already
> and could provide some pointers where to look at?
> 
> Backtrace attached
> 
> Greets

Alright, looking at all threads gives the following interesting backtrace for 
thread 3:

Thread 3 (Thread 0x7f522a7fc700 (LWP 797)):
#0  __lll_lock_wait_private () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x00007f5251588931 in _L_lock_14320 () at malloc.c:5206
#2  0x00007f5251586cc1 in __libc_calloc (n=139990700916768, 
elem_size=<optimized out>) at malloc.c:3197
#3  0x00007f524d896527 in ?? () from /usr/lib/nvidia-331-
updates/tls/libnvidia-tls.so.331.113
#4  0x00007f525256c998 in KCrash::defaultCrashHandler(int) () from 
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
#5  <signal handler called>
#6  malloc_consolidate (av=av@entry=0x7f5220000020) at malloc.c:4151
#7  0x00007f5251583fd8 in _int_malloc (av=av@entry=0x7f5220000020, 
bytes=bytes@entry=2032) at malloc.c:3423
#8  0x00007f5251586cfc in __libc_calloc (n=<optimized out>, 
elem_size=<optimized out>) at malloc.c:3219
#9  0x00007f524d8971ae in ?? () from /usr/lib/nvidia-331-
updates/tls/libnvidia-tls.so.331.113
#10 0x00007f524e3ca822 in g_malloc0 (n_bytes=2032) at 
/build/buildd/glib2.0-2.42.1/./glib/gmem.c:127
#11 0x00007f524e3e1fbc in thread_memory_from_self () at 
/build/buildd/glib2.0-2.42.1/./glib/gslice.c:519
#12 g_slice_free1 (mem_size=<optimized out>, mem_block=0x7f521c002270)
    at /build/buildd/glib2.0-2.42.1/./glib/gslice.c:1088
#13 0x00007f524ee21ea2 in __nptl_deallocate_tsd () at pthread_create.c:157
#14 0x00007f524ee220b8 in start_thread (arg=0x7f522a7fc700) at 
pthread_create.c:322
#15 0x00007f52515fd77d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Seems like kded5 already crashed, but still keeps running because it 
deadlocked in the signal handler...

Still, cannot find any sign of bug report about this issue on the interwebs... 
Just me?

-- 
Kevin Funk | kfunk@kde.org | http://kfunk.org

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]