Bug 222692 - plasma-desktop crash mounting usb volume
Summary: plasma-desktop crash mounting usb volume
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-systemmonitor (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 12:34 UTC by michael.vogl
Modified: 2010-01-20 04:40 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description michael.vogl 2010-01-14 12:34:49 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
When trying to mount an external drive from the device notifyer the desktop crashes.
The device gets mountet and the dolphin window shows but the rest of the desktop is gone.
The device is a mobile phone ( Samsung Galaxy running Android )

It's probably related to the name of the volume since it shows up as 
"/media/_PNG???"

mount says:
/dev/sdc on /media/_PNG
▒ type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,utf8,shortname=mixed,flush)

Hex editor says:_PNG... is 5F 50 4E 47 0D 0A 1A

Looks like there is a CR+LF in the Volume name?????

mountig the volume manually from the command line to /media/phome works without crash.



 -- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7806700 (LWP 2756))]

Thread 2 (Thread 0xac5a7b70 (LWP 2759)):
#0  0x0030c422 in __kernel_vsyscall ()
#1  0x00264e15 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122
#2  0x00ac587d in __pthread_cond_wait (cond=0xa5704c8, mutex=0xa5704b0) at forward.c:139
#3  0x00cece67 in QWaitConditionPrivate::wait (this=0xa356300, mutex=0xa3562fc, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xa356300, mutex=0xa3562fc, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x0133b922 in QHostInfoAgent::run (this=0xa3562f0) at kernel/qhostinfo.cpp:260
#6  0x00cebe32 in QThreadPrivate::start (arg=0xa3562f0) at thread/qthread_unix.cpp:188
#7  0x0026080e in start_thread (arg=0xac5a7b70) at pthread_create.c:300
#8  0x00ab88de in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7806700 (LWP 2756)):
[KCrash Handler]
#6  QBasicAtomicInt::ref (x=0xbfb22ae0, copy=0xd2f9248) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120
#7  QByteArray (x=0xbfb22ae0, copy=0xd2f9248) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:414
#8  QBitArray (x=0xbfb22ae0, copy=0xd2f9248) at ../../include/QtCore/../../src/corelib/tools/qbitarray.h:64
#9  v_construct<QBitArray> (x=0xbfb22ae0, copy=0xd2f9248) at ../../include/QtCore/private/../../../src/corelib/kernel/qvariant_p.h:104
#10 construct (x=0xbfb22ae0, copy=0xd2f9248) at kernel/qvariant.cpp:131
#11 0x04e0b490 in construct (x=0xbfb22ae0, copy=0xd2f9248) at kernel/qguivariant.cpp:152
#12 0x00df98af in QVariant::create (this=0xbfb22ae0, type=10, copy=0xd2f9248) at kernel/qvariant.cpp:1343
#13 0x00df9e92 in QVariant (this=0xbfb22ae0, val=...) at kernel/qvariant.cpp:1627
#14 0x068d8e6e in SystemMonitorEngine::answerReceived (this=0xa632f90, id=-1, answer=...) at ../../../../plasma/dataengines/systemmonitor/systemmonitor.cpp:131
#15 0x092d6532 in KSGRD::SensorAgent::processAnswer (this=0xa6137d0, 
    buf=0xd2ca0d8 "acpi/battery/0/batterycharge\tinteger\nacpi/battery/0/batteryusage\tinteger\nacpi/thermal_zone/TZS1/temperature\tinteger\nacpi/thermal_zone/TZS0/temperature\tinteger\nsystem/processors\tinteger\nsystem/cores\tin"..., buflen=24581) at ../../../../ksysguard/gui/ksgrd/SensorAgent.cc:184
#16 0x092de97b in KSGRD::SensorShellAgent::msgRcvd (this=0xa6137d0) at ../../../../ksysguard/gui/ksgrd/SensorShellAgent.cc:91
#17 0x092e000f in KSGRD::SensorShellAgent::qt_metacall (this=0xa6137d0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb22dac) at ./SensorShellAgent.moc:72
#18 0x00df2263 in QMetaObject::activate (sender=0xa624b30, from_signal_index=13, to_signal_index=13, argv=0x0) at kernel/qobject.cpp:3113
#19 0x00df2ec2 in QMetaObject::activate (sender=0xa624b30, m=0xecbe8c, local_signal_index=5, argv=0x0) at kernel/qobject.cpp:3187
#20 0x00d79e97 in QProcess::readyReadStandardOutput (this=0xa624b30) at .moc/release-shared/moc_qprocess.cpp:156
#21 0x00d7ca0a in QProcessPrivate::_q_canReadStandardOutput (this=0xa6323b8) at io/qprocess.cpp:564
#22 0x00d7fc56 in QProcess::qt_metacall (this=0xa624b30, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb22fa8) at .moc/release-shared/moc_qprocess.cpp:101
#23 0x0086860a in KProcess::qt_metacall (this=0xa624b30, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbfb22fa8) at ./kprocess.moc:63
#24 0x00df2263 in QMetaObject::activate (sender=0xa632580, from_signal_index=4, to_signal_index=4, argv=0xbfb22fa8) at kernel/qobject.cpp:3113
#25 0x00df2ec2 in QMetaObject::activate (sender=0xa632580, m=0xecd8b0, local_signal_index=0, argv=0xbfb22fa8) at kernel/qobject.cpp:3187
#26 0x00e2c503 in QSocketNotifier::activated (this=0xa632580, _t1=21) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#27 0x00df6c87 in QSocketNotifier::event (this=0xa632580, e=0xbfb23364) at kernel/qsocketnotifier.cpp:316
#28 0x04dcaf54 in QApplicationPrivate::notify_helper (this=0xa009170, receiver=0xa632580, e=0xbfb23364) at kernel/qapplication.cpp:4056
#29 0x04dd267c in QApplication::notify (this=0x9fe2308, receiver=0xa632580, e=0xbfb23364) at kernel/qapplication.cpp:3603
#30 0x011011aa in KApplication::notify (this=0x9fe2308, receiver=0xa632580, event=0xbfb23364) at ../../kdeui/kernel/kapplication.cpp:302
#31 0x00ddc6cb in QCoreApplication::notifyInternal (this=0x9fe2308, receiver=0xa632580, event=0xbfb23364) at kernel/qcoreapplication.cpp:610
#32 0x00e072ca in QCoreApplication::sendEvent (source=0xa00b310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#33 socketNotifierSourceDispatch (source=0xa00b310) at kernel/qeventdispatcher_glib.cpp:110
#34 0x00b69e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#35 0x00b6d730 in ?? () from /lib/libglib-2.0.so.0
#36 0x00b6d863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#37 0x00e0702c in QEventDispatcherGlib::processEvents (this=0xa008f60, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#38 0x04e6bbe5 in QGuiEventDispatcherGlib::processEvents (this=0xa008f60, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#39 0x00ddac79 in QEventLoop::processEvents (this=0xbfb23604, flags=) at kernel/qeventloop.cpp:149
#40 0x00ddb0ca in QEventLoop::exec (this=0xbfb23604, flags=...) at kernel/qeventloop.cpp:201
#41 0x00ddd53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#42 0x04dcadd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#43 0x091e580d in kdemain (argc=1, argv=0x9fcb8d8) at ../../../../plasma/shells/desktop/main.cpp:50
#44 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x9fae4e0 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x80511a5 "0") at ../../kinit/kinit.cpp:677
#45 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#46 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#47 0x0804fbaf in main (argc=2, argv=0xbfb23e64, envp=0xbfb23e70) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-18 21:43:14 UTC
Merging with bug 206049. Regards

*** This bug has been marked as a duplicate of bug 206049 ***
Comment 2 John Tapsell 2010-01-19 16:36:41 UTC
SVN commit 1077180 by johnflux:

Sanitize disk device names

Some people have device names like "_PNG\r\n" :-/
BUG:222692
BUGCC:206049

 M  +12 -0     diskstat.c  
 M  +12 -2     diskstats.c  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1077180
Comment 3 John Tapsell 2010-01-19 16:38:06 UTC
SVN commit 1077181 by johnflux:

Sanitize disk device names

Some people have device names like "_PNG\r\n" :-/
BUG:222692
BUGCC:206049

 M  +12 -0     diskstat.c  
 M  +12 -2     diskstats.c  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1077181
Comment 4 John Tapsell 2010-01-20 02:25:20 UTC
(committed twice - once for 4.4 and once for master (4.5). )
Comment 5 John Tapsell 2010-01-20 04:35:07 UTC
SVN commit 1077383 by johnflux:

Fix off-by-one error in systemmonitor data engine.

There is a check to see if we are in a consistent state.  However the
check is faulty, leading to engine trying to parse in an inconsistent
state, leading to a segmentation fault.

CCBUG:222692
CCBUG:206049

 M  +1 -1      systemmonitor.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1077383
Comment 6 John Tapsell 2010-01-20 04:40:28 UTC
SVN commit 1077388 by johnflux:

Fix off-by-one error in systemmonitor data engine.

There is a check to see if we are in a consistent state.  However the
check is faulty, leading to engine trying to parse in an inconsistent
state, leading to a segmentation fault.

CCBUG:222692
CCBUG:206049

 M  +1 -1      systemmonitor.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1077388