330055 – KDE window manager crashed and not recoverable after 12/2313 update

Bug 330055 - KDE window manager crashed and not recoverable after 12/2313 update

Summary: KDE window manager crashed and not recoverable after 12/2313 update

Status:	RESOLVED DUPLICATE of bug 305654

Alias:	None

Product:	kmix
Classification:	Applications
Component:	general (show other bugs)
Version:	unspecified
Platform:	Chakra Linux

Importance:	NOR normal
Target Milestone:	---
Assignee:	Christian Esken

URL:
Keywords:

Depends on:
Blocks:

Reported:	2014-01-17 04:48 UTC by akachi68
Modified:	2014-01-19 05:43 UTC (History)
CC List:	3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description akachi68 2014-01-17 04:48:32 UTC

The system loads into a dark screen and the error message below is displayed at the top of the screen:   "Usbhid couldn't find input interrupt endpoint" . I tried upgrading the system,but it did not help.   How can i repaid the system.  Thanks

 Here's the  KCrash report log: 
Executable: kmix PID: 578 Signal: Bus error (7) Time: 01/04/14
04:30:22 PM
Application: KMix (kmix), signal: Bus error
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#5  0x00007f9859469a94 in testAndSetOrdered (newValue=1,
expectedValue=0, this=0x7f983a298000)
at /usr/include/QtCore/qatomic_x86_64.h:145
#6  testAndSetAcquire (newValue=1, expectedValue=0, this=0x7f983a298000)
at /usr/include/QtCore/qatomic_x86_64.h:267
#7  KSharedDataCache::Private::mapSharedMemory
(this=this@entry=0xaa7790)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/kdecore/util/kshareddatacache.cpp:1160
#8  0x00007f98594638cf in Private (expectedItemSize=0,
defaultCacheSize=83886080, name=..., this=0xaa7790)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/kdecore/util/kshareddatacache.cpp:1005
#9  KSharedDataCache::KSharedDataCache (this=0xa77ce0, cacheName=...,
defaultCacheSize=83886080, expectedItemSize=0)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/kdecore/util/kshareddatacache.cpp:1430
#10 0x00007f9859cf75ae in KImageCache::KImageCache(QString const&,
unsigned int, unsigned int) () from /usr/lib/libkdeui.so.5
#11 0x00007f984dfe8faf in Plasma::ThemePrivate::useCache (this=0xb82010)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/theme.cpp:251
#12 0x00007f984dfe9af2 in Plasma::Theme::findInCache (this=0xb935f0,
key=..., pix=...)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/theme.cpp:974
#13 0x00007f984df804a0 in Plasma::FrameSvgPrivate::generateBackground
(this=this@entry=0xb7f7e0, frame=frame@entry=0xaa73d0)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/framesvg.cpp:671
#14 0x00007f984df815fe in Plasma::FrameSvgPrivate::alphaMask
(this=0xb7f7e0)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/framesvg.cpp:646
#15 0x00007f984df81fb2 in Plasma::FrameSvg::mask (this=<optimized out>)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/framesvg.cpp:459
#16 0x00007f984df61a79 in Plasma::DialogPrivate::updateMask
(this=0xb7fc10)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/dialog.cpp:116
#17 0x00007f984df6308e in Plasma::DialogPrivate::themeChanged
(this=0xb7fc10)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/dialog.cpp:104
#18 0x00007f984df633a2 in Plasma::Dialog::Dialog (this=0xb7f900,
parent=<optimized out>, f=...)
at /chakra/desktop-unstable/kdelibs/src/kdelibs-4.11.3/plasma/dialog.cpp:406
#19 0x00007f9844209a20 in ?? () from /usr/lib/libkdeinit4_kmix.so
#20 0x00007f98441ded93 in ?? () from /usr/lib/libkdeinit4_kmix.so
#21 0x00007f98441e6e13 in ?? () from /usr/lib/libkdeinit4_kmix.so
#22 0x00007f98441e7ffb in ?? () from /usr/lib/libkdeinit4_kmix.so
#23 0x00007f9859c9f9ac in ?? () from /usr/lib/libkdeui.so.5
#24 0x00007f9859c9fa35 in ?? () from /usr/lib/libkdeui.so.5
#25 0x00007f9859c9fc53 in ?? () from /usr/lib/libkdeui.so.5
#26 0x00007f9855c2c106 in ?? () from /usr/lib/libQtDBus.so.4
#27 0x00007f9855c2d1e9 in ?? () from /usr/lib/libQtDBus.so.4
#28 0x00007f9855c2dca4 in ?? () from /usr/lib/libQtDBus.so.4
#29 0x00007f9855c2dd7b in ?? () from /usr/lib/libQtDBus.so.4
#30 0x00007f9858ef21de in QObject::event(QEvent*) ()
from /usr/lib/libQtCore.so.4
#31 0x00007f9858083e43 in QApplication::event(QEvent*) ()
from /usr/lib/libQtGui.so.4
#32 0x00007f985807ee4c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib/libQtGui.so.4
#33 0x00007f9858085410 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libQtGui.so.4
#34 0x00007f9859c9875a in KApplication::notify(QObject*, QEvent*) ()
from /usr/lib/libkdeui.so.5
#35 0x00007f9858eda2ed in QCoreApplication::notifyInternal(QObject*,
QEvent*) () from /usr/lib/libQtCore.so.4
#36 0x00007f9858edd33f in
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
() from /usr/lib/libQtCore.so.4
#37 0x00007f9858f07543 in ?? () from /usr/lib/libQtCore.so.4
#38 0x00007f98547b7375 in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#39 0x00007f98547b76a8 in ?? () from /usr/lib/libglib-2.0.so.0
#40 0x00007f98547b7764 in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#41 0x00007f9858f06e05 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#42 0x00007f985811b676 in ?? () from /usr/lib/libQtGui.so.4
#43 0x00007f9858ed8f4f in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#44 0x00007f9858ed9245 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#45 0x00007f9858ede35b in QCoreApplication::exec() ()
from /usr/lib/libQtCore.so.4
#46 0x00007f98441dddba in kdemain () from /usr/lib/libkdeinit4_kmix.so
#47 0x0000000000407f59 in _start ()





Reproducible: Always

Steps to Reproduce:
1.Reboot system and wait for system to load
2.Reboot system and wait for system to load
3.Reboot system and wait for system to load

Comment 1 Martin Flöser 2014-01-17 12:34:48 UTC

Unfortunately we cannot really help you here. This is not a support forum but a technical issue tracker. The information you provide shows a crash in kmix, but the crash trace is incomplete and of no help.

From the information you provided it looks like a broken installation. I highly recommend to get help in the support forums provided by your distribution.

Reassign to kmix as it's the closest thing I can think of with the crash trace of kmix.

Comment 2 Thomas Lübking 2014-01-17 17:51:04 UTC

The bug is somehow contradictive, either you end up in VT1 ("dark screen") seeing the Usbhid error, or you make it to X11 and KDE - and then X11 crashes.

Either way, reg. the backtrace for kmix:
it ends in KSharedDataCache, what *may* indicate garbage cache data -> try moving it aside:

   mv /var/tmp/kdecache-`whoami` /var/tmp/nix.kdecache-`whoami`

Ever used sth. called bleachbit?

Reg. the Usbhid error: is there a KVM switch involved? -> Try removing it.

But in general and as Martin said: please ask on the chakra support forums to resolve this.

Comment 3 Christoph Feck 2014-01-18 01:00:06 UTC


*** This bug has been marked as a duplicate of bug 305654 ***

Comment 4 akachi68 2014-01-18 19:19:10 UTC

Thanks. I will try the suggestions you provided.
On Jan 17, 2014 11:51 AM, "Thomas Lübking" <thomas.luebking@gmail.com>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=330055
>
> Thomas Lübking <thomas.luebking@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |thomas.luebking@gmail.com
>
> --- Comment #2 from Thomas Lübking <thomas.luebking@gmail.com> ---
> The bug is somehow contradictive, either you end up in VT1 ("dark screen")
> seeing the Usbhid error, or you make it to X11 and KDE - and then X11
> crashes.
>
> Either way, reg. the backtrace for kmix:
> it ends in KSharedDataCache, what *may* indicate garbage cache data -> try
> moving it aside:
>
>    mv /var/tmp/kdecache-`whoami` /var/tmp/nix.kdecache-`whoami`
>
> Ever used sth. called bleachbit?
>
> Reg. the Usbhid error: is there a KVM switch involved? -> Try removing it.
>
> But in general and as Martin said: please ask on the chakra support forums
> to
> resolve this.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.

Comment 5 Thomas Lübking 2014-01-18 19:29:55 UTC

ps, see dupe - full hard drive might be the cause.
-> check
     df -h
and
     du -hs /var/cache/pacman/pkg
for a pot. cause

Comment 6 akachi68 2014-01-19 00:53:02 UTC

Thanks Thomas.  The HD is not full, but how do i clear the cache?

----- Original Message -----
From: "Thomas Lübking" <thomas.luebking@gmail.com>
To: ichery865@gmail.com
Sent: Saturday, January 18, 2014 1:29:55 PM
Subject: [kmix] [Bug 330055] KDE window manager crashed and not recoverable after 12/2313 update

https://bugs.kde.org/show_bug.cgi?id=330055

--- Comment #5 from Thomas Lübking <thomas.luebking@gmail.com> ---
ps, see dupe - full hard drive might be the cause.
-> check
     df -h
and
     du -hs /var/cache/pacman/pkg
for a pot. cause

Comment 7 Thomas Lübking 2014-01-19 00:54:26 UTC

sudo rm /var/cache/pacman/pkg/*

Comment 8 akachi68 2014-01-19 05:43:34 UTC

Thanks a lot. 

----- Original Message -----
From: "Thomas Lübking" <thomas.luebking@gmail.com>
To: ichery865@gmail.com
Sent: Saturday, January 18, 2014 6:54:26 PM
Subject: [kmix] [Bug 330055] KDE window manager crashed and not recoverable after 12/2313 update

https://bugs.kde.org/show_bug.cgi?id=330055

--- Comment #7 from Thomas Lübking <thomas.luebking@gmail.com> ---
sudo rm /var/cache/pacman/pkg/*