Bug 161911 - Konqueror crash when load view profile
Summary: Konqueror crash when load view profile
Status: RESOLVED DUPLICATE of bug 155656
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.0.4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-10 18:35 UTC by IgnorantGuru
Modified: 2008-06-04 09:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash obtained by running "konqueror --profile midnightcommander" (2.68 KB, text/plain)
2008-06-04 02:27 UTC, Rui G.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description IgnorantGuru 2008-05-10 18:35:35 UTC
Version:            (using KDE 4.0.3)
Installed from:    Ubuntu Packages
Compiler:          kubuntu-kde4-8.04-alternate-i386.iso 
OS:                Linux

Attempting to load any Konqueror view profile other than Web Browsing results in a crash.  This occurs with unmodified view profiles (Midnight Commander), profiles I have modified by saving them (File Management), and a custom view profile I created.  The crash occurs using Settings | Load View Profile..., as well as attempting to load the view profile from the command line.  It crashes almost 100% of the time, but I have seen it load a view profile successfully one time for no discernible reason.

I also used the Kubuntu upgrade package to KDE 4.0.4 and got the same results (although KDE still reported itself as 4.0.3 after the successful upgrade, so I'm not certain which version it's now using).

This looks like this bug report which was closed at 4.0.0...
http://bugs.kde.org/show_bug.cgi?id=155559

The first three backtraces below (some using menu, some from the command line) are from KDE 4.0.3.  The last one is from KDE 4.0.4 (assuming the upgrade worked)...

(no debugging symbols found)   [multiple lines]
[Thread debugging using libthread_db enabled]
[New Thread 0xb64af720 (LWP 5876)]
(no debugging symbols found)   [multiple lines]
0xb7f9e410 in __kernel_vsyscall ()
[Current thread is 0 (process 5876)]

Thread 1 (Thread 0xb64af720 (LWP 5876)):
#0  0xb7f9e410 in __kernel_vsyscall ()
#1  0xb7e0dc90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7e0dac7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb79027d0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xb7f9e410 in __kernel_vsyscall ()

-------------------------------------------------------------------------------

(no debugging symbols found)   [multiple lines]
[Thread debugging using libthread_db enabled]
[New Thread 0xb6434720 (LWP 5984)]
(no debugging symbols found)   [multiple lines]
0xb7f23410 in __kernel_vsyscall ()
[Current thread is 0 (process 5984)]

Thread 1 (Thread 0xb6434720 (LWP 5984)):
#0  0xb7f23410 in __kernel_vsyscall ()
#1  0xb7d92c90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7d92ac7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb78877d0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xb7f23410 in __kernel_vsyscall ()

------------------------------------------------------------------------------

(no debugging symbols found)   [multiple lines]
[Thread debugging using libthread_db enabled]
[New Thread 0xb64b6720 (LWP 5998)]
(no debugging symbols found)   [multiple lines]
0xb7fa5410 in __kernel_vsyscall ()
[Current thread is 0 (process 5998)]

Thread 1 (Thread 0xb64b6720 (LWP 5998)):
#0  0xb7fa5410 in __kernel_vsyscall ()
#1  0xb7e14c90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7e14ac7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb79097d0 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xb7fa5410 in __kernel_vsyscall ()

-----------------------------------------------------------------------------

(no debugging symbols found)   [multiple lines]
[Thread debugging using libthread_db enabled]
[New Thread 0xb60c9720 (LWP 5876)]
(no debugging symbols found)   [multiple lines]
0xb7efa410 in __kernel_vsyscall ()
[Current thread is 0 (process 5876)]

Thread 1 (Thread 0xb60c9720 (LWP 5876)):
#0  0xb7efa410 in __kernel_vsyscall ()
#1  0xb7d69c90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7d69ac7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7798910 in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xb7efa410 in __kernel_vsyscall ()
Comment 1 A. Spehr 2008-05-13 08:08:52 UTC
I can't confirm with 4.0 branch svn r802901 (~4.0.4?)
Could this be a distro thing? Can other people test this, please?
Comment 2 IgnorantGuru 2008-05-13 18:07:00 UTC
I posted about this on Kubuntu forums and no one there seemed to experience this crash, even with the same distro and updates.  I had a fresh install from the alternate (text) installer.  I disabled Javascript and Java in Konqueror's options, then added some tabs to the file manager, and saved a profile.  The first time I tried to load a view profile I got the crash, and it has been very consistent since (just occassionally it will load a single profile successfully, but then will begin crashing after that).

If anyone has suggestions of further tests I can do I am willing to give it a try.
Comment 3 IgnorantGuru 2008-05-15 05:03:31 UTC
A little more info...

I formatted the partition and did a fresh install.  Made the following changes: installed nvidia driver; copied my xorg.conf from feisty; did the updates recommended by adept_notifier (41 packages); rebooted; did a full upgrade to KDE 4.0.4 from Adept (using 'unsupported' repository per http://kubuntu.org/announcements/kde-4.0.4.php ).

I then tried Konqueror, without changing any settings in it or elsewhere.  I was able to load the default 'File Management' view profile multiple times without it crashing (though it did not look right the first time it was loaded (did not display folders), only the second).  Midnight Commander view profile crashed on every try.

I then loaded the File Management view profile and added a tab.  With two tabs showing (both containing the home folder), I saved the 'File Management' view profile.

I then restarted Konqueror (web browser).  I loaded the File Management view profile.  The window closed and a new one opened.  It did contain two tabs, but one was simply blank (no title, no contents).  The other contained the 'Conquer Your Desktop' page.  (IOW, neither tab contained the home folder as the view profile had been saved.)  I then tried to load the File Management view profile a second time (without restarting Konqueror), and it crashed.  This behavior was consistent - it would load the view profile on the first try (showing the wrong folders in the tabs), and would crash the second time it was loaded.

Attempting to load the File Management view profile from the command line caused it to crash immediately.
Comment 4 Balachandran Chandrasekharan 2008-05-18 11:41:10 UTC
I can confirm the bug on my Debian experimental:

konqueror -v:

Qt: 4.4.0-rc1
KDE: 4.00.72 (KDE 4.0.72 >= 20080430
Konqueror: 4.00.68 (KDE 4.0.68 >= 20080402)



konqueror --profile midnightcommander:

konqueror(30024) KonqUndoManager::populate:
ASSERT: "!childFrameList.isEmpty()" in file /build/buildd/kdebase-4.0.68+svn794641/apps/konqueror/src/konqmainwindow.cpp, line 4036
konqueror(30024) Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive
konqueror(30024) Konsole::Profile::~Profile: Destroying profile  "Shell"
Comment 5 Rui G. 2008-06-04 02:27:50 UTC
Created attachment 25102 [details]
crash obtained by running "konqueror --profile midnightcommander"

I confirm this bug in trunk r816330 (qt 4.4.0). It's not a debian thing because
it is also crashing in Arch.
Comment 6 Tommi Tervo 2008-06-04 09:51:35 UTC

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