abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 24013 bytes cmdline: /usr/libexec/notification-daemon component: notification-daemon Attached file: coredump, 20381696 bytes crash_function: gtk_window_configure_event executable: /usr/libexec/notification-daemon kernel: 2.6.38-0.rc4.git0.2.fc15.x86_64 package: notification-daemon-0.7.0-4.fc15 rating: 3 reason: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT) release: Fedora release 16 (Rawhide) How to reproduce: it occured gnome-session started as gnome-shell time: 1297788915 uid: 500
Created attachment 478933 [details] File: backtrace
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Start fedora 15 test. 2. 3.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. boot into Fedora 15 alpha TC2 2. login 3. Comment ----- Just after login abrt will report the notification-daemon has crashed
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Login 2. 3.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Login to GNOME3 desktop from gdm 2. After gnome-shell, starts, observe the crash notification that the notification-daemon failed Comment ----- Login to GNOME3 desktop for the first time and observe the notification-daemon failure
Proposing for F15Beta per the following Beta release criteria ... "No part of the default desktop's panel (or equivalent) configuration should crash on boot of the installed system using default installation choices" https://fedoraproject.org/wiki/Fedora_15_Beta_Release_Criteria
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Enable bluetooth 2. Make sure you are paired with other bluetooth device (PC) 3. Go Bluetooth icon in notification area -> Bluetooth settings 4. Select paired device from the list, click "Remove" button and confirm it
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Log user out 2. log user in 3.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Log into GNOME Shell via gdm. Fedora 15 Alpha.TC2 2. ABRT displays the crash notification at the bottom.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Login 2. 3.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. login to Gnome Shell
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- Fresh installed f15 alpha - first login
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. this bug occurs at system startup. 2. every time 3.
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. installed Fedora from LiveCD 2. Reboot 3. See notification-daemon crash
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) - LiveCD for Fedora Test Day (graphics) How to reproduce ----- 1. Ran special Fedora 15 LiveCD created for graphics test week 2. Used the "Fast user switcher" to switch from the LiveCD user to an account that I had added 3. notification-daemon crashed
Package: notification-daemon-0.7.0-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) How to reproduce ----- 1. Install F15-alpha-rc1 with gnome desktop environment. 2. login to the desktop
Discussed at 2011-03-11 blocker review meeting. Agreed that this is a final release blocker per criterion "In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ)" (it doesn't quite hit the Beta criterion as the notification daemon isn't really part of the 'default panel configuration'). We believe notification-daemon-0.7.1-1.fc15 probably fixed this, as there've been no CCs since 2011-02-25 or with that version of the package. Can reporters please confirm they're not seeing this any more? Thanks.
I don't see this bug anymore, I think it is fixed.
thanks.