Bug 199011 - desktop pager crashes plasma
Summary: desktop pager crashes plasma
Status: RESOLVED DUPLICATE of bug 197717
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-pager (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-05 14:11 UTC by Andreas Pietzowski
Modified: 2009-07-06 00:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Pietzowski 2009-07-05 14:11:51 UTC
Version:            (using KDE 4.2.90)
Installed from:    Ubuntu Packages

Today I installed 4.3 RC1 and when I roll my mouse wheel in the pager widget it changes the desktop. But when you roll up and down the pager gets confused and all plasma crashes.

I hope you can reproduce this.
Comment 1 Dario Andres 2009-07-05 22:49:22 UTC
Here using:

Qt: 4.5.2 (KDE-Qt git commit 46a247a2c9a8c0c4456a02f6a0922d859d88fe76
        Date:   Fri Jun 26 13:45:37 2009 +0200)
KDE: 4.3.60 (KDE 4.3.60 (KDE 4.4 >= 20090624))
kdelibs svn rev. 989682 / kdebase svn rev. 989682
on ArchLinux i686 - Kernel 2.6.30

I can't reproduce the crash.

If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You may need to install the "kdebase-workspace-dbg" package. Thanks
Comment 2 Andreas Pietzowski 2009-07-05 23:11:08 UTC
Okay, the crash happens when you use the mouse wheel forward and backwad in a fast switch - up and down the wheel one or two times and back again. Can you reproduce it now? Try out stupid mouse wheel behavior.

I also installed the debug packages but the problem is, that I don't get an bug window from KDE when plasma crashes (I know the back trace dialog from all other apps). How can I get bugsteps from a crashing plasma?

Thanks
Comment 3 Dario Andres 2009-07-05 23:13:53 UTC
I can't reproduce, It may be fixed (or my different configuration isn't allowing me to reproduce it)

Try this:
- Open Konsole
- Type "kquitapp plasma-desktop" press Return
Plasma should close normally
- Type "plasma-desktop" and press Return
Plasma should restart
- Reproduce the crash
You should get the crash + the crash dialog

Thanks
Comment 4 Andreas Pietzowski 2009-07-06 00:33:07 UTC
OK, here it is:

Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 0 (LWP 23953)]

Thread 2 (Thread 0x7fe029e58950 (LWP 23954)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007fe04784a939 in QWaitCondition::wait (this=0x2f1f8f0, mutex=0x2f1f8e8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007fe04ae0e4cc in QHostInfoAgent::run (this=0x2f1f8d0) at kernel/qhostinfo.cpp:260
#3  0x00007fe047849952 in QThreadPrivate::start (arg=0x2f1f8d0) at thread/qthread_unix.cpp:189
#4  0x00007fe043fd63ba in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007fe046da6fcd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe04c405790 (LWP 23953)):
[KCrash Handler]
#4  TaskManager::GroupManager::manualSortingRequest (this=0x0, taskItem=0x2edf700, newIndex=0) at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/groupmanager.cpp:363
#5  0x00007fe02cf54b3a in TaskManager::AbstractGroupingStrategy::closeGroup (this=0x2edf670, group=0x370e7b0)
    at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/abstractgroupingstrategy.cpp:167
#6  0x00007fe02cf5bda8 in TaskManager::ProgramGroupingStrategy::checkGroup (this=0x2edf670) at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/strategies/programgroupingstrategy.cpp:204
#7  0x00007fe02cf5cc2d in TaskManager::ProgramGroupingStrategy::qt_metacall (this=0x2edf670, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=<value optimized out>)
    at /build/buildd/kdebase-workspace-4.2.95/obj-x86_64-linux-gnu/libs/taskmanager/programgroupingstrategy.moc:68
#8  0x00007fe0479481f2 in QMetaObject::activate (sender=0x370e7b0, from_signal_index=<value optimized out>, to_signal_index=22, argv=0x1) at kernel/qobject.cpp:3069
#9  0x00007fe02cf6da92 in TaskManager::TaskGroup::itemRemoved (this=0x0, _t1=0x2e20380) at /build/buildd/kdebase-workspace-4.2.95/obj-x86_64-linux-gnu/libs/taskmanager/taskgroup.moc:146
#10 0x00007fe02cf6e3b1 in TaskManager::TaskGroup::remove (this=0x370e7b0, item=0x2e20380) at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/taskgroup.cpp:182
#11 0x00007fe02cf56ed1 in TaskManager::GroupManagerPrivate::removeTask (this=0x2bd7310, task={d = 0x7fff54545ae0}) at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/groupmanager.cpp:311
#12 0x00007fe02cf5781e in TaskManager::GroupManagerPrivate::actuallyReloadTasks (this=0x2bd7310) at /build/buildd/kdebase-workspace-4.2.95/libs/taskmanager/groupmanager.cpp:164
#13 0x00007fe02cf59472 in TaskManager::GroupManager::qt_metacall (this=0x2c0e750, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff54545c60)
    at /build/buildd/kdebase-workspace-4.2.95/obj-x86_64-linux-gnu/libs/taskmanager/groupmanager.moc:108
#14 0x00007fe0479481f2 in QMetaObject::activate (sender=0x2bd7378, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x1) at kernel/qobject.cpp:3069
#15 0x00007fe0479424d3 in QObject::event (this=0x2bd7378, e=0x2edf700) at kernel/qobject.cpp:1082
#16 0x00007fe04807778d in QApplicationPrivate::notify_helper (this=0x25ead50, receiver=0x2bd7378, e=0x7fff54546310) at kernel/qapplication.cpp:4084
#17 0x00007fe04807f97a in QApplication::notify (this=0x25d3330, receiver=0x2bd7378, e=0x7fff54546310) at kernel/qapplication.cpp:4049
#18 0x00007fe04a74662b in KApplication::notify (this=0x25d3330, receiver=0x2bd7378, event=0x7fff54546310) at /build/buildd/kde4libs-4.2.95/kdeui/kernel/kapplication.cpp:302
#19 0x00007fe04793275c in QCoreApplication::notifyInternal (this=0x25d3330, receiver=0x2bd7378, event=0x7fff54546310) at kernel/qcoreapplication.cpp:602
#20 0x00007fe04795f7f6 in QTimerInfoList::activateTimers (this=0x25ee570) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0x00007fe04795bf0d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#22 0x00007fe0423a620a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x00007fe0423a98e0 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007fe0423a9a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0x00007fe04795be6f in QEventDispatcherGlib::processEvents (this=0x25bad80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#26 0x00007fe04810fbef in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#27 0x00007fe047931002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1414817152}) at kernel/qeventloop.cpp:149
#28 0x00007fe0479313cd in QEventLoop::exec (this=0x7fff545465c0, flags={i = 1414817232}) at kernel/qeventloop.cpp:200
#29 0x00007fe047933694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#30 0x00007fe04c0e063b in kdemain (argc=1, argv=0x7fff545468c8) at /build/buildd/kdebase-workspace-4.2.95/plasma/shells/desktop/main.cpp:50
#31 0x00007fe046cdf5a6 in __libc_start_main (main=0x400890 <main>, argc=1, ubp_av=0x7fff545468c8, init=0x4008c0 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff545468b8) at libc-start.c:220
#32 0x00000000004007c9 in _start () at ../sysdeps/x86_64/elf/start.S:113
Comment 5 Andreas Pietzowski 2009-07-06 00:35:58 UTC
Maybe it is just a matter of historical config files. I also had crashes when I upgraded from 4.2 to 4.3 but they disappeared when I removed all the config files. But this solution is annoying because I don't wanna reconfigure my desktop after every upgrade ;)

But I guess when I have this problem, others will have it too somewhere. Which config files would you suggest me to try out for removing? Maybe we can find the source of that fail.
Comment 6 Beat Wolf 2009-07-06 00:37:51 UTC

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