Bug 165577 - konqueror got sigsev in file browser superuser mode
Summary: konqueror got sigsev in file browser superuser mode
Status: RESOLVED DUPLICATE of bug 162364
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.0.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-02 16:03 UTC by Ed Kenny
Modified: 2008-07-10 22:02 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 Ed Kenny 2008-07-02 16:03:16 UTC
Version:           4.05 (using KDE 4.0.5)
Installed from:    Fedora RPMs
OS:                Linux

select item from drop down and app gets a sigsev --- signal 11.

here is data frm crash

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ef7720 (LWP 5123)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00809b1d in ?? () from /usr/lib/libkdeinit4_konqueror.so
#6  0x0082a568 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#7  0x022e8e67 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#8  0x022e9c22 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0x0075beb7 in ?? () from /usr/lib/kde4/dolphinpart.so
#10 0x0075deeb in ?? () from /usr/lib/kde4/dolphinpart.so
#11 0x022e8e67 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0x022e9c22 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0x008a3357 in DolphinView::modeChanged ()
   from /usr/lib/libdolphinprivate.so.4
#14 0x008a4856 in DolphinView::applyViewProperties ()
   from /usr/lib/libdolphinprivate.so.4
#15 0x008a6382 in DolphinView::updateView ()
   from /usr/lib/libdolphinprivate.so.4
#16 0x008a6448 in DolphinView::setUrl () from /usr/lib/libdolphinprivate.so.4
#17 0x0075cd31 in ?? () from /usr/lib/kde4/dolphinpart.so
#18 0x007d892e in ?? () from /usr/lib/libkdeinit4_konqueror.so
#19 0x00817ff3 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#20 0x007dfcf3 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#21 0x007deaaf in ?? () from /usr/lib/libkdeinit4_konqueror.so
#22 0x007de6ee in ?? () from /usr/lib/libkdeinit4_konqueror.so
#23 0x007dfeec in ?? () from /usr/lib/libkdeinit4_konqueror.so
#24 0x007e0f31 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#25 0x007e14f4 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#26 0x007e4431 in ?? () from /usr/lib/libkdeinit4_konqueror.so
#27 0x0084a82c in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#28 0x08048792 in _start ()
Comment 1 FiNeX 2008-07-02 17:12:44 UTC
"no debugging symbols found" means that the backtrace is not useful. If you can reproduce the crash, you should install the debug enabled packages before providing again the backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports


Thanks!


P.S: could you explain better how to reproduce the crash?

Comment 2 Ed Kenny 2008-07-02 17:37:01 UTC
I'll try to install debug package. I've never done it, so if yiu have suggestions I am open to them.

I am running fedora 9 with latest kernel

As a regular user I select the menu:

System___>More Applictions --->File Manager - Super User Mode

The system prompts for the root password 

Type the password -- authentication screen closes and the KDE Crash Handler appears.

Let me know if you need more. I heve played with UNIX for 25 years and I have no problem getting around -- I'm just new to fedora linux.

Thanks
Ed

-----Original Message-----
From: owner@bugs.kde.org [mailto:owner@bugs.kde.org] On Behalf Of FiNeX
Sent: Wednesday, July 02, 2008 10:13 AM
To: ekkenny@sbcglobal.net
Subject: [Bug 165577] konqueror got sigsev in file browser superuser mode 

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=165577         




------- Additional Comments From finex finex org  2008-07-02 17:12 -------
"no debugging symbols found" means that the backtrace is not useful. If you can reproduce the crash, you should install the debug enabled packages before providing again the backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports


Thanks!


P.S: could you explain better how to reproduce the crash?
Comment 3 Frank Reininghaus 2008-07-10 18:38:27 UTC
Both the backtrace and the description seem to match a bug reported earlier, so I'm marking this as duplicate (feel free to reopen if I'm wrong).

Ed, if you have debugging packages installed now, please paste a backtrace in the other report. Thanks!

*** This bug has been marked as a duplicate of 162364 ***
Comment 4 Ed Kenny 2008-07-10 22:02:30 UTC
Frank,

Workload was very bad this week. I'll try to install the debug version this weekend.

Ed

-----Original Message-----
From: owner@bugs.kde.org [mailto:owner@bugs.kde.org] On Behalf Of Frank Reininghaus
Sent: Thursday, July 10, 2008 11:38 AM
To: ekkenny@sbcglobal.net
Subject: [Bug 165577] konqueror got sigsev in file browser superuser mode 

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=165577         
frank78ac googlemail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |frank78ac googlemail com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE
            Version|3.5                         |4.0.4



------- Additional Comments From frank78ac googlemail com  2008-07-10 18:38 -------
Both the backtrace and the description seem to match a bug reported earlier, so I'm marking this as duplicate (feel free to reopen if I'm wrong).

Ed, if you have debugging packages installed now, please paste a backtrace in the other report. Thanks!

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