Summary: | Kate crash while attempting to save file | ||
---|---|---|---|
Product: | [Frameworks and Libraries] solid | Reporter: | Kevin Adler <zeke> |
Component: | libsolid-fstab | Assignee: | Mario Bensi <nef> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bill-bugs.kde.org, bruno, cfeck, chapelhilllaptopshop, daniel.moyne, jnelson-kde, kdebugs.phobie, mms, niko.sams, pkshima, simonandric5, stefan.bruens, s_chriscollins |
Priority: | VHI | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | https://projects.kde.org/projects/kde/kdelibs/repository/revisions/c96ad34d124519d30d3c0f4b369a9f0fa33b36f6 | Version Fixed In: | 4.8.4 |
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Kevin Adler
2012-03-21 17:50:25 UTC
*** Bug 297015 has been marked as a duplicate of this bug. *** Created attachment 70048 [details]
New crash information added by DrKonqi
gwenview (2.8.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
Gwenview and also dolphin are quite unstable! If running both, crashes occur regulary!
As I posted a separate bug report which was noted a duplicate of this one, I do post some debug info here!!
-- Backtrace (Reduced):
#7 QString::operator= (this=0x7fff6d38a1d8, other=...) at tools/qstring.cpp:1406
#8 0x00007f7cb9ee61bc in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fff6d38a1b0, device=0x21811d0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at ../../../solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9 0x00007f7cb9ee4921 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at ../../../solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00007f7cb9e72099 in Solid::Device::emblems (this=<optimized out>) at ../../../solid/solid/device.cpp:143
#11 0x00007f7cbd3f2369 in KFilePlacesItem::deviceData (this=0x211e290, role=1) at ../../kfile/kfileplacesitem.cpp:174
*** Bug 297330 has been marked as a duplicate of this bug. *** *** Bug 296537 has been marked as a duplicate of this bug. *** Bug #296537 comment #2 contains steps how to reproduce: > 1. Launch kdevelop > 2. On another konsole window, run "umount -a" > 3. Enjoy the crash. > > I use automount, so this crash happens every few minutes, so I am not able to use Kdevelop anymore. I just tested again on 4.8.2 and I'm no longer getting this problem. 1. mount cifs client 2. open file in mounted directory in kate 3. umount directory I got 'The file ... was deleted by another program' dialog like it normally would, instead of crashing. Created attachment 70256 [details]
New crash information added by DrKonqi
dolphin (2.0) on KDE Platform 4.8.2 (4.8.2) "release 491" using Qt 4.8.1
- What I was doing when the application crashed:
dolphin was open on a mounted nfs directory, then networkmanager restart the connection (or systemd, for no good reason)
Dolphin start to crash with a very minimal error
Application: Dolphin (kdeinit4 (deleted)), signal: Segmentation fault
[Current thread is 1 (process 19877)]
Thread 1 (process 19877):
#0 0x874a68dd in ?? ()
And then I get this new crash.
In NetworkManager logs
Apr 9 12:43:09 localhost NetworkManager[1361]: DHCPACK from 192.168.103.151
Apr 9 12:43:09 localhost NetworkManager[1361]: bound to 192.168.103.131 -- renewal in 5994 seconds.
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
Apr 9 14:00:09 localhost NetworkManager[1361]: <warn> Activation (eth0) failed.
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <warn> Activation (eth0) failed.
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): deactivating device (reason 'none') [0]
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): deactivating device (reason 'none') [0]
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2366
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> (eth0): canceled DHCP transaction, DHCP client pid 2366
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> Clearing nscd hosts cache.
Apr 9 14:00:09 localhost NetworkManager[1361]: NetworkManager[1361]: <info> Clearing nscd hosts cache.
Apr 9 14:00:09 localhost NetworkManager[1361]: sent invalidate(hosts) request, exiting
Apr 9 14:00:09 localhost NetworkManager[1361]: <info> Clearing nscd hosts cache
So there's something that can't handle correctly the fact a network connection could be drop. The program should avoid to crash so badly.
-- Backtrace (Reduced):
#7 QString::operator= (this=0x7fffd4b1b778, other=...) at tools/qstring.cpp:1410
#8 0x00007f3f59b7748c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fffd4b1b750, device=0xcb7870, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9 0x00007f3f59b75bf1 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00007f3f59b037e9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/solid/solid/device.cpp:143
#11 0x00007f3f5de533a9 in KFilePlacesItem::deviceData (this=0xbd5a20, role=1) at /usr/src/debug/kdelibs-4.8.2/kfile/kfileplacesitem.cpp:174
*** Bug 298017 has been marked as a duplicate of this bug. *** reopening, 298017 was reported with kde 4.8.2 *** Bug 298007 has been marked as a duplicate of this bug. *** *** Bug 298527 has been marked as a duplicate of this bug. *** I dont mean to rush since I understand this is open source software and developed mostly as community service. But wouldnt it be nice to hear of atleast a workaround for such a critical bug ? Having Kdevelop crash every 2 minutes is definitly a blocker to its success or even adoption. On the technical side, I dont see any issue with Kate, but only with Kdeveop. Yet this crash keeps getting duplicated to a bug titled ".. kate ...". Kate is just an editor. Users can temporarily switch to another easily. Things are not so sweet with kdevelop. Its an IDE too good to have a replacement. So titling this bug as a bug in an editor kind of belittles its importance. Dont you think ? *** Bug 298891 has been marked as a duplicate of this bug. *** *** Bug 298630 has been marked as a duplicate of this bug. *** *** Bug 299139 has been marked as a duplicate of this bug. *** *** Bug 299078 has been marked as a duplicate of this bug. *** *** Bug 299603 has been marked as a duplicate of this bug. *** This one should be fixed by: https://git.reviewboard.kde.org/r/104471/ Fix should be in 4.8.4, openSUSE has it cherrypicked: rpm -q --changelog libkde4 | grep fstabstorageaccess - fix crash due to race in fstabstorageaccess constructor As a temporary workaround, it might be enough to disable the places view in the open dialog. Thanks a lot for the response Stefan, About the fix : You mean version 4.84 of kdelibs ? About the workaround : which "open dialog" ? I see the crash in Kdevelop without doing anything. the bugs title is way too misleading. (In reply to comment #19) > About the workaround : which "open dialog" ? I see the crash in Kdevelop > without doing anything. the bugs title is way too misleading. This bug was specifically about the file dialog in kate, and the same bug can also be seen in dolphin, as it uses the same "Places" side pane. You never submitted a backtrace, so you may be hitting a completely independent bug. Thats quite unfortunate. The bug was very much reported on Kdevelop by me along with backtrace (Bug #296537) But Someone or some = tool keeps marking it as a dup of this bug. I added comments on this bug to show criticality of the issue and impact I am facing every few minutes but alas this bug is still titled as a simple bug in an editor :( (In reply to comment #21) > The bug was very much reported on Kdevelop by me along with backtrace (Bug > #296537) This information would have been useful in the first place - and yes, it is a duplicate (as can be seen from the backtrace). KDevelop must have a "Places" pane somewhere. Disabling the Filesystem Tool View in Kdevelop is a workaround that seems to work. Right click on teh Filesystem toolview and click "Remove Toolview". That aligns with the above comment "KDevelop must have a "Places" pane somewhere." Created attachment 71435 [details]
New crash information added by DrKonqi
k3b (2.0.2) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
waiting for a burn to finish (it was done or very nearly done when the crash happened)
ISO image file was on an NFS mount, if that matters (as has always worked in the past).
-- Backtrace (Reduced):
#7 QString::operator= (this=0x7fff19ea36b8, other=...) at tools/qstring.cpp:1410
#8 0x0000003b3629758c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fff19ea3690, device=0x11a42b0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9 0x0000003b36295c01 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x0000003b362382f9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/device.cpp:143
#11 0x0000003b444635f9 in KFilePlacesItem::deviceData (this=0x11ced20, role=1) at /usr/src/debug/kdelibs-4.8.3/kfile/kfileplacesitem.cpp:174
Created attachment 71815 [details]
New crash information added by DrKonqi
dolphin (2.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2
- What I was doing when the application crashed:
mount data CD. Dolphin crashes shortly thereafter. 4.8.3.
-- Backtrace (Reduced):
#7 QString::operator= (this=0x7fffb963e3a8, other=...) at tools/qstring.cpp:1410
#8 0x00000031d609758c in Solid::Backends::Fstab::FstabStorageAccess::FstabStorageAccess (this=0x7fffb963e380, device=0x1d20540, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabstorageaccess.cpp:40
#9 0x00000031d6095c01 in Solid::Backends::Fstab::FstabDevice::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/backends/fstab/fstabdevice.cpp:80
#10 0x00000031d60382f9 in Solid::Device::emblems (this=<optimized out>) at /usr/src/debug/kdelibs-4.8.3/solid/solid/device.cpp:143
#11 0x00000031d9c635f9 in KFilePlacesItem::deviceData (this=0x1b3c340, role=1) at /usr/src/debug/kdelibs-4.8.3/kfile/kfileplacesitem.cpp:174
Please close, this has been fixed by: https://projects.kde.org/projects/kde/kdelibs/repository/revisions/c96ad34d124519d30d3c0f4b369a9f0fa33b36f6 Fix is in 4.8.4/4.9.0 |