[Ubuntu-x-swat] [Bug 385723] Re: no backlight support for laptop (hal depreciation regression)

So it's not a smartdimmer problem; X.org upstream says it's a bug in the nvidia driver. ** Changed in: xorg-server (Ubuntu) Status: Triaged => Invalid ** Changed in: gnome-power Status: New => Invalid -- no backlight support for laptop (hal depreciation regression) https://bugs.la

[Ubuntu-x-swat] [Bug 394273] Re: [i945] defaults to non-native screen resolutions (mode change from KMS)

It surprises me that you consider this driver specific. NB that the driver correctly detected both screen resolutions. X just decided for a bad "common denominator" instead of defaulting xrandr to be "only external screen with full resolution" or at least driving both screens with 1280x800; so that

[Ubuntu-x-swat] [Bug 311895] Re: [i945] spontaneous black screen (major pipe-A underrun)

With KMS I never had this problem. Upstream said it worked by sheer accident, but now then are feeding the real patches to upstream. I don't think we need to track this any more. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- [i945] spontaneous black screen (major pipe-A

[Ubuntu-x-swat] [Bug 407816] Re: vmmouse should be in main (reverted to universe in intrepid)

I re-promoted -vmmouse to main, but it needs to be depended on by -input-all to stay in main. ** Package changed: xserver-xorg-input-vmmouse (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New => Triaged -- vmmouse should be in main (reverted to universe in intrepid) https

[Ubuntu-x-swat] [Bug 272606] Re: ABNT2 Numpad Keyboard keys misbehaving

** Changed in: xkeyboard-config (Ubuntu Karmic) Status: Confirmed => Fix Committed -- ABNT2 Numpad Keyboard keys misbehaving https://bugs.launchpad.net/bugs/272606 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in ubuntu. _

[Ubuntu-x-swat] [Bug 256021] Re: glxinfo crashed with SIGSEGV in __libc_start_main()

** Package changed: mesa-utils (Ubuntu Jaunty) => mesa (Ubuntu Jaunty) -- glxinfo crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/256021 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. ___

[Ubuntu-x-swat] [Bug 347569] Re: [RS482] low performance due to removal of _tnl_ProgramCacheInit()

Accepted mesa into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: mesa (Ubuntu Jaunty)

[Ubuntu-x-swat] [Bug 228399] Re: Closing lid results in kernel panic visible on VT-1

Accepted linux into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Tags added: verification-needed -- C

[Ubuntu-x-swat] [Bug 327673] Re: glxgears crashed with SIGSEGV due to no GLX on display :0

But should a program really crash if it relies on glx and it's not available? It should handle this condition more gracefully IMHO. Bryce, what should apport do here? Is it safe to say that it should ignore _all_ crashes which end in libGL if 'extension "GLX" missing on display' occurs in /var/log

[Ubuntu-x-swat] [Bug 376220] Re: Kubuntu: package libglu1-mesa 7.4-0ubuntu3.1 failed to install/upgrade: package libglu1-mesa is already installed and configured

** Changed in: apport (Ubuntu) Status: New => Invalid -- Kubuntu: package libglu1-mesa 7.4-0ubuntu3.1 failed to install/upgrade: package libglu1-mesa is already installed and configured https://bugs.launchpad.net/bugs/376220 You received this bug notification because you are a member of U

[Ubuntu-x-swat] [Bug 368282] Re: apport sometimes prints "Cannot open display" when run over ssh

This actually comes from xorg's package hook. I guess there's no way around having $DISPLAY set for some commands, but maybe it can be quiesced a bit. Something like this, perhaps: if os.environ.get('DISPLAY'): # do commands which need $DISPLAY # do commands which don't need $DISPLAY **

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, blank screen

** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- [2.6.32-19 regression] Does not check lid status any more, blank screen https://bugs.launchpad.net/bugs/556253 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, blank screen

To eliminate this part, it's the same situation with plymouth uninstalled. Hm, so xrandr seems to also think that both are running: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 VGA1 disconnected (normal left inverted right x axis y axis) LVDS1 connected 1024x768+0+0 (norma

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

** Summary changed: - [2.6.32-19 regression] Does not check lid status any more, blank screen + [2.6.32-19 regression] Does not check lid status any more, external screen powered off -- [2.6.32-19 regression] Does not check lid status any more, external screen powered off https://bugs.launchpa

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

As expected, booting with video=LVDS-1:d works, but with that I never get back the LVDS, not even after opening the lid. -- [2.6.32-19 regression] Does not check lid status any more, external screen powered off https://bugs.launchpad.net/bugs/556253 You received this bug notification because you

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

Just to complete the data collection and followup to the IRC discussion with Andy: * Same result with VGA instead of DVI * When I force the resolution in xorg.conf, it works: Section "Screen" Identifier "MyScreen" SubSection "Display" Modes "1280x1024"

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

Chase, I tried the package, but no difference. The changelog speaks about fixing the "change resolution" Fn key, which is an unrelated problem. This one happens without any custom xrandr configuration. -- [2.6.32-19 regression] Does not check lid status any more, external screen powered off htt

Re: [Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

al monitor). So the root problem here (apart from the "doesn't work as perfectly as before in lucid") is why the DVI powers off. Getting back the better behavior of previous lucid versions with driving DVI in native resolution is certainly a bonus, but I don't see how to achieve

[Ubuntu-x-swat] [Bug 556872] Re: [lucid] [nouveau] blank screen on Dell Latitude E6410 (NVS 3100M [10de:0a6c])

** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => Chris Halse Rogers (raof) -- [lucid] [nouveau] blank screen on Dell Latitude E6410 (NVS 3100M [10de:0a6c]) https://bugs.launchpad.net/bugs/556872 You received this bug notificatio

[Ubuntu-x-swat] [Bug 556856] Re: [lucid] [nouveau] blank screen on Dell Precision M4500 [10de:0cbc]

** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => Chris Halse Rogers (raof) -- [lucid] [nouveau] blank screen on Dell Precision M4500 [10de:0cbc] https://bugs.launchpad.net/bugs/556856 You received this bug notification because y

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

> Alternatively, can you try booting with i915.fbpercrtc=1? Again no perceivable difference. Unlike with the SVIDEO-1:d test, I also opened and closed the lid, to check that lid detection and resolution updates still work (they do). Thus this X.org log is slightly longer than the SVIDEO one. ** A

[Ubuntu-x-swat] [Bug 556253] Re: [2.6.32-19 regression] Does not check lid status any more, external screen powered off

> video=SVIDEO-1:d No perceivable difference, DVI stays off and LVDS is on in non-native 1024x768 mode. ** Attachment added: "Xorg log with video=SVIDEO-1:d" http://launchpadlibrarian.net/43426771/Xorg.log.SVIDEO-1%3Ad -- [2.6.32-19 regression] Does not check lid status any more, external sc

[Ubuntu-x-swat] [Bug 544012] Re: Doesn't boot into X if external screen connected to dvi port

*** This bug is a duplicate of bug 556253 *** https://bugs.launchpad.net/bugs/556253 ** Tags removed: shutdown-hang ** This bug has been marked a duplicate of bug 556253 [2.6.32-19 regression] Does not check lid status any more, external screen powered off -- Doesn't boot into X if exte

[Ubuntu-x-swat] [Bug 554100] Re: After fresh install, but everything seems to be working

Bryce, this was detected by the "shutdown hang" apport hook. It means that some process was still running during shutdown when /etc/init.d/sendsigs was run, and it didn't get killed by SIGTERM: root 1212 0.7 0.1 7296 3012 tty7 Ss+ 19:48 0:00 /usr/bin/X :0 -nr -verbose -auth /var/

[Ubuntu-x-swat] [Bug 547119] Re: [945GME] X freeze computer shutdown

*** This bug is a duplicate of bug 554100 *** https://bugs.launchpad.net/bugs/554100 ** This bug has been marked a duplicate of bug 554100 X process still running on shutdown even after SIGTERM -- [945GME] X freeze computer shutdown https://bugs.launchpad.net/bugs/547119 You received this

[Ubuntu-x-swat] [Bug 540753] Re: crash improper functining of system after upgrade

*** This bug is a duplicate of bug 554100 *** https://bugs.launchpad.net/bugs/554100 ** This bug has been marked a duplicate of bug 554100 X process still running on shutdown even after SIGTERM -- crash improper functining of system after upgrade https://bugs.launchpad.net/bugs/540753 You

[Ubuntu-x-swat] [Bug 543347] Re: does not terminate at computer shutdown

Potential duplicate of bug 554100 -- does not terminate at computer shutdown https://bugs.launchpad.net/bugs/543347 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ M

[Ubuntu-x-swat] [Bug 537385] Re: does not terminate at computer shutdown

Potential duplicate of bug 554100 -- does not terminate at computer shutdown https://bugs.launchpad.net/bugs/537385 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ M

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Timo, I checked our current libX11, and XCreatePixmap() already calls _XAllocID() inside a LockDisplay() block, so it seems that's not it? -- synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. https://bugs.launchpad.net/bugs/507062 You rece

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Looking at the stack traces, I'm convinced that bug 458989 and its dupes are not fixed, but duplicates of this bug. 458989 hasn't been closed with an upload, just with an "I do not get this any more", but since this bug happens randomy and there is no known reproducer, it's probably still relevant.

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

** Bug watch added: freedesktop.org Bugzilla #27552 http://bugs.freedesktop.org/show_bug.cgi?id=27552 ** Also affects: xlibs via http://bugs.freedesktop.org/show_bug.cgi?id=27552 Importance: Unknown Status: Unknown -- synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XA

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Does anyone have a recipe how to reproduce these crashes? -- synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. https://bugs.launchpad.net/bugs/507062 You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

(not "triaged" yet -- the bug isn't understood, and no reproducer) ** Changed in: libx11 (Ubuntu Lucid) Status: Triaged => Incomplete -- synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed. https://bugs.launchpad.net/bugs/507062 You re

[Ubuntu-x-swat] [Bug 529882] Re: user switch crashes with process termination (lucid alpha)

nation (lucid alpha) + black screen when switching between multiple X session ** Changed in: xserver-xorg-video-ati (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) -- black screen when switching between multiple X session https://bugs.launchpad.net/bugs/529882 You received this bug not

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Could some people who got a crash like this please attach their /var/log/Xorg.0.log? I'm interested in seeing whether this only affects particular video drivers/graphics cards, or only particular extensions. Thank you! -- synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Asser

[Ubuntu-x-swat] [Bug 516520] Re: pam_unix(gdm:auth): conversation failed

** Package changed: gdm (Ubuntu Lucid) => nvidia-graphics-drivers-96 (Ubuntu Lucid) ** Changed in: nvidia-graphics-drivers-96 (Ubuntu Lucid) Status: Incomplete => Confirmed ** Summary changed: - pam_unix(gdm:auth): conversation failed + login fails with nvidia driver 96 -- login fails w

[Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Thanks Scott, Robert, fredrik. The three of you are all using the proprietary Nvidia driver. It might be a coincidence, or just pure luck with a sample size of three. :-) Did anyone here experience this kind of crash who is _not_ using the proprietary driver? I. e. either an NVidia card with the fr

Re: [Ubuntu-x-swat] [Bug 507062] Re: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

David Pothecary [2010-04-16 8:57 -]: > Apologies, GMA 950. Thanks. So let's discard the idea that this is driver specific. I followed up on the upstream bug with some analysis of all the duplicates and the used client-side extensions. -- synaptic assert failure: synaptic: ../../src/xcb_io.

[Ubuntu-x-swat] [Bug 516520] Re: login fails with nvidia driver 96

ged in: nvidia-graphics-drivers-96 (Ubuntu Lucid) Assignee: Martin Pitt (pitti) => Alberto Milone (albertomilone) ** This bug has been marked a duplicate of bug 553200 Mouse and keyboard stop working after selecting user -- login fails with nvidia driver 96 https://bugs.launchpad.ne

[Ubuntu-x-swat] [Bug 567699] Re: Ensure nvidia package works in future for PAE kernel installs

I don't see how this would help at all? All kernel-headers-* flavours have a Provides: linux-headers. Unfortunately this is a highly nontrivial problem. There is no way to express "we need the same kernel header flavour as the installed kernel" in terms of package dependencies. The only thing that

[Ubuntu-x-swat] [Bug 565981] Re: [KMS] gem objects not deallocated

Robert, from the current discussion it seems that it's quite safe to roll back the two glx 1.4 and the 114 patch. Personally I would rather like to see this fixed in final, since it's such a notable regression and the 114 patch was just introduced a few days ago. I heard that the rdepends were tes

[Ubuntu-x-swat] [Bug 565981] Re: [KMS] gem objects not deallocated

I started a testing wiki page at https://wiki.ubuntu.com/X/Testing/GEMLeak I'll send a call for testing to ubuntu-de...@. -- [KMS] gem objects not deallocated https://bugs.launchpad.net/bugs/565981 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xo

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

Ah, *headdesk*, thanks for figuring this out! I'll create and commit a test case and then merge your branch. ** Changed in: pkg-create-dbgsym (Ubuntu) Status: Confirmed => In Progress ** Changed in: pkg-create-dbgsym (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

Test case: http://bazaar.launchpad.net/~ubuntu-core-dev/pkg-create-dbgsym/ubuntu/revision/176 Fix: http://bazaar.launchpad.net/~ubuntu-core-dev/pkg-create-dbgsym/ubuntu/revision/177 ** Changed in: pkg-create-dbgsym (Ubuntu) Status: In Progress => Fix Committed ** Changed in: pkg-create-d

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

So with that xorg-server just needs a rebuild. If one is done for bug 565981 anyway, then this will just be solved along with it, otherwise you have my ack to do a no-change upload for right-after-RC to get the ddebs back. Thanks again, Tormod! ** Changed in: xorg-server (Ubuntu) Status: C

Re: [Ubuntu-x-swat] [Bug 565981] Re: [KMS] gem objects not deallocated

Linuxexperte [2010-04-22 15:38 -]: > 241090560 object bytes This is quite much, but in the end it's really noticeable if you are affected -- after a few hours your system becomes totally sluggish and feels like a tar pit. On my system, shutdown took about a minute, too. > Can anybody give me

[Ubuntu-x-swat] [Bug 553647] Re: xserver crash (repeatable, triggered by drawing circle/ellipse e.g. in xfig)

** Also affects: xorg-server (Ubuntu Lucid) Importance: High Status: Triaged -- xserver crash (repeatable, triggered by drawing circle/ellipse e.g. in xfig) https://bugs.launchpad.net/bugs/553647 You received this bug notification because you are a member of Ubuntu-X, which is subscribe

[Ubuntu-x-swat] [Bug 496363] Re: Installing nvidia kills xorg on non-nvidia systems

** Also affects: nvidia-graphics-drivers (Ubuntu Lucid) Importance: Wishlist Assignee: Alberto Milone (albertomilone) Status: Triaged ** Changed in: nvidia-graphics-drivers (Ubuntu Lucid) Status: Triaged => Won't Fix -- Installing nvidia kills xorg on non-nvidia systems htt

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

** Changed in: pkg-create-dbgsym (Ubuntu) Status: Confirmed => In Progress ** Changed in: xorg-server (Ubuntu) Status: Fix Released => Confirmed ** Changed in: xorg-server (Ubuntu) Milestone: ubuntu-10.04 => None -- many -dbg packages have debug symbols mismatch https://bugs.l

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

Argh, I know why. It's because on Soyuz we currently disable adding the ddebs to debian/files, thus the grep wouldn't find them. -- many -dbg packages have debug symbols mismatch https://bugs.launchpad.net/bugs/562418 You received this bug notification because you are a member of Ubuntu-X, which

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

Fixed for good in http://bazaar.launchpad.net/~ubuntu-core-dev/pkg- create-dbgsym/ubuntu/revision/180 now. Sorry about that! ** Changed in: pkg-create-dbgsym (Ubuntu) Milestone: None => lucid-updates ** Also affects: pkg-create-dbgsym (Ubuntu Lucid) Importance: High Assignee: Mar

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

** Description changed: + SRU INFORMATION: + Impact: Produces empty ddebs and broken debug links on packages which call dh_strip on a package more than once, when being built on Soyuz (not locally). + Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/pkg-create-dbgsym/ubuntu/revision/180 + Tes

[Ubuntu-x-swat] [Bug 562418] Re: many -dbg packages have debug symbols mismatch

I built xorg-server locally with this package, and it works now: dh_strip -pxserver-xorg-core --dbg-package=xserver-xorg-core-dbg dh_strip debug symbol extraction: all non-arch-all packages for this build platform amd64: xserver-xorg-core xserver-xorg-dev xdmx xdmx-tools xnest xvfb xserver-xephy

[Ubuntu-x-swat] [Bug 496363] Re: Installing nvidia kills xorg on non-nvidia systems

Right. Please note that maverick doesn't exist yet in Launchpad, so we can't target to maverick yet. -- Installing nvidia kills xorg on non-nvidia systems https://bugs.launchpad.net/bugs/496363 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-

[Ubuntu-x-swat] [Bug 562418] Re: empty ddebs when dh_strip is called twice

** Summary changed: - many -dbg packages have debug symbols mismatch + empty ddebs when dh_strip is called twice -- empty ddebs when dh_strip is called twice https://bugs.launchpad.net/bugs/562418 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xor

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model

** Also affects: xserver-xorg-input-evdev (Ubuntu Lucid) Importance: High Assignee: Martin Pitt (pitti) Status: Confirmed ** Changed in: xserver-xorg-input-evdev (Ubuntu Lucid) Status: Confirmed => In Progress -- keyboard input broken due to invalid "SKIP" k

[Ubuntu-x-swat] [Bug 562418] Re: empty ddebs when dh_strip is called twice

> Confirmed → Invalid Well, the current ddebs are still broken, so my gut feeling would be to leave it open until p-c-d goes to lucid-updates and xorg-server gets rebuilt. It's of some value to have working debug symbols for an LTS, I guess. -- empty ddebs when dh_strip is called twice https://b

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model

I can't seem to be able to reproduce the actual keyboard breakage any more with XKBLAYOUT="SKIP". Perhaps something in Lucid changed to make X/GNOME/etc. more robust against invalid models. But anyway, let's fix it properly. I confirmed that if XBKMODEL is not specified at all, X.org assumes "evde

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model

For those of you who can still reproduce this by switching /etc/default /console-setup back to "SKIP", can you please try to install my proposed fix in my SRU test PPA? sudo add-apt-repository ppa:pitti/sru-test sudo apt-get update sudo apt-get upgrade (packages should be built in about 30

Re: [Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model

Hello dlotton, dlotton [2010-04-27 20:57 -]: > I set XKBMODEL="SKIP" in '/etc/default/console-setup' and restarted. > > This does not cause the keyboard problem to return at login for me. Is that with the lucid packages or my PPA? Thanks, Martin -- keyboard input broken due to invalid "

Re: [Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model

gets messy. For now I suggest that everyone who is affected fixes /etc/default/console-setup to replace the broken XKBVARIANT="U.S. English" with XKBVARIANT="". Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian D

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid keyboard varient set by VMWare installer

** Summary changed: - keyboard input broken due to invalid "SKIP" keyboard model + keyboard input broken due to invalid keyboard varient set by VMWare installer ** Changed in: xorg-server (Ubuntu Lucid) Importance: High => Low ** Changed in: xorg-server (Ubuntu Lucid) Milestone: lucid-upd

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer

Ah, I just noticed that "U.S. English" is in fact the default value of console-setup's console-setup/layout debconf question, so it does make sense to special-case this as well. ** Changed in: xorg-server (Ubuntu Lucid) Importance: Low => Medium ** Changed in: xorg-server (Ubuntu Lucid) Mi

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer

I. e. due to some strange interaction with the VMWare installer, the value from console-setup/layout ended up in /variant.. -- keyboard input broken due to invalid keyboard variant set by VMWare installer https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer

I now uploaded version 2:1.7.6-2ubuntu7pitti2 to my PPA, which ignores the "U.S. English" breakage as well. Testing appreciated! The i386 build will be available in some 30 minutes, the amd64 variant will unfortunately take another two hours, due to PPA builders being clogged. ** Changed in: xorg

[Ubuntu-x-swat] [Bug 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer

debdiff, for SRU review and git committing ** Description changed: - Summary: /etc/default/console-setup has an invalid XKBMODEL="SKIP" + Summary: /etc/default/console-setup has an invalid XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" Workaround for affected machines: sudo dpkg-reconfigure c

[Ubuntu-x-swat] [Bug 491210] Re: [i865G] Monitor Resolution limited to 800x600

** Changed in: xserver-xorg-video-intel (Ubuntu Lucid) Assignee: (unassigned) => Bryce Harrington (bryceharrington) -- [i865G] Monitor Resolution limited to 800x600 https://bugs.launchpad.net/bugs/491210 You received this bug notification because you are a member of Ubuntu-X, which is subscr

[Ubuntu-x-swat] [Bug 283765] Re: package xorg-driver-fglrx 2:8.543-0ubuntu1 failed to install/upgrade: EOF on stdin at conffile prompt

** Changed in: jockey (Ubuntu) Status: Fix Committed => Fix Released -- package xorg-driver-fglrx 2:8.543-0ubuntu1 failed to install/upgrade: EOF on stdin at conffile prompt https://bugs.launchpad.net/bugs/283765 You received this bug notification because you are a member of Ubuntu-X, whi

[Ubuntu-x-swat] [Bug 517430] Re: [MIR] xserver-xorg-video-nouveau

The package description is still pretty scary, I added a work item to the spec to improve it. This is an approved lucid goal, and the desktop team will maintain it. Approved. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Fix Committed -- [MIR] xserver-xorg-video-nouve

[Ubuntu-x-swat] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM

Christian, indeed quirks handling was broken in pm-utils until last week. Do you have 1.3.0~rc3-1? Can you please try again with that one? If it does not work still, please do sudo rm /var/log/pm-suspend.log sudo PM_DEBUG=true pm-suspend then resume (or reboot if it's broken) and attach /va

[Ubuntu-x-swat] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM

Christian, it seems that at least the quirks handling seems to work. You are using the proprietary nvidia driver, which does not need any quirks (and thus pm-utils disables them, just like hal did). Also, at least the original reporter's problem (http://launchpadlibrarian.net/38123737/Desktop%20aft

[Ubuntu-x-swat] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM

I believe the pm-utils side here is fixed, but there's still a problem with the graphics driver, of course (keeping those tasks open) ** Changed in: pm-utils (Ubuntu) Status: Confirmed => Fix Released -- [lucid regression] random graphics effects after resume from suspend to RAM https://b

[Ubuntu-x-swat] [Bug 515498] Re: lucid lynx xorg resume from suspend colored blocks nonresponsive

*** This bug is a duplicate of bug 488720 *** https://bugs.launchpad.net/bugs/488720 ** This bug is no longer a duplicate of bug 510004 [lucid regression] random graphics effects after resume from suspend to RAM ** This bug has been marked a duplicate of bug 488720 Suspend/resume with nv

[Ubuntu-x-swat] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM

*** This bug is a duplicate of bug 488720 *** https://bugs.launchpad.net/bugs/488720 ** This bug has been marked a duplicate of bug 488720 Suspend/resume with nvidia driver fails -- [lucid regression] random graphics effects after resume from suspend to RAM https://bugs.launchpad.net/bugs

[Ubuntu-x-swat] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM

Sorry, unduplicating again then. ** This bug is no longer a duplicate of bug 488720 Suspend/resume with nvidia driver fails -- [lucid regression] random graphics effects after resume from suspend to RAM https://bugs.launchpad.net/bugs/510004 You received this bug notification because you are

[Ubuntu-x-swat] [Bug 258038] Re: Look into feasibility of using an alternatives system rather than diversions

** Also affects: fglrx-installer (Ubuntu Lucid) Importance: Wishlist Assignee: Alberto Milone (albertomilone) Status: Fix Committed ** Also affects: mesa (Ubuntu Lucid) Importance: Wishlist Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Also affects

[Ubuntu-x-swat] [Bug 494699] Re: Does not support current Lucid kernel (2.6.32)

** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- Does not support current Lucid kernel (2.6.32) https://bugs.launchpad.net/bugs/494699 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-inst

[Ubuntu-x-swat] [Bug 517430] Re: [MIR] xserver-xorg-video-nouveau

Promoted ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Assignee: Bryce Harrington (bryceharrington) => (unassigned) -- [MIR] xserver-xorg-video-nouveau https://bugs.launchpad.net/bugs/51743

[Ubuntu-x-swat] [Bug 522061] Re: Nvidia proprietary drivers fallback test failed

** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => Alberto Milone (albertomilone) -- Nvidia proprietary drivers fallback test failed https://bugs.launchpad.net/bugs/522061 You received this bug notification because you are a memb

[Ubuntu-x-swat] [Bug 522969] Re: Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to menu after installing nvidia driver until you re-login

I just checked the package, and the reason is that the nvidia driver does not actually ship the .desktop file in /usr/share/applications/, but in a different dir, and I suppose the postinst creates a link dynamically. This does not trigger a rebuild of the menu cache. What we can do here is: nvidi

[Ubuntu-x-swat] [Bug 522969] Re: Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to menu after installing nvidia driver until you re-login

** Changed in: gnome-menus (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: nvidia-graphics-drivers (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to menu after instal

[Ubuntu-x-swat] [Bug 528908] Re: Failsafe X troubleshooting dialogs do not load translations

I think upstart jobs don't have a particular environment, you need to source it yourself. I believe you need to add something like if [ -r /etc/default/locale ]; then . /etc/default/locale export LANG LANGUAGE elif [ -r /etc/environment ]; then . /etc/environment

[Ubuntu-x-swat] [Bug 530675] Re: 75dbus_dbus-launch: 13: has_option: not found

anged in: xorg (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- 75dbus_dbus-launch: 13: has_option: not found https://bugs.launchpad.net/bugs/530675 You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 531054] Re: [Lucid Video]Nvidia-current hardware drivers do not install Nvidia GUI config tool in menus

*** This bug is a duplicate of bug 522969 *** https://bugs.launchpad.net/bugs/522969 ** This bug has been marked a duplicate of bug 522969 doesn't add nvidia-xconfig to menu after installing -- [Lucid Video]Nvidia-current hardware drivers do not install Nvidia GUI config tool in menus ht

[Ubuntu-x-swat] [Bug 522969] Re: Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to menu after installing nvidia driver until you re-login

As I pointed out in comment 4, nvidia-graphics-drivers _also_ needs to be fixed to trigger gnome-menus in its postinst. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Fix Released => Triaged ** Summary changed: - Jockey doesn't add nvidia-xconfig (Nvidia X Server Settings) to men

Re: [Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

n/vmmouse_detect", ENV{x11_driver}="vmmouse" If anyone could send me udevadm info --attribute-walk --name=/dev/input/eventXX from the vmmouse device, I can help with making that rule a little tighter to avoid running vmmouse_detect for obvious non-vmmouse devices. Mart

[Ubuntu-x-swat] [Bug 402260] Re: [Needs SRU] segfault when running Xdmx

Accepted xorg-server into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: xorg-server (Ubuntu

[Ubuntu-x-swat] [Bug 518045] Re: Prompting due to modified Xedit conffile that was not modified by the user

Bryce, are you on this bug? If you have too much on your plate, please reassign to me or raof. ** Changed in: x11-apps (Ubuntu Lucid) Assignee: (unassigned) => Bryce Harrington (bryceharrington) -- Prompting due to modified Xedit conffile that was not modified by the user https://bugs.laun

[Ubuntu-x-swat] [Bug 506656] Re: Xorg crashed with SIGSEGV in FatalError()

Alberto indicated that there will be a new release of the ATI driver RSN which works with lucid. ** Changed in: fglrx-installer (Ubuntu Lucid) Status: Confirmed => In Progress ** Changed in: fglrx-installer (Ubuntu Lucid) Assignee: (unassigned) => Alberto Milone (albertomilone) -- X

[Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

Oh, LP caused a line break. The entire udev rule (starting after "sudo tee" and until "EOF") is one line. -- needs an udev rule https://bugs.launchpad.net/bugs/430532 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-vmmouse in ubun

[Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

Can someone please try this? sudo tee /etc/udev/rules.d/69_xorg_vmmouse.rules

[Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

I tried the rule myself in KVM with /bin/true as PROGRAM (I don't have Marc's fix yet), and with fixing to ACTION=="add|change", and it works well. ** Changed in: xserver-xorg-input-vmmouse (Ubuntu) Assignee: Alberto Milone (albertomilone) => Martin Pitt (pitti) ** C

[Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

** Bug watch added: freedesktop.org Bugzilla #26910 https://bugs.freedesktop.org/show_bug.cgi?id=26910 ** Also affects: evdev via https://bugs.freedesktop.org/show_bug.cgi?id=26910 Importance: Unknown Status: Unknown -- needs an udev rule https://bugs.launchpad.net/bugs/430532 Yo

[Ubuntu-x-swat] [Bug 430532] Re: needs an udev rule

** Bug watch added: Debian Bug tracker #572692 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572692 ** Also affects: xserver-xorg-input-vmmouse (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572692 Importance: Unknown Status: Unknown -- needs an udev rule https:

[Ubuntu-x-swat] [Bug 228399] Re: Closing lid results in kernel panic visible on VT-1

** Tags added: verification-done ** Tags removed: verification-needed -- Closing lid results in kernel panic visible on VT-1 https://bugs.launchpad.net/bugs/228399 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xf86-video-intel. _

[Ubuntu-x-swat] [Bug 314928] Re: [i915GM] MTRR entry gets removed when restarting xorg - causes corruption on ttys

Can anyone please test the update in jaunty-proposed and give feedback here? -- [i915GM] MTRR entry gets removed when restarting xorg - causes corruption on ttys https://bugs.launchpad.net/bugs/314928 You received this bug notification because you are a member of Ubuntu-X, which is the registran

[Ubuntu-x-swat] [Bug 314928] Re: [i915GM] MTRR entry gets removed when restarting xorg - causes corruption on ttys

Well, nothing is simple when it comes to video drivers, I'm afraid :-(, and you just said yourself that the patch doesn't work.,,, Anyway, thanks for testing. Since the current patch doesn't work, I removed the current package from jaunty-proposed. ** Changed in: xserver-xorg-video-intel (Ubuntu

[Ubuntu-x-swat] [Bug 223212] Re: Non-free files distributed without license/copyright info

ogress ** Changed in: jockey (Ubuntu Karmic) Milestone: None => ubuntu-9.10-beta ** Changed in: jockey (Ubuntu Karmic) Assignee: (unassigned) => Martin Pitt (pitti) -- Non-free files distributed without license/copyright info https://bugs.launchpad.net/bugs/223212 You received this bug

[Ubuntu-x-swat] [Bug 385658] Re: 'nv' is selected when no xorg.conf is present even if it doesn't support the nvidia hardware

Assigning to Alberto for now, who covers for Bryce. Timo, Mario, please feel free to assign to you if you can/want to handle it. Thanks Mario for putting together the patch. This approach seems appropriate to me in the sense that it errs on the side of caution. As for the regression potential, hav

[Ubuntu-x-swat] [Bug 419126] Re: X fails to start up after mesa+git update - gdm loops after logging in

** Tags added: regression-potential ** Tags removed: regression ** Summary changed: - X fails to start up after mesa+git update - gdm loops after logging in + [ATI R6xx] X fails to start up after mesa+git update - gdm loops after logging in ** Also affects: mesa (Ubuntu Karmic) Importance: H

<    1   2   3   4   5   6   7   8   9   10   >