abrt version: 1.1.13 architecture: i686 cmdline: /usr/bin/python /usr/bin/radiotray component: radiotray executable: /usr/bin/radiotray kernel: 2.6.34.7-56.fc13.i686.PAE package: radiotray-0.6.1-1.fc13 reason: Notification.py:39:notify:GError: Unable to connect to server release: Fedora release 13 (Goddard) time: 1287079931 uid: 500 backtrace ----- Notification.py:39:notify:GError: Unable to connect to server Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/radiotray/AudioPlayerGStreamer.py", line 114, in on_message self.mediator.notifyPlaying() File "/usr/lib/python2.6/site-packages/radiotray/StateMediator.py", line 104, in notifyPlaying self.notification.notify(C_("Notifies which radio is currently playing.", "Radio Tray Playing"), self.currentRadio) File "/usr/lib/python2.6/site-packages/radiotray/Notification.py", line 39, in notify self.notif.show() GError: Unable to connect to server Local variables in innermost frame: message: '80s Sky.FM' pixbuf: <gtk.gdk.Pixbuf object at 0xa221d4c (GdkPixbuf at 0xa299288)> self: <radiotray.Notification.Notification instance at 0xa22370c> title: 'Radio Tray Playing' How to reproduce ----- 1. started radiotray after yum upgrade 2. 3.
Created attachment 453524 [details] File: backtrace
Hi, Thanks for reporting this bug. Does radiotray do this every time on every radio you try to play? Thank you!
yes eachtime radiotray is running fine but eachtime at sarting a new bug is automatic reported
Ok, just to be sure I understand that one correctly : - Radiotray is not running - You start radiotray - You choose a new radio to listen - This error message popup but radiotray play fine Is it correct? If yes, do you run GNOME, KDE, XFCE, etc?
It is correct! I run Gnome or XFCE, both installed
Thank you for the feedback. My understanding is that the bug is caused by radiotray not being able to connect to the notification server. Do you have a notification tray on your desktop? Thanks!
yes i have, also from radiotray
Package: radiotray-0.6.1-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Started app for the first time 2. Selected a station (181.FM Classic Hits) 3. Stream started playing just as the notification of a crash happened Comment ----- This seems to be a crash that hasn't effedted the app. I was able to switch to other stations and it kept playing.
Package: radiotray-0.6.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start radiotray. 2. Start playing a radio station. 3. Playback starts successfully and a correct notification is displayed, but ABRT complains of a crash. Comment ----- I am using F14 Xfce Spin x86_64 with xfce4-notifyd v.0.1.0-3.fc12 as my notification system, perhaps radiotray is expecting notification-daemon?
radiotray-0.6.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/radiotray-0.6.3-1.fc14
radiotray-0.6.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/radiotray-0.6.3-1.fc13
Package: radiotray-0.6.1-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Launch radiotray 2. Select a station 3. Radio starts playing fine, but for some reason ABRT reports a bug Comment ----- I'm using F14 Xfce Spin.
Whoops, forgot that I'd already submitted a bug report for this! The radiotray 0.6.3 build from koji fixes this issue for me.
radiotray-0.6.3-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update radiotray'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/radiotray-0.6.3-1.fc14
radiotray-0.6.3-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
radiotray-0.6.3-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.