Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Desktop Environments
  • Search

[SOLVED] KDE broke after upgrade

Problems with GUI applications? Questions about X, KDE, Gnome, Fluxbox, etc.? Come on in. NOTE: For multimedia, go up one forum
Post Reply
Advanced search
46 posts
  • 1
  • 2
  • Next
Author
Message
Etal
Veteran
Veteran
User avatar
Posts: 1932
Joined: Fri Jul 15, 2005 3:01 pm

[SOLVED] KDE broke after upgrade

  • Quote

Post by Etal » Wed Dec 02, 2009 3:43 am

Hello,

I upgraded Qt to 4.6 and KDE to 4.3.4. The problem is that now Plasma and KDED4 segfault.

Here are the backtraces (they look similar):

Plasma:

Code: Select all

Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[KCrash Handler]
#6  qVariantToHelper<QStringList> (this=<value optimized out>) at kernel/qvariant.cpp:2061
#7  QVariant::toStringList (this=<value optimized out>) at kernel/qvariant.cpp:2080
#8  0xac0c0f83 in HalPower::brightnessControlsAvailable (this=0x8abeb38) at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/solid/hal/halpower.cpp:364
#9  0xac384cbc in Solid::Control::PowerManager::brightnessControlsAvailable () at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/libs/solid/control/powermanager.cpp:147
#10 0xac386588 in Solid::Control::PowerManager::brightness (device=<value optimized out>) at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/libs/solid/control/powermanager.cpp:187
#11 0xac12d55a in Battery::initExtenderItem (this=0x890afa0, item=0x8ac2c40) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4/plasma/applets/battery/battery.cpp:406
#12 0x417c8d39 in Plasma::ExtenderPrivate::loadExtenderItems (this=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/plasma/extender.cpp:659
#13 0x417c9e54 in Extender (this=<value optimized out>, applet=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/plasma/extender.cpp:114
#14 0x41788530 in Plasma::Applet::extender (this=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/plasma/applet.cpp:688
#15 0xac130e03 in Battery::init (this=0x890afa0) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4/plasma/applets/battery/battery.cpp:148
#16 0x417b2ce4 in Plasma::Corona::loadLayout (this=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/plasma/corona.cpp:377
#17 0x417b3eb5 in Plasma::Corona::initializeLayout (this=<value optimized out>, configName=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/plasma/corona.cpp:324
#18 0x410840ab in PlasmaApp::corona (this=<value optimized out>) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4/plasma/shells/desktop/plasmaapp.cpp:574
#19 0x410843d1 in PlasmaApp::setupDesktop (this=<value optimized out>) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4/plasma/shells/desktop/plasmaapp.cpp:252
#20 0x41084d51 in PlasmaApp::qt_metacall (this=<value optimized out>, _c=<value optimized out>, _id=<value optimized out>, _a=<value optimized out>)
    at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4_build/plasma/shells/desktop/plasmaapp.moc:121
#21 0x421e50bd in QMetaObject::metacall (object=<value optimized out>, cl=<value optimized out>, idx=<value optimized out>, argv=<value optimized out>) at kernel/qmetaobject.cpp:237
#22 0x421f3e9f in QMetaObject::activate (sender=<value optimized out>, m=) at kernel/qobject.cpp:3286
#23 0x421fbe36 in QSingleShotTimer::timeout (this=) at .moc/release-shared/qtimer.moc:82
#24 0x421fbf6d in QSingleShotTimer::timerEvent (this=<value optimized out>) at kernel/qtimer.cpp:308
#25 0x421f0934 in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1216
#26 0x4665da5c in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:4242
#27 0x46666808 in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3661
#28 0x424df1a2 in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#29 0x421dfc8d in QCoreApplication::notifyInternal (this=) at kernel/qcoreapplication.cpp:704
#30 0x422102da in QCoreApplication::sendEvent (this=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#31 QTimerInfoList::activateTimers (this=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:603
#32 0x4220cef3 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184
#33 0x43cd1b9f in g_main_dispatch (context=) at gmain.c:1960
#34 IA__g_main_context_dispatch (context=) at gmain.c:2513
#35 0x43cd55b8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=) at gmain.c:2591
#36 0x43cd56df in IA__g_main_context_iteration (context=<value optimized out>, may_block=) at gmain.c:2654
#37 0x4220cbc2 in QEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#38 0x4670c1eb in QGuiEventDispatcherGlib::processEvents (this=) at kernel/qguieventdispatcher_glib.cpp:202
#39 0x421de24e in QEventLoop::processEvents (this=) at kernel/qeventloop.cpp:149
#40 0x421de6a9 in QEventLoop::exec (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:201
#41 0x421e290e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#42 0x4665db05 in QApplication::exec () at kernel/qapplication.cpp:3570
#43 0x41067aaa in kdemain (argc=) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4/plasma/shells/desktop/main.cpp:50
#44 0x080486fb in main (argc=1, argv=0xbf9350b4) at /var/tmp/portage/kde-base/plasma-workspace-4.3.4/work/plasma-workspace-4.3.4_build/plasma/shells/desktop/plasma-desktop_dummy.cpp:3
KDED4:

Code: Select all

Application: KDE Daemon (kded4), signal: Segmentation fault
[KCrash Handler]
#6  qVariantToHelper<QStringList> (this=<value optimized out>) at kernel/qvariant.cpp:2061
#7  QVariant::toStringList (this=<value optimized out>) at kernel/qvariant.cpp:2080
#8  0xb6191f83 in HalPower::brightnessControlsAvailable (this=0x9477c28) at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/solid/hal/halpower.cpp:364
#9  0x41047cbc in Solid::Control::PowerManager::brightnessControlsAvailable () at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/libs/solid/control/powermanager.cpp:147
#10 0x4104918f in Solid::Control::PowerManager::setBrightness (brightness=) at /var/tmp/portage/kde-base/solid-4.3.4/work/solid-4.3.4/libs/solid/control/powermanager.cpp:157
#11 0xb5f70fb9 in PowerDevilDaemon::applyProfile (this=0x94680f8) at /var/tmp/portage/kde-base/powerdevil-4.3.4/work/powerdevil-4.3.4/powerdevil/daemon/PowerDevilDaemon.cpp:458
#12 0xb5f71808 in PowerDevilDaemon::refreshStatus (this=0x94680f8) at /var/tmp/portage/kde-base/powerdevil-4.3.4/work/powerdevil-4.3.4/powerdevil/daemon/PowerDevilDaemon.cpp:402
#13 0xb5f74295 in PowerDevilDaemon (this=0x94680f8, parent=0x93d25c0) at /var/tmp/portage/kde-base/powerdevil-4.3.4/work/powerdevil-4.3.4/powerdevil/daemon/PowerDevilDaemon.cpp:229
#14 0xb5f7931b in KPluginFactory::createInstance<PowerDevilDaemon, QObject> (parentWidget=0x0, parent=0x93d25c0, args=...) at /usr/include/KDE/../kpluginfactory.h:461
#15 0x41b52edf in KPluginFactory::create (this=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdecore/util/kpluginfactory.cpp:191
#16 0x410091b4 in KPluginFactory::create<KDEDModule> (this=<value optimized out>, s=<value optimized out>, onDemand=)
    at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdecore/util/kpluginfactory.h:491
#17 Kded::loadModule (this=<value optimized out>, s=<value optimized out>, onDemand=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kded/kded.cpp:380
#18 0x4100abe8 in Kded::initModules (this=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kded/kded.cpp:238
#19 0x4100cf4d in KDEDApplication::newInstance (this=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kded/kded.cpp:860
#20 0x424e6dd4 in KUniqueApplicationAdaptor::newInstance (this=<value optimized out>, asn_id=<value optimized out>, args=)
    at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kuniqueapplication.cpp:459
#21 0x424e757c in KUniqueApplicationAdaptor::qt_metacall (this=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kdeui/kuniqueapplication_p.moc:81
#22 0x414cce06 in QDBusConnectionPrivate::deliverCall (this=) at qdbusintegrator.cpp:904
#23 0x414cda65 in QDBusConnectionPrivate::activateCall (this=) at qdbusintegrator.cpp:809
#24 0x414ce356 in QDBusConnectionPrivate::activateObject (this=<value optimized out>, node=<value optimized out>, msg=<value optimized out>, pathStartPos=<value optimized out>)
    at qdbusintegrator.cpp:1368
#25 0x414ce628 in QDBusActivateObjectEvent::placeMetaCall (this=) at qdbusintegrator.cpp:1481
#26 0x421f0aff in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1252
#27 0x421df75b in QCoreApplication::event (this=) at kernel/qcoreapplication.cpp:1533
#28 0x466603a1 in QApplication::event (this=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:2344
#29 0x4665da5c in QApplicationPrivate::notify_helper (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:4242
#30 0x46666808 in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3661
#31 0x424df1a2 in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>)
    at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kdeui/kernel/kapplication.cpp:302
#32 0x421dfc8d in QCoreApplication::notifyInternal (this=) at kernel/qcoreapplication.cpp:704
#33 0x421e26da in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x93bbee0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x93bbee0) at kernel/qcoreapplication.cpp:1345
#35 0x421e283d in QCoreApplication::sendPostedEvents (receiver=) at kernel/qcoreapplication.cpp:1238
#36 0x4220d0ee in QCoreApplication::sendPostedEvents (s=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#37 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:276
#38 0x43cd1b9f in g_main_dispatch (context=) at gmain.c:1960
#39 IA__g_main_context_dispatch (context=) at gmain.c:2513
#40 0x43cd55b8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=) at gmain.c:2591
#41 0x43cd56df in IA__g_main_context_iteration (context=<value optimized out>, may_block=) at gmain.c:2654
#42 0x4220cbc2 in QEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#43 0x4670c1eb in QGuiEventDispatcherGlib::processEvents (this=) at kernel/qguieventdispatcher_glib.cpp:202
#44 0x421de24e in QEventLoop::processEvents (this=) at kernel/qeventloop.cpp:149
#45 0x421de6a9 in QEventLoop::exec (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:201
#46 0x421e290e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#47 0x4665db05 in QApplication::exec () at kernel/qapplication.cpp:3570
#48 0x4100b8e9 in kdemain (argc=) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4/kded/kded.cpp:936
#49 0x080486db in main (argc=1, argv=0xbff5b8d4) at /var/tmp/portage/kde-base/kdelibs-4.3.4/work/kdelibs-4.3.4_build/kded/kded4_dummy.cpp:3
Anyone else had this problem and know how to fix it?

Thanks in advance! :)
Last edited by Etal on Sun Dec 13, 2009 12:01 am, edited 1 time in total.
Top
Bigun
Advocate
Advocate
User avatar
Posts: 2198
Joined: Sun Sep 21, 2003 3:45 am
Contact:
Contact Bigun
Website

  • Quote

Post by Bigun » Wed Dec 02, 2009 3:57 pm

Have you ran revdep-rebuild?
"It's ok, they might have guns but we have flowers." - Perpetual Victim
Top
SamuliSuominen
Retired Dev
Retired Dev
Posts: 2133
Joined: Fri Sep 30, 2005 8:38 am
Location: Finland

  • Quote

Post by SamuliSuominen » Wed Dec 02, 2009 4:41 pm

Also try rebuilding kdelibs now after Qt-4.6 is installed...
Top
Etal
Veteran
Veteran
User avatar
Posts: 1932
Joined: Fri Jul 15, 2005 3:01 pm

  • Quote

Post by Etal » Wed Dec 02, 2009 5:22 pm

Bigun wrote:Have you ran revdep-rebuild?
revdep-rebuild does not pick up anything.
ssuominen wrote:Also try rebuilding kdelibs now after Qt-4.6 is installed...
I've actually updated Qt before updating KDE, so kdelibs were built against Qt 4.6.
Top
earendilion
Tux's lil' helper
Tux's lil' helper
Posts: 115
Joined: Mon Nov 26, 2007 1:58 pm
Location: Meudon (92), France

  • Quote

Post by earendilion » Wed Dec 02, 2009 8:23 pm

I also have a problem since my upgrade : http://forums.gentoo.org/viewtopic-p-6080119.html

I don't know if it's a segfault (I can launch krunner). All I have is a black screen or the wallpaper only. Nepomuk launches and tries to index files...

I also tried to rebuild @kdebase but nothing changed.

If you've got an idea ;)
Top
gcasillo
l33t
l33t
User avatar
Posts: 739
Joined: Tue Sep 23, 2003 9:21 pm
Location: Cincinnati, Ohio, USA

  • Quote

Post by gcasillo » Wed Dec 02, 2009 8:25 pm

No segfault here, but after an update and reboot, I've got kded4 using a whole lot of CPU:

Code: Select all

top - 15:22:35 up 4 min,  5 users,  load average: 1.07, 0.66, 0.27
Tasks: 173 total,   3 running, 170 sleeping,   0 stopped,   0 zombie
Cpu(s): 19.0%us,  8.9%sy,  0.0%ni, 72.1%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   8195824k total,   781032k used,  7414792k free,    18688k buffers
Swap:   987988k total,        0k used,   987988k free,   271844k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 2277 gregg     20   0  315m  24m  13m R  100  0.3   3:03.97 kded4
 2305 gregg     20   0  510m  50m  33m S    5  0.6   0:05.89 kwin
 1988 root      20   0  382m  54m  11m S    3  0.7   0:10.43 X
 2676 gregg     20   0  486m 145m  28m S    3  1.8   0:19.11 firefox
 2311 gregg     20   0  633m  47m  22m R    1  0.6   0:03.63 plasma-desktop
I've got a Core 2 Quad in this particular box. Another computer, a multi-purpose HTPC/file server, updated and does not have the same issue. Curious. I'm going to try rebuilding some stuff. Anyone else seeing a spike in CPU usage after this kde-4.3.4 update particularly with a process called "kded4?"
Top
Pond247
n00b
n00b
Posts: 22
Joined: Sun Jun 19, 2005 5:51 pm

  • Quote

Post by Pond247 » Wed Dec 02, 2009 8:36 pm

Same problem (kded4 and plasma crash) here.

Trying to restart them from console brings up the following message (repeated quite often before the crash happens):
QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.AccessDenied"
Top
yngwin
Retired Dev
Retired Dev
User avatar
Posts: 4572
Joined: Thu Dec 19, 2002 1:22 pm
Location: Suzhou, China

  • Quote

Post by yngwin » Wed Dec 02, 2009 8:43 pm

I've heard there are problems between plasma and hal-0.5.14. So downgrading hal might help.
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Top
earendilion
Tux's lil' helper
Tux's lil' helper
Posts: 115
Joined: Mon Nov 26, 2007 1:58 pm
Location: Meudon (92), France

  • Quote

Post by earendilion » Wed Dec 02, 2009 10:00 pm

I downgraded to hal 0.5.13 but it changed nothing...

Don't know if it's a good idea, but I launched X trough startx, then launched plasma-desktop from console and got that message :
could not access kephald, falling back to QDesktopWidget
adding an output 0 with geom: QRect(0,0 1680x1050)
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kconf_update.so
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kglobalaccel.so
QFont::setPointSize: Point size <= 0 (0), must be greater than 0
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
KCrash: Application 'plasma-desktop' crashing...
sock_file=/home/earendil/.kde4/socket-ithil/kdeinit4__0
kdeinit4: preparing to launch /usr/lib64/kde4/libexec/drkonqi
QDBusObjectPath: invalid path ""
kephald starting up
XRANDR error base: 161
RRInput mask is set!!
RandRScreen::loadSettings - adding mode: 69 1680 x 1050
RandRScreen::loadSettings - adding mode: 70 1680 x 1050
RandRScreen::loadSettings - adding mode: 71 1280 x 1024
RandRScreen::loadSettings - adding mode: 72 1280 x 1024
RandRScreen::loadSettings - adding mode: 73 1280 x 960
RandRScreen::loadSettings - adding mode: 74 1152 x 864
RandRScreen::loadSettings - adding mode: 75 1152 x 864
RandRScreen::loadSettings - adding mode: 76 1024 x 768
RandRScreen::loadSettings - adding mode: 77 1024 x 768
RandRScreen::loadSettings - adding mode: 78 1024 x 768
RandRScreen::loadSettings - adding mode: 79 832 x 624
RandRScreen::loadSettings - adding mode: 80 800 x 600
RandRScreen::loadSettings - adding mode: 81 800 x 600
RandRScreen::loadSettings - adding mode: 82 800 x 600
RandRScreen::loadSettings - adding mode: 83 800 x 600
RandRScreen::loadSettings - adding mode: 84 640 x 480
RandRScreen::loadSettings - adding mode: 85 640 x 480
RandRScreen::loadSettings - adding mode: 86 640 x 480
RandRScreen::loadSettings - adding mode: 87 640 x 480
RandRScreen::loadSettings - adding mode: 88 720 x 400
RandRScreen::loadSettings - adding crtc: 63
RandRScreen::loadSettings - adding crtc: 64
RandRScreen::loadSettings - adding output: 65
Setting CRTC 0 on output "DVI-D_1" (previous 0 )
RandRScreen::loadSettings - adding output: 66
Setting CRTC 0 on output "VGA_1" (previous 0 )
RandRScreen::loadSettings - adding output: 67
Setting CRTC 63 on output "DVI-I_2/digital" (previous 0 )
CRTC outputs: (67)

He seems not to be able to launch kephal, though it's installed, but maybe it's because I launch from another Desktop...

Any idea ?
Top
gami
Apprentice
Apprentice
Posts: 297
Joined: Fri Jun 02, 2006 12:32 am

  • Quote

Post by gami » Wed Dec 02, 2009 10:09 pm

I saw kded4 using 100% CPU right after updating. However, after killing kded4 and logging out and in again this issue seems to have solved itself...
Top
gcasillo
l33t
l33t
User avatar
Posts: 739
Joined: Tue Sep 23, 2003 9:21 pm
Location: Cincinnati, Ohio, USA

  • Quote

Post by gcasillo » Wed Dec 02, 2009 10:16 pm

gami wrote:I saw kded4 using 100% CPU right after updating. However, after killing kded4 and logging out and in again this issue seems to have solved itself...
Same as well for me. :)
Top
Etal
Veteran
Veteran
User avatar
Posts: 1932
Joined: Fri Jul 15, 2005 3:01 pm

  • Quote

Post by Etal » Wed Dec 02, 2009 10:44 pm

The HAL is not a problem because I had 0.5.13 when that happened (and I don't have hald start anyway).

What I've found is that if I create a new user, only KDED fails, so I deleted my plasma rc files and plasma now works.

And for KDED, looking at the backtrace, I figured that it was powerdevil-related, so I edited ~/.kde4/share/config/kdedrc and set Module-powerdevil autoload to false. Now KDED loads fine. (I did however find kded4 use up 100% CPU once today and I had to kill and restart it...)

So that's an interim solution to make KDE at least workable.
Top
Featherfoot
Veteran
Veteran
Posts: 1108
Joined: Sat Dec 28, 2002 10:55 pm
Location: Stuart, Florida

  • Quote

Post by Featherfoot » Thu Dec 03, 2009 1:12 am

Same problem here. Even when I logged out and back in again, my CPU graph shows big spikes every 10 seconds or so...
Top
lenk
Apprentice
Apprentice
User avatar
Posts: 211
Joined: Mon Mar 08, 2004 8:32 pm

  • Quote

Post by lenk » Thu Dec 03, 2009 3:08 am

Did you guys use optimized-qmake flag for qt-core-4.6.0?
E6300 Gigabyte GA-965P-DS3 2GB Corsair 320GB Seagate 7200.10 XFX 7600GT Gentoo
Dell M1330 T7500 2GB 160GB 13.3" WXGA Gentoo
Sharp Zaurus SL-C760 Cacko ROM 1.21b / pdaXrom 1.10rc5 512MB CF + 512MB SD
Sun Ultra5 Gentoo
Top
Featherfoot
Veteran
Veteran
Posts: 1108
Joined: Sat Dec 28, 2002 10:55 pm
Location: Stuart, Florida

  • Quote

Post by Featherfoot » Thu Dec 03, 2009 3:35 am

No. That is not the default.

Was I supposed to use it?
Top
earendilion
Tux's lil' helper
Tux's lil' helper
Posts: 115
Joined: Mon Nov 26, 2007 1:58 pm
Location: Meudon (92), France

  • Quote

Post by earendilion » Thu Dec 03, 2009 5:31 am

Ok so finally I have a segfault.

Looking at dmesg I get that :
drkonqi[3324]: segfault at 100000000 ip 00007f5ee3bc7562 sp 00007fffaa1e2810 error 6 in libQtGui.so.4.6.0[7f5ee37e2000+8c2000]
plasma-desktop[3325]: segfault at 100000000 ip 00007f0dc5481562 sp 00007fff1c5a0f30 error 6 in libQtGui.so.4.6.0[7f0dc509c000+8c2000]
I had to use a new version of GCC during the installation, so one part of Qt is compiled with GCC 4.3.4 and another with 4.4.2 : can it be that ?

[EDIT] SOLVED for me : recompiled every Qt package (to be sure) and everything works fine ;)
Top
PinguinoLoco
n00b
n00b
User avatar
Posts: 21
Joined: Wed Feb 04, 2009 4:21 pm

  • Quote

Post by PinguinoLoco » Thu Dec 03, 2009 1:19 pm

Downgrading dbus to version 1.2.3-r1 "fixed" the dbus-daemon erros in the log and crashes for me (kded4, plasma-desktop, dolphin). Not beautiful but a valid workaround until someone figures what is going on here.
Top
yngwin
Retired Dev
Retired Dev
User avatar
Posts: 4572
Joined: Thu Dec 19, 2002 1:22 pm
Location: Suzhou, China

  • Quote

Post by yngwin » Thu Dec 03, 2009 1:55 pm

lenk wrote:Did you guys use optimized-qmake flag for qt-core-4.6.0?
That would have no effect on runtime, so can't cause the errors here.
earendilion wrote:one part of Qt is compiled with GCC 4.3.4 and another with 4.4.2 : can it be that ?
That is indeed a big no-no, as qt-core's elog message says.
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Top
Qubit
Tux's lil' helper
Tux's lil' helper
Posts: 136
Joined: Mon Sep 23, 2002 2:59 pm
Location: /dev/urandom

  • Quote

Post by Qubit » Thu Dec 03, 2009 2:24 pm

Same here.

QT-4.6 / KDE-4.3.4

Deleted/Moved all

rm $(kde4-config --localprefix)share/config/plasma*

But it doesn't helped.

Regards Daniel
©Qubit
Top
guilc
Bodhisattva
Bodhisattva
User avatar
Posts: 3326
Joined: Sat Nov 15, 2003 5:32 pm
Location: Paris - France
Contact:
Contact guilc
Website

  • Quote

Post by guilc » Thu Dec 03, 2009 5:06 pm

yngwin wrote:I've heard there are problems between plasma and hal-0.5.14. So downgrading hal might help.
Hi,

For me this fixed the issue of plasma-desktop segfaulting. So back to hal 0.5.13-r2 !
Thanks !
Merci de respecter les règles du forum.

Mon site perso : https://www.xwing.info
Mon PORTDIR_OVERLAY : https://gentoo.xwing.info ou layman -a xwing
Top
Ken69267
Developer
Developer
User avatar
Posts: 111
Joined: Sun Apr 08, 2007 7:59 pm
Location: #gentoo-pr0n
Contact:
Contact Ken69267
Website

  • Quote

Post by Ken69267 » Thu Dec 03, 2009 6:01 pm

Downgrading to hal-0.5.13-r2 fixed plasma-desktop from crashing here as well
!snack
Top
krushia
n00b
n00b
Posts: 10
Joined: Thu May 10, 2007 6:32 pm

  • Quote

Post by krushia » Thu Dec 03, 2009 6:31 pm

If you have troubles with kded4 eating a CPU core after your second reboot, disabling notification sounds may fix it (did for me). See https://bugs.kde.org/show_bug.cgi?id=202744

Perhaps some buggy patch was merged into Qt mainline in 4.6.0? Dunno.
Top
platojones
Veteran
Veteran
User avatar
Posts: 1602
Joined: Wed Oct 23, 2002 10:48 pm
Location: Just over the horizon

  • Quote

Post by platojones » Thu Dec 03, 2009 7:03 pm

Weird...I haven't noticed this problem.
Top
OPelerin
Guru
Guru
User avatar
Posts: 354
Joined: Sat Jul 17, 2004 5:17 pm
Location: Belgium

  • Quote

Post by OPelerin » Thu Dec 03, 2009 8:47 pm

downgraded hal - plasma crash is gone.

akonadi still crash
Olivier PELERIN
Top
daseinhorn
Apprentice
Apprentice
User avatar
Posts: 150
Joined: Fri Jan 16, 2009 1:11 pm
Location: Canada

  • Quote

Post by daseinhorn » Thu Dec 03, 2009 10:09 pm

Downgrading hal also made it work for me.
Top
Post Reply
46 posts
  • 1
  • 2
  • Next

Return to “Desktop Environments”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic