Your message dated Thu, 10 Mar 2011 22:31:35 +0100 with message-id <1299792695.21613.74.camel@minnika> and subject line has caused the Debian Bug report #513639, regarding compiz-core: compiz should not try to read /var/log/Xorg.0.log to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 513639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513639 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: compiz-core: compiz should not try to read /var/log/Xorg.0.log
- From: Neil <neil.stewart@warwick.ac.uk>
- Date: Fri, 30 Jan 2009 22:53:50 +0000
- Message-id: <20090130225350.6092.35588.reportbug@macbook>
Package: compiz-core Version: 0.7.6-7 Severity: important compiz fails to start because it cannot read /var/log/Xorg.0.log. $compiz --replace & Checking for Xgl: not present. egrep: /var/log/Xorg.0.log: Permission denied egrep: /var/log/Xorg.0.log: Permission denied egrep: /var/log/Xorg.0.log: Permission denied egrep: /var/log/Xorg.0.log: Permission denied egrep: /var/log/Xorg.0.log: Permission denied egrep: /var/log/Xorg.0.log: Permission denied No whitelisted driver found aborting and using fallback: /usr/bin/metacity For increased security I'm running with umask 077, which means /var/log/Xorg.0.log is not read writable by normal users. $ ls -l Xorg.0.log -rw------- 1 root root 27106 Jan 30 22:42 Xorg.0.log The script /usr/bin/compiz assumes /var/log/Xorg.0.log to be readable by normal users in the function running_under_whitelisted_driver() on line 247. Changing the permissions for Xorg.0.log fixes the problem. To avoid having to do this every time I startx, I added a "return 0" at line 260 to skip this check. This is only a bodge. Presumably another method should be used to acquire the driver name to check for whitelisting. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to POSIX) Shell: /bin/sh linked to /bin/bash Versions of packages compiz-core depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libgl1-mesa-glx [libgl1] 7.0.3-7 A free implementation of the OpenG ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libsm6 2:1.0.3-2 X11 Session Management library ii libstartup-notification0 0.9-1 library for program launch feedbac ii libx11-6 2:1.1.5-2 X11 client-side library ii libxcomposite1 1:0.4.0-3 X11 Composite extension library ii libxdamage1 1:1.1.1-4 X11 damaged region extension libra ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxml2 2.6.32.dfsg-5 GNOME XML library ii libxrandr2 2:1.2.3-1 X11 RandR extension library ii libxslt1.1 1.1.24-2 XSLT processing library - runtime ii mesa-utils 7.0.3-7 Miscellaneous Mesa GL utilities Versions of packages compiz-core recommends: ii compiz-plugins 0.7.6-7 OpenGL window and compositing mana Versions of packages compiz-core suggests: pn nvidia-glx <none> (no description available) -- debconf-show failed
--- End Message ---
--- Begin Message ---
- To: 513639-close@bugs.debian.org
- Subject:
- From: Sean Finney <seanius@debian.org>
- Date: Thu, 10 Mar 2011 22:31:35 +0100
- Message-id: <1299792695.21613.74.camel@minnika>
Version: 0.8.4-4 This does not affect compiz in stable or unstable.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---