Bug 132996 - while shutting down the system with an open kdvi-window, a crash-info about kdvi(sigsev)is shown an the system waits for an action. The shutdown stops. No need for this.
Summary: while shutting down the system with an open kdvi-window, a crash-info about k...
Status: RESOLVED DUPLICATE of bug 122961
Alias: None
Product: kdvi
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Stefan Kebekus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-25 21:59 UTC by Matthias Borck-Elsner
Modified: 2006-08-29 18:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Borck-Elsner 2006-08-25 21:59:53 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

while shutting down the system with an open kdvi-window, a crash-info about kdvi(sigsev)is shown and the system waits for an action. The shutdown stops. No need for this.

Sometimes the system keeps running unnoticed.
Comment 1 Wilfried Huss 2006-08-26 11:06:34 UTC
Yes, there really is no need for a crash :-)

*** This bug has been marked as a duplicate of 122961 ***
Comment 2 Matthias Borck-Elsner 2006-08-26 19:30:59 UTC
Wollte sagen, es macht keinen Sinn, das Herunterfahren zu stoppen und
eine Bestätigung zu fordern für eine Crashmeldung die eh' nicht mehr
interessiert.

mbe

Am Samstag, den 26.08.2006, 09:06 +0000 schrieb Wilfried Huss:
[bugs.kde.org quoted mail]
Comment 3 Konrad Urlichs 2006-08-28 08:45:36 UTC
Here is the debugging info of the same crash I see when kdvi is shut down.
In my version of KDE, this bug is not resolved!
And I agree with Matthias: Crash reports on shutdown, which stop the shutdown process are useless. After the error message the computer should shut down after a while.


Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1096217536 (LWP 6841)]
[KCrash handler]
#6  0x4175f487 in KViewPart::writeSettings ()
   from /opt/kde3/lib/kde3/kviewerpart.so
#7  0x41761dc5 in KViewPart::~KViewPart ()
   from /opt/kde3/lib/kde3/kviewerpart.so
#8  0x4062640e in QPtrList<QObject>::deleteItem ()
   from /opt/kde3/lib/libkdeui.so.4
#9  0x40e330cd in QGList::clear () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x4078dbc7 in KLibrary::~KLibrary () from /opt/kde3/lib/libkdecore.so.4
#11 0x4078e253 in KLibLoader::close_pending ()
   from /opt/kde3/lib/libkdecore.so.4
#12 0x4078e6be in KLibLoader::~KLibLoader () from /opt/kde3/lib/libkdecore.so.4
#13 0x4073142b in KLibLoader::cleanUp () from /opt/kde3/lib/libkdecore.so.4
#14 0x407dab43 in KApplication::~KApplication ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x080503ef in main ()
Comment 4 Wilfried Huss 2006-08-29 18:39:31 UTC
The crash reporting is not done by KDVI itself, so we have no control over it
anyway. This is done by drkonqi in kdelibs.

And I do not share your opinion that crash reporting during shutdown is uninteresting, because a crash might result in lost data.

The issue that drkonqi blocks the shutdown process is aleady reported in
bug 126073.

Anyway this particual crash should be finally fixed now. See bug 122961.

Greetings,
Wilfried Huss