Bug 195024 - Default KDE Network Management Control Module shows no connections, even though there are. Manually creating one crashes.
Summary: Default KDE Network Management Control Module shows no connections, even thou...
Status: RESOLVED DUPLICATE of bug 192957
Alias: None
Product: Network Management
Classification: Unmaintained
Component: Plasma Widget (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-02 21:30 UTC by Kyle Jones
Modified: 2009-07-31 19:38 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle Jones 2009-06-02 21:30:15 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-6-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Default KDE Network Management Control Module shows no existing network connections, even though there are and they are active. Manually creating one crashes the Control Module. Reproduceable every time. This is on Kubuntu Karmic daily x64 with latest repo builds. Installing debug libs now and will update bug with backtraces once they are installed. 

Note, this is originally a Ubuntu Karmic x64 install with KDE installed along-side GDM using apt-get install kubuntu-desktop. Shouldn't matter though, running multiple desktop managers isn't out of the ordinary. 

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

Thread 2 (Thread 0x7f42921f1950 (LWP 13002)):
#0  0x00007f42abb372e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f42b127d83b in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x00007f42ae033d1c in ?? () from /usr/lib/libQtNetwork.so.4
#3  0x00007f42b127c781 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f42abb333ba in start_thread () from /lib/libpthread.so.0
#5  0x00007f42b40ed0bd in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f42b46dd7a0 (LWP 13001)):
[KCrash Handler]
#5  0x00007f42b408b378 in memcpy () from /lib/libc.so.6
#6  0x00007f42b12a0c9d in QListData::detach2 () from /usr/lib/libQtCore.so.4
#7  0x00007f4295696b63 in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so
#8  0x00007f4295695aaf in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so
#9  0x00007f42956a725c in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so
#10 0x00007f42956a4b5f in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so
#11 0x0000000000000000 in ?? ()
Comment 1 Will Stephenson 2009-07-23 08:30:06 UTC
Where is the full backtrace you offered?

You're right about display managers - it makes no odds here.
Comment 2 Will Stephenson 2009-07-31 19:38:02 UTC
Guessing that it's a dupe of this since there is no backtrace.

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