Description of problem: in mate window manager: 1. install dropbox 2. launch caja 3. crash Version-Release number of selected component: mate-file-manager-1.6.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_slice_alloc0 at gslice.c:1042 #4 g_object_notify_queue_freeze at gobject.c:237 #5 g_object_freeze_notify at gobject.c:1095 #6 gtk_label_set_text at gtklabel.c:1908 #7 set_label_size at caja-zoom-control.c:282 #8 caja_zoom_control_init at caja-zoom-control.c:359 #9 g_type_create_instance at gtype.c:1868 Potential duplicate: bug 982111
Created attachment 842101 [details] File: backtrace
Created attachment 842102 [details] File: cgroup
Created attachment 842103 [details] File: core_backtrace
Created attachment 842104 [details] File: dso_list
Created attachment 842105 [details] File: environ
Created attachment 842106 [details] File: exploitable
Created attachment 842107 [details] File: limits
Created attachment 842108 [details] File: maps
Created attachment 842109 [details] File: open_fds
Created attachment 842110 [details] File: proc_pid_status
Created attachment 842111 [details] File: var_log_messages
Another user experienced a similar problem: My background theme is random theme, and when the caja is killed, the background theme swithched to another theme. I think... reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.12.5-302.fc20.x86_64 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Szőke Károly from comment #12) > Another user experienced a similar problem: What does this mean? Do you talking from another user on your server? Pls do not mix different user expirience in one report without a new backtrace. > My background theme is random theme, and when the caja is killed, the > background theme swithched to another theme. I think... Which application do you use for background switching?
Another user experienced a similar problem: I was only using the file manager, opening closing folders, and it crashed. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.12.6-300.fc20.x86_64 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I did like to write, when my background theme switched to another picture. It is the built in mate function, which can be set up in System/Preferences/Appearance. Sorry for my english... Another user experienced a similar problem: Sorry for this. The program crashed twice, and second crash was together with the background picture switching, and I wrote my experience.
Another user experienced a similar problem: Cliquei no icone do Caja para abri-lo e ele nao abriu. Depois apareceu a mensagem pedindo para reportar este bug. Porem ao clicar novamente para reexecuta-lo, abriu normal. O erro aconteceu somente na primeira tentativa. Nao é um problema frequente. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.12.9-301.fc20.x86_64 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Dans l'affichage du poste de travail : panneau droit de la fenêtre, vue en liste (défaut), clic sur un cd audio non reproduit When viewing my computer : right pane of the window, list view (default), clic on an audio cd does not happen again on retry reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.12.10-300.fc20.x86_64 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Not sure why caja (File manager for MATE Desktop) is killed, was reading. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.13.3-201.fc20.x86_64 package: mate-file-manager-1.6.3-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I unmounted a CD-ROM as the superuser. < in a terminal, bash prompt, after having done "sudo su - " much earlier > # umount /dev/sr0 Then ABRT popped up. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.13.6-200.fc20.x86_64 package: mate-file-manager-1.6.4-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Wolfgang Ulbrich from comment #13) > (In reply to Szőke Károly from comment #12) > > Another user experienced a similar problem: > What does this mean? > Do you talking from another user on your server? > Pls do not mix different user expirience in one report without a new > backtrace. > > My background theme is random theme, and when the caja is killed, the > > background theme swithched to another theme. I think... > Which application do you use for background switching? Hi Wolfgang, The text "Another user experienced a similar problem:" is automatically generated by ABRT. (Maybe that's a bug you should open against the ABRT package :^) - to indicate somewhere that the message is automatically generated). Anyway, when ABRT ran for me, it performed a backtrace, but did not see fit to attach it because "A duplicate bug has already been submitted". If I can find it in /var somewhere, I'll post my backtrace too. --James
Created attachment 878079 [details] caja backtrace - mate-file-manager-1.6.4-1.fc20.x86_64 Backtrace retrieved from /var/tmp/abrt/ccpp-2014-03-24-09:39:31-3623
Another user experienced a similar problem: just launched caja, after second launch this problem didn't appear reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: caja -n crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.13.6-200.fc20.x86_64 package: mate-file-manager-1.6.4-1.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Created attachment 879122 [details] backtrace I don't know why caja crashed this time. It was open, but I wasn't using it.
Another user experienced a similar problem: I was scrolling down the window watching a batch (184) of mp3 files being saved on an NFS share after modifying with Easytag. This is the first time that abrt notified me of this problem, indicating that it is a new problem. I may have other large sets of MP3s I can batch edit to try to duplicate problem. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: caja crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.13.10-200.fc20.x86_64 package: mate-file-manager-1.6.4-2.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: caja was started just as the USB drive got plugged in reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: caja crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.13.10-200.fc20.x86_64 package: mate-file-manager-1.6.4-2.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I had another crash this morning; Caja was in the background. Previously I had been deleting files from a remote server (sftp).
Another user experienced a similar problem: I had 3 sessions of Caja Opened, one pointing o my home folder and another to a smb share within the same lan as mine. So it crashed without reason. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: caja crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.14.4-200.fc20.x86_64 package: mate-file-manager-1.6.4-4.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
forward to upstream https://github.com/mate-desktop/caja/issues/295
Another user experienced a similar problem: I checked "I don't know what caysed this problem" box. Please don't ask me. I really don't know. Maybe Jesus send SIGSEGV from heaven. Maybe god touched my laptop. Maybe it was miracle! My laptop will be saint! Haleluja! PS: No. I really don't know what happened. Abrt just show me this dialog box and I obeyed orders of holy abrt. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: caja crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.15.3-200.fc20.x86_64 package: mate-file-manager-1.6.4-4.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 20787
Another user experienced a similar problem: Connecting an MTP Device reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: caja crash_function: magazine_chain_pop_head executable: /usr/bin/caja kernel: 3.15.6-200.fc20.x86_64 package: mate-file-manager-1.6.4-4.fc20 reason: caja killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
mate-file-manager-1.6.x isn't ship anymore in f20 repo, and upstream ships 1.8.x.