Bug 691249

Summary: [abrt] xfdesktop-4.6.2-2.fc14.1: _thunar_vfs_path_shutdown: Process /usr/bin/xfdesktop was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Davor <davor>
Component: xfdesktopAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: kevin, maxamillion
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:46df7afc42a616f4f4f89c90b7e814dc040bc267
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 21:29:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Davor 2011-03-27 22:05:48 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 10361 bytes
cmdline: xfdesktop --display :0.0 --sm-client-id 2223ded38-b7a5-4de3-b0e1-321d70d46335
component: xfdesktop
Attached file: coredump, 11886592 bytes
crash_function: _thunar_vfs_path_shutdown
executable: /usr/bin/xfdesktop
kernel: 2.6.35.11-83.fc14.i686
package: xfdesktop-4.6.2-2.fc14.1
rating: 4
reason: Process /usr/bin/xfdesktop was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1301263201
uid: 500

How to reproduce
-----
1. I have 'killall xfdesktop' every hour run by cron, for wallpaper change. It's all!!
2.
3.

Comment 1 Davor 2011-03-27 22:05:51 UTC
Created attachment 488046 [details]
File: backtrace

Comment 2 Kevin Fenzi 2011-03-27 22:18:08 UTC
This might be a crash in Thunar, but you really shouldn't be killing xfdesktop just to change your wallpaper... instead: 

xfdesktop --reload

should gracefully reload xfdesktop and load the next wallpaper. 

if you change your cron job to that, does it stop the crashes?

Comment 3 Davor 2011-03-27 22:38:09 UTC
option reload did not work. I have system mail:

From: root (Cron Daemon)
To: davor
Subject: Cron <davor@Bonifacije> linux/xfdreload
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/davor>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=davor>
X-Cron-Env: <USER=davor>


(xfdesktop:5052): Gtk-WARNING **: cannot open display:



I will try wallpapoz.

Comment 4 Kevin Fenzi 2011-03-28 00:27:11 UTC
Sorry, I guess that won't work from cron that way. 

Try a: 

killall -USR2 xfdesktop 

in your cron. That should tell it simply to go to the next image.

Comment 5 Davor 2011-03-28 10:08:15 UTC
Please tell me who is -USR1 and -USR2?

I will try 0 * * * * ps -u davor | grep xfdesktop | awk '{print $1}' | xargs kill

Comment 6 Kevin Fenzi 2011-03-28 15:20:09 UTC
Those are signal types you can send a process. ;) In this case xfdesktop listens for a USR2 signal and then reloads the background. 

The above will just be the same as killall... you want 

'killall -USR2 xfdesktop' which will send it the USR2 signal without killing it.

Comment 7 Davor 2011-03-28 21:09:58 UTC
TNX! But i have new solution. I find nice script and make some changes:

#!/bin/bash
#set -x
while [ 1 -eq 1 ]
do
dir="/media/home2/Video/Zaslon/wallpaper/"
#
a=`ls $dir -A `
if [ "$a" == "" ]
then
mv /media/home2/Video/Zaslon/wllpcpy/* $dir
fi
#
cd $dir
brsl=`ls | wc -l | tr -d "[ ]"`
br=0
for i in `ls`
do
slk[br]=${dir}$i
((br=br+1))
done
RANDOM=`date '+%s'`
brsls=$[($RANDOM % brsl)]
#donja naredba je za GNOME
#gconftool-2 --type string --set /desktop/gnome/background/picture_filename ${slk[$brsls]}
#donja naredba je za XFCE
xfconf-query -c xfce4-desktop -p /backdrop/screen0/monitor0/image-path -s  ${slk[$brsls]}
cp /home/davor/log/wall.txt /home/davor/log/wall-stari.txt
echo ${slk[$brsls]} > /home/davor/log/wall.txt
echo $(date)  >> /home/davor/log/wall.txt
#
((p=60))
((m=`date +%M`))
((s=`date +%S`))
((jm= p - m - 1 ))
((js= p - s ))
((jv= jm * p + js + 5 ))
#((jv = 3))
sleep $jv
mv ${slk[$brsls]} /media/home2/Video/Zaslon/wllpcpy/
done
#set +x

Put it in autostart aplication and i no need kill.

Comment 8 Kevin Fenzi 2011-03-29 00:21:54 UTC
great. That should work fine as well. 

I'll see what upstream can make of this bug.

Comment 9 Kevin Fenzi 2011-05-14 12:18:03 UTC
*** Bug 704707 has been marked as a duplicate of this bug. ***

Comment 10 Kevin Fenzi 2011-05-14 12:26:12 UTC
Added upstream bug link.

Comment 11 abrt-bot 2012-03-21 15:41:45 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  thunar-volman: bug #560125, bug #641300, bug #654051
  xfdesktop: bug #553514, bug #704707

This comment is automatically generated.

Comment 12 Fedora End Of Life 2012-08-16 21:29:42 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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