Version: 4.1.4 (using KDE 4.1.4) OS: Linux Installed from: Fedora RPMs Application: Desktop Sharing (krfb), signal SIGSEGV [Current thread is 1 (Thread 0xb8093770 (LWP 3670))] Thread 1 (Thread 0xb8093770 (LWP 3670)): [KCrash Handler] #6 0x061f423d in QNetworkAddressEntry::ip () from /usr/lib/libQtNetwork.so.4 #7 0x08054ae8 in _start () steps to reproduce: 1.open up krfb 2.select create email invitation 3.look at Crash box that pops up!
As 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? Thanks :)
Created attachment 30963 [details] Krfb crash backtrace Krfb backtrace
The backtrace is the same as the first one. Have you installed libqt4-debuginfo and kdenetwork-debuginfo packages? Thanks
Application: Desktop Sharing (krfb), signal SIGSEGV [Current thread is 1 (Thread 0xb7f51770 (LWP 9569))] Thread 1 (Thread 0xb7f51770 (LWP 9569)): [KCrash Handler] #6 0x06f4723d in QNetworkAddressEntry::ip () from /usr/lib/libQtNetwork.so.4 #7 0x08054ae8 in ManageInvitationsDialog::inviteByMail (this=0xbf874654) at /usr/src/debug/kdenetwork-4.1.4/krfb/manageinvitationsdialog.cpp:134 #8 0x08055268 in ManageInvitationsDialog::qt_metacall (this=0xbf874654, _c=QMetaObject::InvokeMetaMethod, _id=4129, _a=0xbf87373c) at /usr/src/debug/kdenetwork-4.1.4/i386-redhat-linux-gnu/krfb/manageinvitationsdialog.moc:78 #9 0x0053bdf0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0x0053c1f0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0x03502791 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #12 0x03255ae9 in ?? () from /usr/lib/libQtGui.so.4 #13 0x032576c4 in ?? () from /usr/lib/libQtGui.so.4 #14 0x03257956 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #15 0x02f6d6f2 in QWidget::event () from /usr/lib/libQtGui.so.4 #16 0x0325598e in QAbstractButton::event () from /usr/lib/libQtGui.so.4 #17 0x032fc240 in QPushButton::event () from /usr/lib/libQtGui.so.4 #18 0x02f1568c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #19 0x02f1de81 in QApplication::notify () from /usr/lib/libQtGui.so.4 #20 0x028fe72d in KApplication::notify () from /usr/lib/libkdeui.so.5 #21 0x005271c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #22 0x02f1d10e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #23 0x02f87456 in ?? () from /usr/lib/libQtGui.so.4 #24 0x02f867e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #25 0x02faee1a in ?? () from /usr/lib/libQtGui.so.4 #26 0x008e7238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #27 0x008ea8e3 in ?? () from /lib/libglib-2.0.so.0 #28 0x008eaaa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #29 0x005517f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #30 0x02fae515 in ?? () from /usr/lib/libQtGui.so.4 #31 0x0052588a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #32 0x00525a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #33 0x00528105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #34 0x02f15507 in QApplication::exec () from /usr/lib/libQtGui.so.4 #35 0x08050d15 in main (argc=5, argv=0xbf874834) at /usr/src/debug/kdenetwork-4.1.4/krfb/main.cpp:103 Sorry, this backtrace is with the packages requested installed.
The last one is a lot better. Thanks!
If you need anything else, just let me know! :)
Can you post the output of the shell command "ifconfig" ? Thanks
I'm not quite sure what this has to do with the bug itself but heres what you requested: eth0 Link encap:Ethernet HWaddr 00:16:36:37:98:57 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:884 errors:0 dropped:0 overruns:0 frame:0 TX packets:884 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:99331 (97.0 KiB) TX bytes:99331 (97.0 KiB) pan0 Link encap:Ethernet HWaddr 16:FD:99:6A:27:B6 inet6 addr: fe80::14fd:99ff:fe6a:27b6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) virbr0 Link encap:Ethernet HWaddr 56:B8:65:FA:14:B6 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::54b8:65ff:fefa:14b6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:7566 (7.3 KiB) wlan0 Link encap:Ethernet HWaddr 00:13:02:6C:62:A6 inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::213:2ff:fe6c:62a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:219230 errors:0 dropped:0 overruns:0 frame:0 TX packets:144187 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:251261620 (239.6 MiB) TX bytes:14473742 (13.8 MiB) wmaster0 Link encap:UNSPEC HWaddr 00-13-02-6C-62-A6-F4-7F-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
The application is crashing on fetching the IP of a network interface (to later send it in the invitation email). So I thought you may have some different network interface and that case wasn't properly handled (and therefore it crashes)
I can confirm this bug in krfb 4.1.2. Exact same symptoms as described above.
*** Bug 207029 has been marked as a duplicate of this bug. ***
Bug 207029 (duplicate of this one) also contains some very useful information for debugging this issue. Bumping the priority of this report so I remember to get it fixed soon :)
Created attachment 36976 [details] Attempt 1 at narrowing down the crash cause No matter what I do, I can't reproduce this bug :( I've looked at the line of code concerned, and come up with a possible patch that might help diagnose the problem some more. Can anyone who can reproduce this bug recompile krfb with this patch and then trigger the crash again and paste a new backtrace?
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!