notifications are all black with some pixel artifacts

Bug #510762 reported by Kolomona
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: notify-osd

All NotifyOSD noticications appear as black with random pixels.

They work fine when I boot with the Live CD. They also worked when I first installed Ubuntu.

I suspect it's a video card driver issue.

I was unsuccessful in using EnvyNG to install the ATI video driver.

I then booted into recovery mode, and ran envyng --uninstall-all

Since then all NotifyOSD notifications have appeared this way.

I've attached a screenshot

Machine info
IBM ThinkPad T-30
16MB RADEON 7500 ATI Mobility video chipset
Additional specs can be found here.
http://www-307.ibm.com/pc/support/site.wss/MIGR-42218.html

apt-cache policy notify-osd
lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

notify-osd:
  Installed: 0.9.24-0ubuntu1
  Candidate: 0.9.24-0ubuntu1
  Version table:
 *** 0.9.24-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

My xorg.conf

# /etc/X11/xorg.conf for T30 2366-85U
# with ATI Radeon Mobility 7500 (M7) GPU
# running UNR 9.10

Section "Device"
 Identifier "Configured Video Device"
 Driver "ati"
 BusID "PCI:1:0:0"
 #Option "GARTSize" "16"
 #Option "AGPMode" "4"
 #Option "DPMS"
 Option "AccelMethod" "XAA"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 Option "AIGLX" "true"
EndSection

ProblemType: Bug
Architecture: i386
Date: Thu Jan 21 08:47:54 2010
DistroRelease: Ubuntu 9.10
GtkTheme: Human
IconTheme: Humanity
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 4971:ce12
 Bus 002 Device 002: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 236685U
Package: notify-osd 0.9.24-0ubuntu1
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=8b2c72b5-2f95-4d30-a319-a0013e096f8b ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2.1
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: notify-osd
Uname: Linux 2.6.31-17-generic i686
WindowManager: metacity
XsessionErrors:
 (gnome-settings-daemon:7127): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:7235): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:7253): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:10398): GLib-WARNING **: g_set_prgname() called multiple times
dmi.bios.date: 08/08/2005
dmi.bios.vendor: IBM
dmi.bios.version: 1IET70WW (2.09 )
dmi.board.name: 236685U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1IET70WW(2.09):bd08/08/2005:svnIBM:pn236685U:pvrNotAvailable:rvnIBM:rn236685U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 236685U
dmi.product.version: Not Available
dmi.sys.vendor: IBM

Revision history for this message
Kolomona (kolomona) wrote :
Revision history for this message
Steve McGrath (smcgrath23) wrote :

I've marked this as a duplicate of bug #426582. It's a problem with the new Xorg and ATI Radeon 7500 chipsets. There's a few workarounds noted on the other bug report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.