Bug#487202: grandr: "Display Geometry Switcher" quit unexpectedly, if external monitor is unplugged
Package: grandr Version: 0.1+git20080326-1 Severity: normal On my laptop (Thinkpad T60), I start the "Display Geometry Switcher" with an external screen plugged (see xrandr output below). If I then unplug the monitor, then go to the menu an click on anything, I get a popup says `"Display Geometry Switcher" has quit unexpectedly' I haven't tried to reproduce it with another configuration yet. Franklin #xrandr output : Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 1920 x 1200 VGA connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 60.0*+ 1600x1200 59.9 1680x1050 60.0 1280x1024 75.0 59.9 1152x864 74.8 1024x768 75.1 60.0 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 285mm x 214mm 1024x768 60.0*+ 50.0 800x60060.3 640x48060.0 59.9 TMDS-1 disconnected (normal left inverted right x axis y axis) TV disconnected (normal left inverted right x axis y axis) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-rc6-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grandr depends on: ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit ii libc6 2.7-10 GNU C Library: Shared libraries ii libcairo2 1.6.4-3The Cairo 2D vector graphics libra ii libgconf2-4 2.22.0-1 GNOME configuration database syste ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libgtk2.0-0 2.12.9-4 The GTK+ graphical user interface ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio ii libx11-6 2:1.1.4-2 X11 client-side library ii libxrandr22:1.2.2-2 X11 RandR extension library grandr recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484583: xserver-xorg-video-nv: Failed to set up write-combining range
Ryo Furue wrote: > | > I have this warning in my /var/log/Xorg.0.log : > | > > | > (WW) NV(0): Failed to set up write-combining range > (0xd800,0x800) > | > > | > and this in /var/log/kern.log > | > > | >kernel: mtrr: type mismatch for d800,800 old: write-back new: > write-combining > | > > | > | Not sure this is actually a bug. The kernel is mainly responsible for > | marking ranges as WC. But sometimes there are too many entries allocated > | so Xorg cannot get a new one. And sometimes, the existing ranges are > | difficult to modify to satisfy what Xorg wants. > | > | What does /proc/mtrr contains before and after starting X? > > I've just found a chance to restart my machine. I don't know an > easy way of getting a status "before X", so I shut down the machine > and booted to a single-user mode, where I copied the contents of > /proc/mtrr to another file. I then exited, which brought the machine > to the regular mode. I logged in from KDM to my regular session, and > copied the contents of /proc/mtrr again. > > The result is that /proc/mtrr didn't change between before and after X > and is > > reg00: base=0x ( 0MB), size=65536MB: write-back, count=1 > reg01: base=0xcff0 (3327MB), size= 1MB: uncachable, count=1 > reg02: base=0xd000 (3328MB), size= 256MB: uncachable, count=1 > reg03: base=0xe000 (3584MB), size= 512MB: uncachable, count=1 > reg04: base=0xff000 (65280MB), size= 256MB: uncachable, count=1 > > Does this info help? > I am not sure. The video memory range is included in the reg02 line above. Maybe the kernel fails to split the range into a WC range for your video board and the UC range for the other half. You might want to look in your BIOS for some MTRR setup in case you can make the BIOS setup different ranges at boot time. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423775: xserver-xorg-core: Still experiencing crashes, will try Sid's 1.4 version.
Le Fri, Jun 20, 2008 at 07:26:47AM +0200, Brice Goglin a écrit : > Charles Plessy wrote: > > > > Shall I try Sid's packages ? > > > > The ati driver in sid is probably better than the one in testing, the > server update is about security. Updated. I will restart the machine Monday and let you know at the next crash if any. (I just have too many windows opened now :) Have a nice day, -- Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 484875
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.29 > tags 484875 + fixed-upstream Bug#484875: [xserver-xorg-video-nv] enhance support for geforce 9 mobile gpus There were no tags set. Tags added: fixed-upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481548: xserver-xorg-video-ati: XVideo gamma curve is wrong for at least r300 chips
Tobias Diedrich wrote: > Package: xserver-xorg-video-ati > Version: 1:6.8.0-1 > Severity: normal > Tags: upstream patch > > > Hi, > > I noticed that there are very visible steps in the video overlay in dark > scenes. After investigating I found this to be a problem with the video > overlay (XVideo), since software-converted YV12 looks fine compared with > the overlay. > Also, when using other gamma values than 1.0, I would get a pink > overlay. > After playing with the driver and graphics registers a bit, > I found the gamma tables in radeon_video.c to be wrong for my two cards: Can you try 6.8.191 ? There are some Gamma fixes for r300 in there. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423775: xserver-xorg-core: Still experiencing crashes, will try Sid's 1.4 version.
Charles Plessy wrote: > Le Fri, Jun 20, 2008 at 07:02:16AM +0200, Brice Goglin a écrit : > >> Charles Plessy wrote: >> >>> I hope that the upgrade will fix the problem, it just seems too >>> complicated to handle. >>> >>> >> Did you have a chance to upgrade? >> > > Yes, I now have X 1:7.3+10 and the ATI driver 1:6.8.0-1. I still > experience some unpredicatble crashes. A few times it happened when I > ran a program that tried to use more memory than the available RAM. So > maybe despite the fact that I do not encounter crashes with OSX, it may > be a hardware problem after all. I ran the memtester program, and it > never stopped (It sometimes paused, however). > > Sometimes I have many crashes a day, sometimes not. Importantly, I never > switch the computer off in week days. Maybe it crashes until some kind > of bad ram gets in an area that for whatever reason is not allocated > until the next reboot; that could explain why sometimes I have no > problem for more than a week? > > Shall I try Sid's packages ? > The ati driver in sid is probably better than the one in testing, the server update is about security. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480355: xserver-xorg: With KVM, screen not set to highest resolution
Daniel Dickinson wrote: > Package: xserver-xorg > Version: 1:7.3+10 > Severity: normal > > > With an el-cheapo KVM a monitor (Compaq P110) and video card (ATI Radeon 8500 > QL) (= r200) that normally autodetect, don't. Using PreferredResolution in > the Monitor section does the right thing. I don't know if this can be > autodetected or not, but I'll provide info to help in case it can. > IIRC, the KVM can break the EDID and thus make autodetection fail. Can you try read-edid to compare the EDID with and without the KVM? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#423775: xserver-xorg-core: Still experiencing crashes, will try Sid's 1.4 version.
Le Fri, Jun 20, 2008 at 07:02:16AM +0200, Brice Goglin a écrit : > Charles Plessy wrote: > > I hope that the upgrade will fix the problem, it just seems too > > complicated to handle. > > > > Did you have a chance to upgrade? Yes, I now have X 1:7.3+10 and the ATI driver 1:6.8.0-1. I still experience some unpredicatble crashes. A few times it happened when I ran a program that tried to use more memory than the available RAM. So maybe despite the fact that I do not encounter crashes with OSX, it may be a hardware problem after all. I ran the memtester program, and it never stopped (It sometimes paused, however). Sometimes I have many crashes a day, sometimes not. Importantly, I never switch the computer off in week days. Maybe it crashes until some kind of bad ram gets in an area that for whatever reason is not allocated until the next reboot; that could explain why sometimes I have no problem for more than a week? Shall I try Sid's packages ? Have a nice day, -- Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480241: xserver-xorg-video-i810: No console, bad flicker after suspend to ram
Brian McKee wrote: > Brice Goglin wrote: > > Brian McKee wrote: > >> Package: xserver-xorg-video-i810 > >> Version: 2:2.2.1-2 > >> Severity: important > >> First time bug reporter - let me know what else I can do > >> No consoles and heavy flickering after suspend to ram > > > Could you try xserver-xorg-video-intel 2.3 from experimental ? And maybe > > a more recent kernel too ? (namely 2.6.25 or 2.6.26-rc) > > OK - will try in next couple of days. Any news ? Can you try intel 2.3.2 ? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479771: xserver-xorg: I've upgraded to 7.3 and keyboard auto repeat stops working
Diego Woitasen wrote: > Package: xserver-xorg > Version: 1:7.3+10 > Severity: important > > > With the default config, the keyboard auto repeat doesn't work > Did you manage to work around this problem? Or does any of the latest X packages help? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#399204: bug still present in 1:0.2.2-5
Paolo Cavallini wrote: > The bugs is still present in the latest xorg, and causes X to crash: > (II) VIA: driver for VIA chipsets: CLE266, KM400/KN400, K8M800, > PM800/PM880/CN400 > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > (EE) No devices detected. > AFAICU, the bug seems to be fixed upstream: what prevents from fixing it > in the package? > Many thanks. > pc > xserver-xorg-video-openchrome is in Debian now, can you try it ? I actually have no idea whether openchrome supports the same hardware than -via, but it's probably worth trying it. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452376: xserver-xorg-video-i810: Screen corrupted after suspend to ram
Mark Small wrote: > 2.2.1 failed in the same manner on resume as the earlier versions. > 2.3.0 locked my computer when on resume from s2ram. > what about 2.3.2 now ? :) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-openchrome: Changes to 'upstream-unstable'
src/via_driver.c |1 -
src/via_swov.c |2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
New commits:
commit da2e50a6485667c0d2c5fc1b2b15610523c705ef
Author: ben <[EMAIL PROTECTED]>
Date: Sun Jun 15 22:17:42 2008 +
VM800/CN700 appears to have a CLE video engine (reported by Vincent
Magnin).
git-svn-id: http://svn.openchrome.org/svn/[EMAIL PROTECTED]
e8d65cb0-85f4-0310-8831-c60e2a5ce829
diff --git a/src/via_driver.c b/src/via_driver.c
index e51ed8e..0287e78 100644
--- a/src/via_driver.c
+++ b/src/via_driver.c
@@ -824,7 +824,6 @@ VIASetupDefaultOptions(ScrnInfoPtr pScrn)
pVia->DRIIrqEnable = FALSE;
break;
case VIA_VM800:
-pVia->VideoEngine = VIDEO_ENGINE_CME;
pVia->agpEnable = FALSE;
break;
case VIA_K8M890:
commit 48a5888fcb96eb619891de62f101181c81299b52
Author: schlobinux <[EMAIL PROTECTED]>
Date: Fri Jun 13 19:31:32 2008 +
fix typo
git-svn-id: http://svn.openchrome.org/svn/[EMAIL PROTECTED]
e8d65cb0-85f4-0310-8831-c60e2a5ce829
diff --git a/src/via_swov.c b/src/via_swov.c
index 1806c0e..2a13419 100644
--- a/src/via_swov.c
+++ b/src/via_swov.c
@@ -1727,7 +1727,7 @@ Upd_Video(ScrnInfoPtr pScrn, unsigned long videoFlag,
* FIXME:
* Enable video on secondary
*/
-if (pVia->VideoEngine == VIDEO_ENGINE_CME;
+if (pVia->VideoEngine == VIDEO_ENGINE_CME
&& pVia->pBIOSInfo->PanelActive) {
/* V1_ON_SND_DISPLAY */
vidCtl |= 0x8000;
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478999: xserver-xorg-video-intel: "Error in I830WaitLpRing()" on 855GM while web browsing
Andrew Moise wrote: > Package: xserver-xorg-video-intel > Version: 2:2.2.99.901-1 > Severity: normal > > Today I got a crash while doing not much of anything (just browsing > the web in Iceweasel); my screen became unresponsive, and on sshing in > from another machine I found "Error in I830WaitLpRing()" in the log and > no running X process. > This happened within an hour (of X usage) or so of upgrading > xserver-xorg-core from version 2:1.4.1~git20080131-3 to version > 2:1.4.1~git20080131-4. With version 2:1.4.1~git20080131-3 I hadn't seen > crashes like this in quite some time. Looking over the changelist, I > can't quite imagine that that upgrade is actually the cause of the > brokenness unless something else is screwy, but anyway that's how it > happened. > Still the same problem with intel 2.3.2 ? What if you enable XAA instead of EXA ? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-openchrome: Changes to 'debian-unstable'
debian/changelog |7 +-- debian/links |1 + debian/overrides |1 - debian/rules |1 + src/via_driver.c |1 - src/via_swov.c |2 +- 6 files changed, 8 insertions(+), 5 deletions(-) New commits: commit c5c9d9ffcc17d044df0068b999f56828ecb15838 Author: Raphael Geissert <[EMAIL PROTECTED]> Date: Thu Jun 19 23:42:47 2008 -0500 Added missing dh_link call diff --git a/debian/rules b/debian/rules index f4cc01f..57ae5d5 100755 --- a/debian/rules +++ b/debian/rules @@ -72,6 +72,7 @@ binary-arch: serverabi install install -D -m 0644 debian/overrides \ debian/$(PACKAGE)/usr/share/lintian/overrides/$(PACKAGE) dh_strip + dh_link dh_compress dh_fixperms dh_makeshlibs commit de8c9ca1a60c2b8aebc6bfe72728ff8c26c0a0a2 Author: Raphael Geissert <[EMAIL PROTECTED]> Date: Thu Jun 19 23:40:47 2008 -0500 Install a symlink to xserver-xorg-core's bugreport script diff --git a/debian/changelog b/debian/changelog index e48cbb8..5d88f2a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -19,8 +19,9 @@ xserver-xorg-video-openchrome (1:0.2.902+svn577-1) UNRELEASED; urgency=low * Stripped enclosing chevrons from the unichrome link (Closes: #485957) - p.d.o displays the link with or without them, and looks ugly * Removed a useless lintian override + * Install a symlink to xserver-xorg-core's bugreport script - -- Raphael Geissert <[EMAIL PROTECTED]> Thu, 19 Jun 2008 22:10:17 -0500 + -- Raphael Geissert <[EMAIL PROTECTED]> Thu, 19 Jun 2008 23:39:43 -0500 xserver-xorg-video-openchrome (1:0.2.902+svn570-1) unstable; urgency=low diff --git a/debian/links b/debian/links new file mode 100644 index 000..aedc5bd --- /dev/null +++ b/debian/links @@ -0,0 +1 @@ +usr/share/bug/xserver-xorg-core/script usr/share/bug/xserver-xorg-video-openchrome/script \ No newline at end of file commit f25e8a67fb8d1e3664e9d03ed66843c7eb2d7695 Author: Raphael Geissert <[EMAIL PROTECTED]> Date: Thu Jun 19 22:11:10 2008 -0500 Update changelog to reflect changes made by upstream diff --git a/debian/changelog b/debian/changelog index 84476fc..e48cbb8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -xserver-xorg-video-openchrome (1:0.2.902+svn575-1) UNRELEASED; urgency=low +xserver-xorg-video-openchrome (1:0.2.902+svn577-1) UNRELEASED; urgency=low [ Timo Aaltonen ] * debian/patches/01_gen_pci_ids.diff: @@ -13,13 +13,14 @@ xserver-xorg-video-openchrome (1:0.2.902+svn575-1) UNRELEASED; urgency=low * New upstream snapshot. + Fixes some Xv issues. + Disables XvDMA for P4M890 and K8M890, as it is broken. ++ Enables CLE video engine on VM800/CN700. * Bump Standards-Version to 3.8.0 + Use find instead of findstring for DEB_BUILD_OPTIONS parsing in d/rules * Stripped enclosing chevrons from the unichrome link (Closes: #485957) - p.d.o displays the link with or without them, and looks ugly * Removed a useless lintian override - -- Raphael Geissert <[EMAIL PROTECTED]> Sun, 15 Jun 2008 16:38:30 -0500 + -- Raphael Geissert <[EMAIL PROTECTED]> Thu, 19 Jun 2008 22:10:17 -0500 xserver-xorg-video-openchrome (1:0.2.902+svn570-1) unstable; urgency=low commit da2e50a6485667c0d2c5fc1b2b15610523c705ef Author: ben <[EMAIL PROTECTED]> Date: Sun Jun 15 22:17:42 2008 + VM800/CN700 appears to have a CLE video engine (reported by Vincent Magnin). git-svn-id: http://svn.openchrome.org/svn/[EMAIL PROTECTED] e8d65cb0-85f4-0310-8831-c60e2a5ce829 diff --git a/src/via_driver.c b/src/via_driver.c index e51ed8e..0287e78 100644 --- a/src/via_driver.c +++ b/src/via_driver.c @@ -824,7 +824,6 @@ VIASetupDefaultOptions(ScrnInfoPtr pScrn) pVia->DRIIrqEnable = FALSE; break; case VIA_VM800: -pVia->VideoEngine = VIDEO_ENGINE_CME; pVia->agpEnable = FALSE; break; case VIA_K8M890: commit 0ca2f123dda4897f4d26c67f5fe4202deb04c784 Author: Raphael Geissert <[EMAIL PROTECTED]> Date: Sun Jun 15 16:39:12 2008 -0500 Removed a useless lintian override diff --git a/debian/changelog b/debian/changelog index c71ebf1..84476fc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -17,8 +17,9 @@ xserver-xorg-video-openchrome (1:0.2.902+svn575-1) UNRELEASED; urgency=low + Use find instead of findstring for DEB_BUILD_OPTIONS parsing in d/rules * Stripped enclosing chevrons from the unichrome link (Closes: #485957) - p.d.o displays the link with or without them, and looks ugly + * Removed a useless lintian override - -- Raphael Geissert <[EMAIL PROTECTED]> Thu, 12 Jun 2008 11:52:35 -0500 + -- Raphael Geissert <[EMAIL PROTECTED]> Sun, 15 Jun 2008 16:38:30 -0500 xserver-xorg-video-openchrome (1:0.2.902+svn570-1) unstable; urgency=low diff --git a/debian/overrides b/debian/overrides index 2884826..847b813 100644 --- a/debian/overrides +++ b/debian/overrides @@ -1,4 +
Bug#423775: xserver-xorg-core: Still experiencing crashes, will try Sid's 1.4 version.
Charles Plessy wrote: > I hope that the upgrade will fix the problem, it just seems too > complicated to handle. > Did you have a chance to upgrade? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#475112: xserver-xorg-video-intel: lockup with G33 on x86_64
found 475112 2:2.2.99.902-1 thank you Jerry Quinn wrote: >> Also, it would be good to know whether it is EXA related. Add >> Option "AccelMethod" "XAA" >> do the Device section of your xorg.conf. > > I've now seen the same X death with XAA enabled in 2.2.99.902-1, so > the problem is not dependent on EXA acceleration. Is it better with 2.3.2 or upstream git ? I am feeling like 2.3.2 fixed some of my lockups. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#475112: xserver-xorg-video-intel: lockup with G33 on x86_64
Processing commands for [EMAIL PROTECTED]: > found 475112 2:2.2.99.902-1 Bug#475112: xserver-xorg-video-intel: lockup with G33 on x86_64 Bug marked as found in version 2:2.2.99.902-1. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#474106: video-vesa: does not work on i815
Debian Live user wrote: > Package: xserver-xorg-video-vesa > Version: 1:1.3.0-1 > Severity: normal > File: video-vesa > > > Because the i815 card is misdetected by the X config scripts vesa is > used instead of intel driver. However, with vesa the card does not work, > only garbage is displayed on the screen. > Is it better with the latest X packages? Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#485465: thinkpad-acpi EC/NVRAM brightness sync errors
On Fri, 20 Jun 2008, [EMAIL PROTECTED] wrote: > H> 1. If it is *spamming* your logs with *lots* of EC/NVRAM out of sync > No, that message only happens when I tried > echo 0 > /sys/class/backlight/thinkpad_screen/brightness > to counteract xdm or whatever it is that turns my thinkpad to full > brightness, as mentioned in this bug report. > > But now that I use the better workaround of > echo level 0 > /proc/acpi/ibm/brightness > in /etc/X11/xdm/Xsetup I don't see that message anymore. They are supposed to do *exactly* the same thing in thinkpad-acpi... but hey, it *is* two code paths, one of which doesn't go through the horrible backlight sysfs class, but rather the even worse proc fs :-) Please tell me the exact version of the kernel and thinkpad-acpi in your box, I will look into it. Might be a timing issue, but it might be some real bug. I do remember I added better locking to that area of the code a while back. cat /proc/acpi/ibm/version would help, as well as uname -a output. > I hope I'm not doing anything bad. At least my workaround saves me > having to adjust the brightness back down each time I start xdm. No, you're not doing anything bad. It should be safe, as long as you don't press any brightness keys, and you do it BEFORE running xdm, or AFTER it has settled down. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: overwrite over upgrades on unstable package
Gabriel Filion a écrit :
> Hello,
>
> I run Debian unstable and I also happen to own a "Logitech Elite
> Keyboard". The howtos that I've found on google showed me that to make
> the keys on the upper part of the keyboard to work, I have to modify
> three files in /usr/share/x11/xkb -- namely symbols.dir symbols/inet and
> rules/base . I don't get all the keys working that way but I can still
> manage to use most of them.
>
> Now, my problem is that every time the package xkb-data is upgraded, it
> overwrites those three files without verifying if they were modified.
> And it is beginning to be annoying to have to restore the files from my
> backups, manually each time so that I don't break modifications the
> maintainers could have made to them.
>
> So, first, would you know of a way to get my keyboard working for all
> users on the computer with a less drastic modification?
> And if not, then second, is it possible to make those files be config
> files so that it checks for differences when the package gets upgraded?
> This way I could be aware that the files are getting changed and I could
> check a diff to see if anything is new at all.
>
> Thanks
>
> p.s.: if you need more details on the system, package versions or the
> changes I do in the files, I will be glad to provide the information you
> need.
>
I have the exact same problem with the same keyboard.
1) If you want all keys to work, just use the attached file
keymap-logitech (has to be run at boot time, I put it in rcS.d)
This is necessary because there is no kernel support for all those keys.
2) I use diversions to cope with the other problem (changes in
xkb-data). I attached my patch and my init program that takes care of
everything. Adapt it to your needs. However, it would really be better
if base.xml and other files be built from a bunch of files kept in a
directory, it would be easier to customize (system-wide). Please insert
the *patch files in /etc/X11/xkb, and the fixkeyboard in init.d (and
some rc*.d at your convenience).
Please see this message as one of support for your requests. :)
--
JCD
#!/bin/sh
#For the messenger key
setkeycodes e011 232 #Should be 145 . Yields 228
# For the webcam key
setkeycodes e012 233 #Should be 146 . Yields 142
# For the itouch key
setkeycodes e013 147 #works!
# For the shopping key
setkeycodes e014 148 #Is OK. Should be . Yields 159
#For the function keys not as function keys
setkeycodes e03b 187 #Is OK. Should be . Yields 131
setkeycodes e03c 188 #Is OK. Should be . Yields 247
setkeycodes e03d 118 #Is OK. Should be .Yields 123
setkeycodes e03e 189 #Should be 119 . Yields 132
setkeycodes e03f 120 #Is OK. Should be . Yields 139
setkeycodes e040 121 #Is OK. Should be . Yields 134
setkeycodes e041 122 #Is OK. Should be . Yields 121
setkeycodes e042 194 #Is OK. Should be . Yields 119
setkeycodes e043 195 #Is OK. Should be . Yields 149
setkeycodes e044 196 #Is OK. Should be . Yields 150
setkeycodes e057 215 #Is OK. Should be . Yields 120
setkeycodes e058 192 #Should be 216 . Yields 249
loadkeys << EOF
keycode 187 = F71
keycode 188 = F72
keycode 118 = F73
keycode 189 = F74
keycode 120 = F75
keycode 121 = F76
keycode 122 = F77
keycode 194 = F78
keycode 195 = F79
keycode 196 = F80
keycode 215 = F81
keycode 192 = F82
string F71=""
string F72=""
string F73=""
string F74=""
string F75=""
string F76=""
string F77=""
string F78=""
string F79=""
string F80=""
string F81=""
string F82=""
EOF
#!/bin/bash
### BEGIN INIT INFO
# Provides: fixkeyboard
# Required-Start:$local_fs
# Required-Stop: $local_fs
# Should-Start:
# Should-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: S 0 1 6
# Short-Description: Keyboard fixing
# Description: Adds logielite and Extended French keyboard
### END INIT INFO
KEYBOARD_PATCH=/etc/X11/xkb/keyboard.patch
XML_PATCH=/etc/X11/xkb/xml.patch
XKBDIR=/usr/share/X11/xkb
if [ ! -f "$KEYBOARD_PATCH" ]; then
exit 0
fi
echo -n "JCD keyboard: "
EXKBDIR=${XKBDIR//\//\\/}
# Delete any unwanted diversions
for i in $(dpkg-divert --list | grep ^local| grep /xkb/| cut -f4 -d' '); do rm
$i;dpkg-divert --remove $i > /dev/null; echo -n .; done
# First, check wether all diversions are active
case "$1" in
start|restart|reload)
find "$XKBDIR" -name '*.rej' | xargs rm 2>/dev/null
for i in $(grep ^+++ "$KEYBOARD_PATCH"| cut -f2 -d' '|cut -f1|sed -e
"s/^./$EXKBDIR/g"); do
B=$(dpkg-divert --list "$i")
if [ -z "$B" ]; then
if [ -e "$i.orig" ]; then
mv "$i.orig" "$i"
fi
dpkg-divert --add --rename --divert "$i.orig" "$i">/dev/null
echo -n "."
fi
cp "$i.orig" "$i"
done
dpkg-divert --add --rename --divert "/etc/X11/xkb/base.xml.orig"
"/etc/X11/xkb/base.xml">/dev/null
cp "/etc/X11/xkb/base.xml.orig" "/etc/X11/xkb/base.xml"
cd "$XKBDIR"
patch -p0 -s < "$KEYBOARD_PATCH"
cd /etc/X11/xkb
patch -p0 -s < "$XML_PATCH"
echo "enabled."
for i in $(grep ^+++ "
Bug#485465: thinkpad-acpi EC/NVRAM brightness sync errors
H> 1. If it is *spamming* your logs with *lots* of EC/NVRAM out of sync No, that message only happens when I tried echo 0 > /sys/class/backlight/thinkpad_screen/brightness to counteract xdm or whatever it is that turns my thinkpad to full brightness, as mentioned in this bug report. But now that I use the better workaround of echo level 0 > /proc/acpi/ibm/brightness in /etc/X11/xdm/Xsetup I don't see that message anymore. I hope I'm not doing anything bad. At least my workaround saves me having to adjust the brightness back down each time I start xdm. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
venturously elasticating
Hej, http://Ir.lettershell.cn What i'll have!33 that is exactly what you will of broken up and corroded rock, similar to the usual place. Ellie was different. I saw it at a feat of endurance and speed than a graceful arrived, with a gallant, dressed like a lord's one or two converts. Pas si mail i'm with you, eat her all the sooner if she was meek to them. [EMAIL PROTECTED] email contact links and up to.
Bug#487054: fix for 487054
tags 487054 +patch thanks add libxext-dev to the build dependencies to fix this bug -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: fix for 487054
Processing commands for [EMAIL PROTECTED]: > tags 487054 +patch Bug#487054: libxprintutil: FTBFS: checking for XPRINTUTIL... configure: error: Package requirements (x11 xp xt printproto xau) were not met: There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
overwrite over upgrades on unstable package
Hello, I run Debian unstable and I also happen to own a "Logitech Elite Keyboard". The howtos that I've found on google showed me that to make the keys on the upper part of the keyboard to work, I have to modify three files in /usr/share/x11/xkb -- namely symbols.dir symbols/inet and rules/base . I don't get all the keys working that way but I can still manage to use most of them. Now, my problem is that every time the package xkb-data is upgraded, it overwrites those three files without verifying if they were modified. And it is beginning to be annoying to have to restore the files from my backups, manually each time so that I don't break modifications the maintainers could have made to them. So, first, would you know of a way to get my keyboard working for all users on the computer with a less drastic modification? And if not, then second, is it possible to make those files be config files so that it checks for differences when the package gets upgraded? This way I could be aware that the files are getting changed and I could check a diff to see if anything is new at all. Thanks p.s.: if you need more details on the system, package versions or the changes I do in the files, I will be glad to provide the information you need. -- Gabriel Filion signature.asc Description: OpenPGP digital signature
[bts-link] source package xorg-server
# # bts-link upstream status pull for source package xorg-server # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #472205 # * https://bugs.freedesktop.org/show_bug.cgi?id=15169 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 472205 + fixed-upstream usertags 472205 - status-NEW usertags 472205 + status-RESOLVED resolution-FIXED thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package xorg
# # bts-link upstream status pull for source package xorg # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #484685 # * https://bugs.freedesktop.org/show_bug.cgi?id=15359 # * remote status changed: (?) -> NEW usertags 484685 + status-NEW # remote status report for #484685 # * https://bugs.freedesktop.org/show_bug.cgi?id=15359 # * remote status changed: (?) -> NEW usertags 484685 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package xdm
# # bts-link upstream status pull for source package xdm # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #486606 # * https://bugs.freedesktop.org/show_bug.cgi?id=10665 # * remote status changed: (?) -> NEW usertags 486606 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package mesa
# # bts-link upstream status pull for source package mesa # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #411141 # * https://bugs.freedesktop.org/show_bug.cgi?id=8732 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 411141 + fixed-upstream usertags 411141 - status-NEW usertags 411141 + status-RESOLVED resolution-FIXED # remote status report for #484180 # * https://bugs.freedesktop.org/show_bug.cgi?id=8724 # * remote status changed: (?) -> NEW usertags 484180 + status-NEW # remote status report for #478880 # * https://bugs.freedesktop.org/show_bug.cgi?id=16072 # * remote status changed: (?) -> NEW forwarded 478880 http://bugs.freedesktop.org/show_bug.cgi?id=16363, merged-upstream: https://bugs.freedesktop.org/show_bug.cgi?id=16072 usertags 478880 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package xserver-xorg-video-intel
# # bts-link upstream status pull for source package xserver-xorg-video-intel # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #478196 # * https://bugs.freedesktop.org/show_bug.cgi?id=15370 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 478196 + fixed-upstream usertags 478196 - status-NEW usertags 478196 + status-RESOLVED resolution-FIXED # remote status report for #483487 # * https://bugs.freedesktop.org/show_bug.cgi?id=15278 # * remote status changed: (?) -> NEW usertags 483487 + status-NEW # remote status report for #483487 # * https://bugs.freedesktop.org/show_bug.cgi?id=15278 # * remote status changed: (?) -> NEW usertags 483487 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package xkeyboard-config
# # bts-link upstream status pull for source package xkeyboard-config # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #463373 # * https://bugs.freedesktop.org/show_bug.cgi?id=16164 # * remote status changed: (?) -> NEW usertags 463373 + status-NEW # remote status report for #483687 # * https://bugs.freedesktop.org/show_bug.cgi?id=16164 # * remote status changed: (?) -> NEW usertags 483687 + status-NEW # remote status report for #483687 # * https://bugs.freedesktop.org/show_bug.cgi?id=16164 # * remote status changed: (?) -> NEW usertags 483687 + status-NEW thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package xorg-server
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package xorg-server > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #472205 > # * https://bugs.freedesktop.org/show_bug.cgi?id=15169 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 472205 + fixed-upstream Bug#472205: xorg-server: FTBFS on alpha in hw/xfree86/os-support/bus/axpPci.c There were no tags set. Tags added: fixed-upstream > usertags 472205 - status-NEW Bug#472205: xorg-server: FTBFS on alpha in hw/xfree86/os-support/bus/axpPci.c Usertags were: status-NEW. Usertags are now: . > usertags 472205 + status-RESOLVED resolution-FIXED Bug#472205: xorg-server: FTBFS on alpha in hw/xfree86/os-support/bus/axpPci.c There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package xserver-xorg-video-intel
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package xserver-xorg-video-intel > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #478196 > # * https://bugs.freedesktop.org/show_bug.cgi?id=15370 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 478196 + fixed-upstream Bug#478196: G35 via TMDS (HDMI=>DVI): wrong resolution There were no tags set. Tags added: fixed-upstream > usertags 478196 - status-NEW Bug#478196: G35 via TMDS (HDMI=>DVI): wrong resolution Usertags were: status-NEW. Usertags are now: . > usertags 478196 + status-RESOLVED resolution-FIXED Bug#478196: G35 via TMDS (HDMI=>DVI): wrong resolution There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #483487 > # * https://bugs.freedesktop.org/show_bug.cgi?id=15278 > # * remote status changed: (?) -> NEW > usertags 483487 + status-NEW Bug#483487: xserver-xorg-video-intel: font rendering problem hit me about two weeks ago There were no usertags set. Usertags are now: status-NEW. > # remote status report for #483487 > # * https://bugs.freedesktop.org/show_bug.cgi?id=15278 > # * remote status changed: (?) -> NEW > usertags 483487 + status-NEW Bug#483487: xserver-xorg-video-intel: font rendering problem hit me about two weeks ago Usertags were: status-NEW. Usertags are now: status-NEW. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package mesa
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package mesa > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #411141 > # * https://bugs.freedesktop.org/show_bug.cgi?id=8732 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 411141 + fixed-upstream Bug#411141: need Direct Rendering to Redirected windows There were no tags set. Tags added: fixed-upstream > usertags 411141 - status-NEW Bug#411141: need Direct Rendering to Redirected windows Usertags were: status-NEW. Usertags are now: . > usertags 411141 + status-RESOLVED resolution-FIXED Bug#411141: need Direct Rendering to Redirected windows There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #484180 > # * https://bugs.freedesktop.org/show_bug.cgi?id=8724 > # * remote status changed: (?) -> NEW > usertags 484180 + status-NEW Bug#484180: mesa: some ASM optimizations must be disabled for non-AMD 64-bit There were no usertags set. Usertags are now: status-NEW. > # remote status report for #478880 > # * https://bugs.freedesktop.org/show_bug.cgi?id=16072 > # * remote status changed: (?) -> NEW > forwarded 478880 http://bugs.freedesktop.org/show_bug.cgi?id=16363, > merged-upstream: https://bugs.freedesktop.org/show_bug.cgi?id=16072 Bug#478880: mayavi2: Opacity == 1.0, but still slightly transparent Forwarded-to-address changed from http://bugs.freedesktop.org/show_bug.cgi?id=16363 to http://bugs.freedesktop.org/show_bug.cgi?id=16363, merged-upstream: https://bugs.freedesktop.org/show_bug.cgi?id=16072. > usertags 478880 + status-NEW Bug#478880: mayavi2: Opacity == 1.0, but still slightly transparent There were no usertags set. Usertags are now: status-NEW. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487110: Packaging of the current git master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brice Goglin schrieb: > Patrick Matthäi wrote: >> Package: xserver-xorg-video-radeonhd >> Version: 1.2.1-2 >> Severity: wishlist >> >> Hello, >> >> I think it would be a good idea to ship lenny with the most recent >> radeonhd driver out from the git master branch. > > Well, we still have some time before Lenny gets frozen, so 1.2.2 or > 1.3.0. may even be available by then. For sure, we'll upload it. > > Brice > > Shouldn't it freeze next month? - -- Mit freundlichem Gruß / With kind regards, Patrick Matthäi E-Mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhalwwACgkQ2XA5inpabMdF1QCdHOhHTO9otcq9vbnDTkmMZJ+5 v4IAn3Ha6SPXtqHsY2pjHsZ4yRqeNrtU =7YSi -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487110: Packaging of the current git master
Patrick Matthäi wrote: > Package: xserver-xorg-video-radeonhd > Version: 1.2.1-2 > Severity: wishlist > > Hello, > > I think it would be a good idea to ship lenny with the most recent > radeonhd driver out from the git master branch. Well, we still have some time before Lenny gets frozen, so 1.2.2 or 1.3.0. may even be available by then. For sure, we'll upload it. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487110: Packaging of the current git master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: xserver-xorg-video-radeonhd Version: 1.2.1-2 Severity: wishlist Hello, I think it would be a good idea to ship lenny with the most recent radeonhd driver out from the git master branch. They've done some great work from 1.2.1 until yet and it should also fix many bugs (some which are also reported at Debian) and supporting newer hardware. The last point should be one of the most important reasons to use the master branch - so on "veryone" is able to use Debian on his Desktop (with X ;)). Here's also a list of bugs which could be closed then: #484902: xserver-xorg-video-radeonhd: Draws some parts of application windows incorrectly #476198: xserver-xorg-video-radeonhd: Cannot turn on a secondary screen without restarting X (xrandr-related problem) #476618: radeonhd: Can't change to other consoles after running Xserver Maybe more or less but I can't reproduce these three bugs on my both desktops anymore. And don't forget to build-depend on xutils-dev :) - -- Mit freundlichem Gruß / With kind regards, Patrick Matthäi E-Mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhaiOQACgkQ2XA5inpabMf1KACglwqouBPESiCjtRHrPWZF8uQs X5IAnRusoL1Q6tdq4cv8EF4WfId9NvV+ =PZNd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#485465: thinkpad-acpi EC/NVRAM brightness sync errors
Well, at least the thinkpad-acpi angle I can help with. I am the kernel maintainer for thinkpad-acpi. 1. If it is *spamming* your logs with *lots* of EC/NVRAM out of sync messages, you need a newer thinkpad-acpi. Depending on your kernel version, a backport will be available at ibm-acpi.sf.net. 2. There are just two ways to make EC/NVRAM get out of sync: BIOS bugs, or doing something you are never supposed to do. The X.org server does not fit the profile for "doing something you are never supposed to do" AFAIK. Anything writing directly to the NVRAM, or accessing either thinkpad-acpi or ACPI at the time the firmware is doing something to brightness itself, or misconfiguring thinkpad-acpi, or accessing both thinkpad-acpi and ACPI at the same time, *will* cause breakage. Basically, you must NOT react to brightness changes on a thinkpad in userspace by trying to change brightness again, EXCEPT if you managed to block the BIOS from doing so, and the only way to do it is through X.org's trick with the GPU registers, which doesn't work on every thinkpad out there, either. So, as a rule, do NOT enable the brightness keys in thinkpad-acpi hotkey mask on any ThinkPad from IBM. I *MEAN* it. If the thinkpad is changing the brightness through firmware by itself, which is the norm for IBM thinkpads, you must never enable the brightness keys in thinkpad-acpi's hotkey_mask unless you REALLY, REALLY know what you're doing. thinkpad-acpi defaults are already sane, but it is a common error to misconfigure it in HAL or manually, and outdated documentation you find everywhere in the net doesn't help putting this issue to rest. You only enable thinkpad brightness keys when a) the thinkpad doesn't handle brightness on its own (thinkpad-acpi already knows when to do this), or b) you managed to get x.org intel xserver to BLOCK the thinkpad BIOS to change brightness on its own, and you now have to handle the keys through xbacklight. Some Ubuntu changes to HAL, which I belive DID land in Debian from HAL upstream where they filtered to (argh!) are especially good at completely fucking all the brightness control on thinkpads. You cannot enable the brightness keys and have them issue BRIGHTNESS_UP/DOWN events when the firmware is active, as the brightness changes will already be in-flight and something else trying to do the same change (usually by abusing thinkpad-acpi) will cause trouble. Anything stupid enough to also write to every brightness control it finds in sysfs in a ~1s window can also cause the same issue, so it doesn't have to be HAL. It could be a gnome or kde helper too, for example. So, that's it. You either silence the firmware, or you MUST NOT do any brightness control based on *the brightness key presses*, EVER. If you do, you will always hit the window where the firmware is also doing a change, and bad things happen. thinkpad-acpi cannot silence the firmware (it tries, but it has no effect), the ACPI AML does not support it on most thinkpads. If X.org can't do it on a given thinkpad, nobody can. If feedback loops caused by bad handling of the brightness keys are taken out of the mess, there is still one thing you cannot do: You cannot use both ACPI video brightness control, and thinkpad-acpi brightness control AT THE SAME TIME. You can use one, and after a while, the other. This is in the process of being fixed in the kernel, but it will take a while. ACPI video clashing with thinkpad-acpi shouldn't be a problem on a R50, I don't believe it has ACPI video brightness control interface. But if it does, either disable it, or disable thinkpad-acpi's to make sure nothing in userspace is tempted into breaking things. And send me a note, it is something I would like to handle automatically in the driver. Newer enough thinkpad-acpi has an option to disable its brightness control interface that you can use to check if things get better for your userspace configuration. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#487057: libxprintapputil: FTBFS: checking for XPRINTAPPUTIL... configure: error: Package requirements (x11 xp xprintutil printproto xau) were not met:
Package: libxprintapputil
Version: 1:1.0.1.xsf1-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080618 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
i386.
Relevant part:
> /usr/bin/fakeroot debian/rules clean
> rm -f stampdir/genscripts
> rm -f debian/*.config \
> debian/*.postinst \
> debian/*.postrm \
> debian/*.preinst \
> debian/*.prerm
> rm -f stampdir/patch
> Unapplying patches...nothing to do.
> dh_testdir
> rm -f .pc patches
> rm -rf stampdir build-tree
> rm -rf imports
> dh_clean debian/shlibs.local \
>debian/MANIFEST.i386 debian/MANIFEST.i386.new \
>debian/po/pothead
> dh_testdir
> dh_testroot
> rm -f build-stamp
> rm -f config.cache config.log config.status
> rm -f */config.cache */config.log */config.status
> rm -f conftest* */conftest*
> rm -rf autom4te.cache */autom4te.cache
> rm -rf obj-*
> dh_clean
> dpkg-source -b libxprintapputil-1.0.1.xsf1-2
> dpkg-source: warning: source directory 'libxprintapputil-1.0.1.xsf1-2' is not
> - 'libxprintapputil-1.0.1.xsf1'
> dpkg-source: warning: .orig directory name libxprintapputil-1.0.1.xsf1-2.orig
> is not - (wanted libxprintapputil-1.0.1.xsf1.orig)
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building libxprintapputil using existing
> libxprintapputil_1.0.1.xsf1.orig.tar.gz
> dpkg-source: info: building libxprintapputil in
> libxprintapputil_1.0.1.xsf1-2.diff.gz
> dpkg-source: info: building libxprintapputil in
> libxprintapputil_1.0.1.xsf1-2.dsc
> debian/rules build
> mkdir stampdir
> >stampdir/stampdir
> if [ ! -e stampdir/patches ]; then \
> mkdir stampdir/patches; \
> ln -s stampdir/patches .pc; \
> echo 2 >stampdir/patches/.version; \
> fi; \
> if [ ! -e stampdir/log ]; then \
> mkdir stampdir/log; \
> fi; \
> if [ ! -e patches ]; then \
> ln -s debian/patches patches; \
> fi; \
> >stampdir/prepare
> if ! [ `which quilt` ]; then \
> echo "Couldn't find quilt. Please install it or add it to the
> build-depends for this package."; \
> exit 1; \
> fi; \
> if quilt next; then \
> echo -n "Applying patches..."; \
> if quilt push -a -v >stampdir/log/patch 2>&1; then \
> echo "successful."; \
> else \
> echo "failed! (check stampdir/log/patch for details)"; \
> exit 1; \
> fi; \
> else \
> echo "No patches to apply"; \
> fi; \
> >stampdir/patch
> No patches in series
> No patches to apply
> dh_testdir
> test -d obj-i486-linux-gnu || mkdir obj-i486-linux-gnu
> cd obj-i486-linux-gnu && \
> ../configure --prefix=/usr --mandir=\${prefix}/share/man \
>--infodir=\${prefix}/share/info --build=i486-linux-gnu
> --enable-fc \
>CFLAGS="-Wall -g -O2"
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking build system type... i486-pc-linux-gnu
> checking host system type... i486-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how
Bug#487054: libxprintutil: FTBFS: checking for XPRINTUTIL... configure: error: Package requirements (x11 xp xt printproto xau) were not met:
Package: libxprintutil
Version: 1:1.0.1.xsf1-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080618 qa-ftbfs
Justification: FTBFS on i386
Hi,
During a rebuild of all packages in sid, your package failed to build on
i386.
Relevant part:
> /usr/bin/fakeroot debian/rules clean
> rm -f stampdir/genscripts
> rm -f debian/*.config \
> debian/*.postinst \
> debian/*.postrm \
> debian/*.preinst \
> debian/*.prerm
> rm -f stampdir/patch
> Unapplying patches...nothing to do.
> dh_testdir
> rm -f .pc patches
> rm -rf stampdir build-tree
> rm -rf imports
> dh_clean debian/shlibs.local \
>debian/MANIFEST.i386 debian/MANIFEST.i386.new \
>debian/po/pothead
> dh_testdir
> dh_testroot
> rm -f build-stamp
> rm -f config.cache config.log config.status
> rm -f */config.cache */config.log */config.status
> rm -f conftest* */conftest*
> rm -rf autom4te.cache */autom4te.cache
> rm -rf obj-*
> dh_clean
> dpkg-source -b libxprintutil-1.0.1.xsf1-2
> dpkg-source: warning: source directory 'libxprintutil-1.0.1.xsf1-2' is not
> - 'libxprintutil-1.0.1.xsf1'
> dpkg-source: warning: .orig directory name libxprintutil-1.0.1.xsf1-2.orig is
> not - (wanted libxprintutil-1.0.1.xsf1.orig)
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building libxprintutil using existing
> libxprintutil_1.0.1.xsf1.orig.tar.gz
> dpkg-source: info: building libxprintutil in
> libxprintutil_1.0.1.xsf1-2.diff.gz
> dpkg-source: info: building libxprintutil in libxprintutil_1.0.1.xsf1-2.dsc
> debian/rules build
> mkdir stampdir
> >stampdir/stampdir
> if [ ! -e stampdir/patches ]; then \
> mkdir stampdir/patches; \
> ln -s stampdir/patches .pc; \
> echo 2 >stampdir/patches/.version; \
> fi; \
> if [ ! -e stampdir/log ]; then \
> mkdir stampdir/log; \
> fi; \
> if [ ! -e patches ]; then \
> ln -s debian/patches patches; \
> fi; \
> >stampdir/prepare
> if ! [ `which quilt` ]; then \
> echo "Couldn't find quilt. Please install it or add it to the
> build-depends for this package."; \
> exit 1; \
> fi; \
> if quilt next; then \
> echo -n "Applying patches..."; \
> if quilt push -a -v >stampdir/log/patch 2>&1; then \
> echo "successful."; \
> else \
> echo "failed! (check stampdir/log/patch for details)"; \
> exit 1; \
> fi; \
> else \
> echo "No patches to apply"; \
> fi; \
> >stampdir/patch
> No patches in series
> No patches to apply
> dh_testdir
> test -d obj-i486-linux-gnu || mkdir obj-i486-linux-gnu
> cd obj-i486-linux-gnu && \
> ../configure --prefix=/usr --mandir=\${prefix}/share/man \
>--infodir=\${prefix}/share/info --build=i486-linux-gnu
> --enable-fc \
>CFLAGS="-Wall -g -O2"
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking build system type... i486-pc-linux-gnu
> checking host system type... i486-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
>
Bug#484087: xserver-xorg-video-intel: Another logfile
Sander Marechal wrote: > Package: xserver-xorg-video-intel > Version: 2:2.3.1-1 > Followup-For: Bug #484087 > > > The lock-up has happened again. This time it happened right when I was > working. Usually it locks up when I'm away and xscreensaver is running, > but I'm away from my computer a lot (meetings) so that's probably pure > chance. > > What can I do to further debug this issue? > Try 2.3.2 from unstable. Then try upstream git master. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ati_6.8.191-2_i386.changes is NEW
xserver-xorg-video-ati-dbg_6.8.191-2_i386.deb to pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-ati-dbg_6.8.191-2_i386.deb xserver-xorg-video-ati_6.8.191-2.diff.gz to pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.8.191-2.diff.gz xserver-xorg-video-ati_6.8.191-2.dsc to pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.8.191-2.dsc xserver-xorg-video-ati_6.8.191-2_i386.deb to pool/main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.8.191-2_i386.deb (new) xserver-xorg-video-radeon-dbg_6.8.191-2_i386.deb extra x11 X.Org X server -- ATI Radeon display driver (debugging symbols) This driver for the X.Org X server (see xserver-xorg for a further description) provides support for the ATI Radeon and FireGL series. It provides the 'radeon' driver. . This driver provides support for Radeon and FireGL series ATI cards. . This package provides debugging symbols for the Xorg X server ATI Radeon display driver. (new) xserver-xorg-video-radeon_6.8.191-2_i386.deb optional x11 X.Org X server -- ATI Radeon display driver This driver for the X.Org X server (see xserver-xorg for a further description) provides support for the ATI Radeon and FireGL series. It provides the 'radeon' driver. . Note that this is not the same as the ATI-provided, binary-only, 'fglrx' driver, which provides additional 3D functionality for some newer Radeon cards, but is not supported. . This driver provides support for Radeon and FireGL series ATI cards. . More information about X.Org can be found at: http://www.X.org> http://xorg.freedesktop.org> http://lists.freedesktop.org/mailman/listinfo/xorg> . This package is built from the X.org xf86-video-ati driver module. Changes: xserver-xorg-video-ati (1:6.8.191-2) unstable; urgency=low . * Split the package into into the -ati package containing the ati driver wrapper, and xserver-xorg-video-radeon containing the actual radeon sub-driver. xserver-xorg-video-ati now depends on -r128, -mach64 and -radeon while -ati-dbg depends on their corresponding -dbg packages. Override entries for your package: xserver-xorg-video-ati-dbg_6.8.191-2_i386.deb - extra x11 xserver-xorg-video-ati_6.8.191-2.dsc - source x11 xserver-xorg-video-ati_6.8.191-2_i386.deb - optional x11 Announcing to [EMAIL PROTECTED] Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of xserver-xorg-video-ati_6.8.191-2_i386.changes
xserver-xorg-video-ati_6.8.191-2_i386.changes uploaded successfully to localhost along with the files: xserver-xorg-video-ati_6.8.191-2.dsc xserver-xorg-video-ati_6.8.191-2.diff.gz xserver-xorg-video-ati_6.8.191-2_i386.deb xserver-xorg-video-ati-dbg_6.8.191-2_i386.deb xserver-xorg-video-radeon_6.8.191-2_i386.deb xserver-xorg-video-radeon-dbg_6.8.191-2_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ati: Changes to 'refs/tags/xserver-xorg-video-ati-1_6.8.191-2'
Tag 'xserver-xorg-video-ati-1_6.8.191-2' created by Brice Goglin <[EMAIL PROTECTED]> at 2008-06-19 07:07 + Tagging upload of xserver-xorg-video-ati 1:6.8.191-2 to unstable. Changes since xserver-xorg-video-ati-1_6.8.191-1: Brice Goglin (2): Split a -radeon binary package out of -ati Prepare changelog for upload --- debian/changelog | 10 ++ debian/control| 49 -- debian/patches/01_gen_pci_ids.diff|6 +-- debian/rules |4 +- debian/xserver-xorg-video-ati.install |4 -- debian/xserver-xorg-video-ati.manpages|2 - debian/xserver-xorg-video-radeon.install |3 + debian/xserver-xorg-video-radeon.links|1 debian/xserver-xorg-video-radeon.manpages |1 src/Makefile.in |6 +-- 10 files changed, 66 insertions(+), 20 deletions(-) --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xserver-xorg-video-ati: Changes to 'debian-unstable'
ChangeLog | 2182 ++ Makefile.am | 11 Makefile.in |8 README.ati| 828 - README.ati.sgml | 648 README.r128 | 160 - README.r128.sgml | 138 aclocal.m4| 14 config.h.in | 18 configure | 356 +- configure.ac | 83 debian/NEWS |9 debian/changelog | 72 debian/control| 69 debian/patches/01_gen_pci_ids.diff|8 debian/rules |6 debian/xserver-xorg-video-ati.install |4 debian/xserver-xorg-video-ati.manpages|2 debian/xserver-xorg-video-radeon.install |3 debian/xserver-xorg-video-radeon.links|1 debian/xserver-xorg-video-radeon.manpages |1 debian/xsfbs/xsfbs-autoreconf.mk | 150 - debian/xsfbs/xsfbs.mk | 102 debian/xsfbs/xsfbs.sh | 394 +- ltmain.sh |2 man/Makefile.am |5 man/Makefile.in |5 man/r128.man | 156 - man/radeon.man| 40 src/AtomBios/CD_Operations.c |9 src/AtomBios/Decoder.c|9 src/AtomBios/includes/CD_Common_Types.h |8 src/AtomBios/includes/ObjectID.h | 928 +++--- src/AtomBios/includes/atombios.h | 50 src/Makefile.am | 91 src/Makefile.in | 305 -- src/ati.c |6 src/ati.h |3 src/ati_pciids_gen.h | 28 src/atiadjust.c | 134 src/atiadjust.h | 31 src/atiaudio.c| 50 src/atiaudio.h| 51 src/atibank.c | 114 src/atibank.h | 44 src/atibus.c | 123 src/atibus.h | 49 src/atichip.c | 271 - src/atichip.h | 94 src/aticlock.c| 443 -- src/aticlock.h| 62 src/aticonfig.c | 506 --- src/aticonsole.c | 816 - src/aticonsole.h | 43 src/aticrtc.h | 42 src/aticursor.h | 42 src/atidac.c | 462 --- src/atidac.h | 99 src/atidecoder.c | 50 src/atidecoder.h | 51 src/atidga.c | 483 --- src/atidga.h | 36 src/atidri.c | 1640 --- src/atidri.h | 49 src/atidripriv.h | 57 src/atidsp.c | 302 -- src/atidsp.h | 35 src/atii2c.c | 399 -- src/atii2c.h | 48 src/atiload.c | 98 src/atiload.h | 32 src/atilock.c | 537 --- src/atilock.h | 31 src/atimach64.c | 1341 - src/atimach64.h | 36 src/atimach64accel.c | 1068 --- src/atimach64accel.h | 42 src/atimach64cursor.c | 426 -- src/atimach64exa.c| 696 src/atimach64i2c.c| 469 --- src/atimach64i2c.h| 32 src/atimach64io.c | 103 src/atimach64io.h | 421 -- src/atimach64probe.c | 289 - src/atimach64probe.h | 32 src/atimach64render.c | 898 -- src/atimach64version.h| 59 src/atimach64xv.c | 1686 --- src/atimisc.c | 78 src/atimode.c | 1084 --- src/atimode.h | 35 src/atimodule.c |2 src/atioption.h | 98 src/atipreinit.c | 2509 src/atipreinit.h | 30 src/atiprint
