| Summary: | ark loaded at startup from previous session crashes if closed | ||
|---|---|---|---|
| Product: | [Applications] ark | Reporter: | Bernhard Frauendienst <kde> |
| Component: | general | Assignee: | Harald Hvaal <metellius> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | admiraljkb, alessioboccialoni, amadlopes2, andresbajotierra, ascanabys, bmw, dglent, diego.ml, django_2005-bastard, Duncan.Doyle, e.cisotti, EagleScreen, echidnaman, eddieg780, ethankhall, g4mba5, gliporace, javieradrianr, jjj123jjj, kirst, kristjan.ugrin, lesergi, morf3089, peerit, rafael.regisp, rakuco, rocker, rrsriram, ruud_slootweg, saalo, saulotoledo, stefnn, sven.burmeister, tonywhite100, usrrgt, wesleyhg, yollywau |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Create KPart on session restore | ||
|
Description
Bernhard Frauendienst
2008-11-20 09:57:44 UTC
Happens in 4.1.3 too. (In reply to comment #1) > Happens in 4.1.3 too. > If I remember correctly, this happened in every KDE4-Version I've tried so far (which would be all since 4.1, I think), so this probably isn't a regression bug. Does it actually open any file when it resumes the ark instance? Or does it just open an empty ark? I can't say, because -- like I said -- the form is completely empty. It contains none of the usual controls. I'll keep an eye out though and try to find out more details. (In reply to comment #4) > I'll keep an eye out though and try to find out more details. > Ok, so I shutdown session with a file open in ark, and without one, and both times the ark window in the new session was completely empty (no controls whatsoever, except the window decoration of course) and crashed on closing. *** Bug 179926 has been marked as a duplicate of this bug. *** Bug 179926 seems to happen in current trunk happens also to me on kde 4.2 RC1. Ark crashed for me also in the same conditions in KDE 4.2 RC1, I obtained this backtrace: Aplicación: Ark (ark), señal SIGSEGV 0x00007f7e6ea215f0 in nanosleep () from /lib/libc.so.6 Thread 1 (Thread 0x7f7e726636f0 (LWP 6398)): [KCrash Handler] #5 0x000000000040d2a0 in _start () I just experienced this symptom with ARK with Intrepid with KDE 4.2 RC1. The backtrace looks like a match Rafael's above. Application: Ark (ark), signal SIGSEGV 0x00007fb8c602c5f0 in nanosleep () from /lib/libc.so.6 Thread 1 (Thread 0x7fb8c9c6c6f0 (LWP 6702)): [KCrash Handler] #5 0x000000000040d2a0 in _start () I also am running KDE 4.2.RC1 (4.1.96) and without having opened Ark in a prior session after recent updates over past two days, 1/19 & 1/20. Here is the backtrace for me: Application: Ark (ark), signal SIGSEGV Thread 1 (Thread 0xb610c8d0 (LWP 5884)): [KCrash Handler] #6 0x080532b3 in _start () This bug also happens for me without having Ark open in last session. Here, that's the same for me with KDE4.2RC1 and also happens without having Ark open in last session. Same here as previous comments. KDE 4.2RC1 for Fedora 10, Ark 2.12. Open Ark in a session, then close it, exit the session, enter a new session. You get a blank Ark screen and when you close you get the backtrace at comment #9 and #10. Please mark this bug as confirmed. I have experienced this too.. I'm trying to discover what causes this: Bug 181678 may be related as the Ark process isn't terminated after a succesful extraction. So... it may be saved on session when closing the KDE session, and started on Login... *** Bug 182357 has been marked as a duplicate of this bug. *** How do I actually reproduce this? I tried setting the session manager to open last session, then opening ark with a file, then logging out and in again, but nothing happened, ark didn't open. @Harald: have you read my comment about bug 181678 ? Anyways, the last time I tried I couldn't reproduce it (using 4.3trunk) Ah, I see. Yes, I just forgot about that. I will see if I can trigger it first, then check afterwards if it goes away fixing the first bug. from OpenSUSE 11.1, kde 4.2.00 (KDE 4.2.0) "release 83.1" installed from one click install provided by factory (but given as stable) repositories as default package (not the base one) ark used in a previous session but closed on restart, it's shown after the restart as empty window, on close: Applicazione: Ark (ark), segnale SIGSEGV 0x00007fa118009cb0 in nanosleep () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fa11bd3c750 (LWP 4486))] Thread 1 (Thread 0x7fa11bd3c750 (LWP 4486)): [KCrash Handler] #5 0x000000000040c8bc in _start () Hi, same problem on KDE 4.2 (kubuntu 8.10): Ark blank window loaded at startup and it crashes when you close it. Application: Ark (ark), signal SIGSEGV Thread 1 (Thread 0xb60c88d0 (LWP 5590)): [KCrash Handler] #6 0x080532b3 in _start () *** Bug 182696 has been marked as a duplicate of this bug. *** *** Bug 182733 has been marked as a duplicate of this bug. *** As far as I can see this happens because the KPart is not created on session restore. I'm attaching a (not much tested) patch to fix this. Created attachment 30894 [details]
Create KPart on session restore
Workflow for to reproduce for me (KDE 4.2, x86_64): From Dolphin, right click on an archive, choose "Extract here..." Progress bar is displayed in notification box. After extracting is completed, notification box dissappears, but ark process is still visible in process list. Next time KDE is started, all those hanging ark-s are restored from session and crash when closed. I used to extract RAR archives. I'll check later if the behaviour depends on archive type. afaics, after successfully extracting some archives there are still some ark processes in the background: $ ps aux|grep ark mikko 5870 0.2 0.7 191588 15140 ? Sl 13:56 0:00 /usr/kde/live/bin/ark --batch --autodestination /mnt/dati/House.S05E14.HDTV.XviD-2HD/house.s05e14.hdtv.xvid-2hd.r00 So kde restores them at startup. The problem is why those processes aren't killed when the extraction is over. @Mikko: bug 181678 may be the cause (recently fixed) kirst@byte.ee and Mikko: Please do not use this bug report to report other bugs. This one is about the session restore problem. (In reply to comment #26) > Next time KDE is started, all those hanging ark-s are restored from session > and crash when closed. If you file a bug on this, please cc me! *** Bug 182380 has been marked as a duplicate of this bug. *** Same here. Blank Ark window starts up with every session of kde 4.2, and when i close it, it crashes immediatly. *** Bug 183128 has been marked as a duplicate of this bug. *** *** Bug 183405 has been marked as a duplicate of this bug. *** (In reply to comment #29) > kirst@byte.ee and Mikko: Please do not use this bug report to report other > bugs. This one is about the session restore problem. > But this is the actual problem why it persists across sessions in first place. If you use menu shortcuts to extract archives, ark will do the job but *n instances will remain open after successful extraction. And when you logout, kde will remember that, so it will spawn *n ark instances, which will be completely blank and crash when you close them. https://bugs.kde.org/show_bug.cgi?id=175637#c26 is one of possible ways to reproduce this. Very annoying. *n - times you extracted an archive. Please see bug #180321 about the hanging processes when extracting rar archives. The two problems are completely unrelated. *** Bug 183679 has been marked as a duplicate of this bug. *** (In reply to comment #36) > Please see bug #180321 about the hanging processes when extracting rar > archives. The two problems are completely unrelated. > I'm not getting that on rar files, but on every archive I've tried (tar, tar.gz, zip). And it does that 100% of time. Should I open a new bug about hanging process when extracting via pop-up menu? This is also the reason why blank ark instances are opened after kde restores new session (processes are there on exit), *** Bug 183997 has been marked as a duplicate of this bug. *** I got exactly the same error. There are lots of duplicates bugs of these. Even one with kde 3.5.4 see here:https://bugs.kde.org/show_bug.cgi?id=132641 *** Bug 184051 has been marked as a duplicate of this bug. *** Same here on KDE 4.2 and ark version 2.12. When I extracted archives with or without the context menu in a previous session ark reappears as a totally blank screen just with the title in the windows but without any buttons in the next session. And then every time I try to close the blank ark screen it crashes. *** Bug 184723 has been marked as a duplicate of this bug. *** *** Bug 184664 has been marked as a duplicate of this bug. *** SVN commit 927671 by metellius: BUG: 175637 Applied patch from Volker Lanz to fix the session restoring in ark. M +16 -4 main.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=927671 SVN commit 927740 by metellius: Backporting revision 927671 BUG: 175637 Applied patch from Volker Lanz to fix the session restoring in ark. M +16 -4 main.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=927740 *** Bug 183750 has been marked as a duplicate of this bug. *** Can you please let me know how to apply the patch Excuse me, I have the same bug. I read that someone has fixed it. How can I fix it? Thanks to all @Alessio: the crash is fixed in KDE4.2.1 and 4.3, you will have to wait for that versions to be released and included in your distribution *** Bug 185294 has been marked as a duplicate of this bug. *** (In reply to comment #45) > SVN commit 927671 by metellius: > > BUG: 175637 > Applied patch from Volker Lanz to fix the session restoring in ark. > > M +16 -4 main.cpp > > > WebSVN link: http://websvn.kde.org/?view=rev&revision=927671 I just wanted to confirm that the bug no longer occurs for me (using r930273). Thanks and keep up the good work ;) *** Bug 185613 has been marked as a duplicate of this bug. *** *** Bug 186196 has been marked as a duplicate of this bug. *** *** Bug 188155 has been marked as a duplicate of this bug. *** *** Bug 184830 has been marked as a duplicate of this bug. *** *** Bug 184935 has been marked as a duplicate of this bug. *** |