By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1037 - [REGRESSION] Konqueror crashes when opening the navigation panel
Summary: [REGRESSION] Konqueror crashes when opening the navigation panel
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 critical
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 892
  Show dependency tree / graph
 
Reported: 2012-06-14 13:30 CDT by Julius Schwartzenberg
Modified: 2012-06-27 03:44 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julius Schwartzenberg 2012-06-14 13:30:47 CDT 
The navigation panel doesn't display in Konqueror anymore on Precise with the latest nightlies. Trying to open it manually causes Konqueror to crash.

Backtrace:
passprompt
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash handler]
#5  0xffffffffffffffb0 in ?? ()
#6  0x00007fa4ff1f32e5 in Sidebar_Widget::Sidebar_Widget(TQWidget*, KParts::ReadOnlyPart*, char const*, bool, TQString const&) () from /opt/trinity/lib/trinity/konq_sidebar.so
#7  0x00007fa4ff1ee56c in ?? () from /opt/trinity/lib/trinity/konq_sidebar.so
#8  0x00007fa4ff1eec03 in ?? () from /opt/trinity/lib/trinity/konq_sidebar.so
#9  0x00007fa50b2700c6 in KParts::Factory::createPart(TQWidget*, char const*, TQObject*, char const*, char const*, TQStringList const&) () from /opt/trinity/lib/libkparts.so.2
#10 0x00007fa502b82ca5 in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#11 0x00007fa502b74f03 in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#12 0x00007fa502b596b8 in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#13 0x00007fa502b5a395 in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#14 0x00007fa502b98cf5 in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#15 0x00007fa502bbafbf in ?? () from /opt/trinity/lib/libtdeinit_konqueror.so
#16 0x00007fa509dcb46f in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /usr/lib/libtqt-mt.so.3
#17 0x00007fa509dcba77 in TQObject::activate_signal_bool(int, bool) () from /usr/lib/libtqt-mt.so.3
#18 0x00007fa508ab482b in KAction::slotPopupActivated() () from /opt/trinity/lib/libtdeui.so.4
#19 0x00007fa508ab4ba8 in KAction::tqt_invoke(int, TQUObject*) () from /opt/trinity/lib/libtdeui.so.4
#20 0x00007fa509dcb46f in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /usr/lib/libtqt-mt.so.3
#21 0x00007fa50a075e0d in TQSignal::signal(TQVariant const&) () from /usr/lib/libtqt-mt.so.3
#22 0x00007fa509ddf2d5 in TQSignal::activate() () from /usr/lib/libtqt-mt.so.3
#23 0x00007fa509ea1ebf in TQPopupMenu::mouseReleaseEvent(TQMouseEvent*) () from /usr/lib/libtqt-mt.so.3
#24 0x00007fa509df5153 in TQWidget::event(TQEvent*) () from /usr/lib/libtqt-mt.so.3
#25 0x00007fa509d799ad in TQApplication::internalNotify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#26 0x00007fa509d7a0b3 in TQApplication::notify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#27 0x00007fa50a563b29 in KApplication::notify(TQObject*, TQEvent*) () from /opt/trinity/lib/libtdecore.so.4
#28 0x00007fa509d254e0 in ?? () from /usr/lib/libtqt-mt.so.3
#29 0x00007fa509d2430f in TQApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libtqt-mt.so.3
#30 0x00007fa509d32c37 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3
#31 0x00007fa509d8b099 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3
#32 0x00007fa509ea2c75 in TQPopupMenu::exec(TQPoint const&, int) () from /usr/lib/libtqt-mt.so.3
#33 0x00007fa509ec488a in TQToolButton::popupTimerDone() () from /usr/lib/libtqt-mt.so.3
#34 0x00007fa50a08e2f8 in TQToolButton::tqt_invoke(int, TQUObject*) () from /usr/lib/libtqt-mt.so.3
#35 0x00007fa509dcb46f in TQObject::activate_signal(TQConnectionList*, TQUObject*) () from /usr/lib/libtqt-mt.so.3
#36 0x00007fa509dcb547 in TQObject::activate_signal(int) () from /usr/lib/libtqt-mt.so.3
#37 0x00007fa509de49fe in TQTimer::event(TQEvent*) () from /usr/lib/libtqt-mt.so.3
#38 0x00007fa509d799ad in TQApplication::internalNotify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#39 0x00007fa509d79b6e in TQApplication::notify(TQObject*, TQEvent*) () from /usr/lib/libtqt-mt.so.3
#40 0x00007fa50a563b29 in KApplication::notify(TQObject*, TQEvent*) () from /opt/trinity/lib/libtdecore.so.4
#41 0x00007fa509d7036e in TQEventLoop::activateTimers() () from /usr/lib/libtqt-mt.so.3
#42 0x00007fa509d337a3 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3
#43 0x00007fa509d8b099 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3
#44 0x00007fa509d8b022 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3
#45 0x00007fa502b425c4 in kdemain () from /opt/trinity/lib/libtdeinit_konqueror.so
#46 0x00007fa502e1668c in tdeinitmain () from /opt/trinity/lib/trinity/konqueror.so
#47 0x0000000000408665 in _start ()
Comment 1 Darrell 2012-06-14 19:24:03 CDT 
Just in case this related to the recent XDG updates, would you please backup or
temporarily rename your $TDEHOME directory ($HOME/.trinity) and then restart
Trinity to force creating a new $TDEHOME profile directory? Then try accessing the konqueror navigation panel.

A missing navigation panel is one of the quirks a user will see in an existing profile, when the profile *.desktop files have not been updated correctly through starttde.

Please perform the following against your existing $TDEHOME profile:

find $HOME/.trinity -name "*.desktop" -exec sed -i 's|X-KDE-|X-TDE-|g' {} \;

find $HOME/.trinity -name "*.desktop" -exec sed -i 's|KDE\;|TDE\;|g' {} \;

In the updated starttde, the script needs to know the $TDEHOME and $tdehome variables. If those variables are unknown then the starrtde changes are not being executed and hence, the profile is not being updated to synchronize with the XDG changes.
Comment 2 Julius Schwartzenberg 2012-06-15 16:35:28 CDT 
With a hacked starttde (added -H) and after resetting the config option from true to false, restarting Trinity fixed this issue. I'll close this one as it is not a new problem.

*** This bug has been marked as a duplicate of bug 892 ***
Comment 3 Darrell 2012-06-15 17:12:47 CDT 
Thanks Julius!

I have an updated starttde that I will soon attach to bug report 892. I added:

* Error checking against sym linked profile directories (a corner case but needed).

* Usage of a verbose X message box to warn about the sym link, why an R14 XDG update will not occur, what fails to function properly because of that lack of update, and possible remedies for the user.

* Nominal validation tests that the updates succeeded. When failures are detected then an X message box appears for each type of failure, thereby informing the user specifically what needs repairs.

I have not yet but will split the R14 XDG updates to a new script.

I am updating the migratekde3 script (bug report 709). That script will run the new R14 XDG update script too.

I have been testing all afternoon. :-)

Results:

Had these changes been in place you would have been informed sufficiently what had failed and offered remedies to fix. :-)

Yes, I'll be asking you to test. :-)
Comment 4 Julius Schwartzenberg 2012-06-27 03:44:11 CDT 
This was fixed in a recent update. (I guess the XDG changes were only partly in the nightlies for a while.)