Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: baobab crash_function: cell_destroyed executable: /usr/bin/baobab kernel: 3.1.2-1.fc16.i686 pid: 24010 pwd: /home/Darkanonymous reason: Process /usr/bin/baobab was killed by signal 11 (SIGSEGV) time: Thu 01 Dec 2011 05:57:45 PM WET uid: 1000 username: Darkanonymous xsession_errors: backtrace: Text file, 14885 bytes build_ids: Text file, 2952 bytes dso_list: Text file, 6702 bytes event_log: Text file, 6739 bytes maps: Text file, 21088 bytes smolt_data: Text file, 3057 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=2 :HOSTNAME=Darkanonymous :SHELL=/bin/bash :HISTSIZE=1000 :XDG_SESSION_COOKIE=e1fef6852b0e8c3b37037d1f00000010-1322746017.575560-1208148746 :GNOME_KEYRING_CONTROL=/tmp/keyring-0cZIHF :USER=Darkanonymous :USERNAME=Darkanonymous :MAIL=/var/spool/mail/Darkanonymous :PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/Darkanonymous/.local/bin:/home/Darkanonymous/bin :DESKTOP_SESSION=gnome :PWD=/home/Darkanonymous :GNOME_KEYRING_PID=1343 :LANG=en_US.utf8 :GDM_LANG=en_US.utf8 :GDMSESSION=gnome :HISTCONTROL=ignoredups :HOME=/home/Darkanonymous :XDG_SEAT=seat0 :SHLVL=1 :LOGNAME=Darkanonymous :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-gYNf85efOe,guid=490379ad5a6faeacacbbe3ac00000040 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/Darkanonymous :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-Darkanonymous-NfgGPf/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1347,unix/unix:/tmp/.ICE-unix/1347 :SSH_AUTH_SOCK=/tmp/keyring-0cZIHF/ssh :GPG_AGENT_INFO=/tmp/keyring-0cZIHF/gpg:0:1 :GJS_DEBUG_OUTPUT=stderr :'GJS_DEBUG_TOPICS=JS ERROR;JS LOG' :DESKTOP_STARTUP_ID=gnome-shell-1440-Darkanonymous-baobab-43_TIME16268170 :GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/gnome-baobab.desktop :GIO_LAUNCHED_DESKTOP_FILE_PID=24010 var_log_messages: :Dec 1 17:57:45 Darkanonymous kernel: [16312.331178] baobab[24010]: segfault at 40000064 ip 48868f50 sp bf8f3ff0 error 4 in libgtk-3.so.0.200.2[48559000+475000] :Dec 1 17:57:45 Darkanonymous abrt[24021]: Saved core dump of pid 24010 (/usr/bin/baobab) to /var/spool/abrt/ccpp-2011-12-01-17:57:45-24010 (22171648 bytes)
Created attachment 539339 [details] File: event_log
Created attachment 539340 [details] File: build_ids
Created attachment 539341 [details] File: maps
Created attachment 539342 [details] File: smolt_data
Created attachment 539343 [details] File: dso_list
Created attachment 539344 [details] File: backtrace
*** Bug 770856 has been marked as a duplicate of this bug. ***
I have scanned my file system to have a size of each branch. When I tried to mark few branches by holding CTRL and clicking on them (just to check if it works that way) the program was killed. rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
I can't repeat this bug the way posted in comment 8. Maybe it was random exception caused by my hard drive.
Запустил сканирование системы rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Clicking around in the "disk usage analyzer". Sorry, that's about all i got. I was rather randomly clicking folders (on the left side, i think) when it happened. rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Was trying to check the details of sub-directories while scanning and it suddenly crashed backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 563913 [details] File: backtrace
Right-click on an entry in the treeview backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 564269 [details] File: backtrace
Classical random issue of disk usage tool. I was just clicking on folders of my home directory. They had about 1GB of data each. It were three quick click in combination folder, it's ancestor, ancestor's ancestor. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 565085 [details] File: backtrace
Opened disk analyser, analysed file system, crash when I clicked on a few folders backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 566663 [details] File: backtrace
Right-clicking on a folder in the left pane, a sub-folder of /var/tmp/ backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 570403 [details] File: backtrace
I have filed upstream GNOME bug Bug 672177 https://bugzilla.gnome.org/show_bug.cgi?id=672177
*** Bug 768909 has been marked as a duplicate of this bug. ***
I was browsing /var/cache/abrt-di/usr/lib/debug/usr/lib64 with baobab, then clicked on dri. I was not able to reproduce the problem. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 581008 [details] File: backtrace
Clicked on a node in the directory tree. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581102 [details] File: backtrace
I had clicked on Scan Home, and once that was complete, I clicked on a section of the diagram to the right. The tree expanded to reveal the file that I had clicked on. I then right-clicked on the file to see if there was a delete option. The outline of the context menu was drawn, but the application then crashed. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 582829 [details] File: backtrace
Opened itunes and crashed after opened backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Created attachment 583961 [details] File: backtrace
slowly entering the directories to see which files were using so much space. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
clicked on the root directory. backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
no idea backtrace_rating: 4 Package: gnome-utils-3.2.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.