[Ubuntu-x-swat] [Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

> Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5 The -once was an attempt to work around this, but it doesn't help, nor change the behaviour of this bug. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

umockdev's test suite now started to see this crash in current Ubuntu jammy. Simple reproducer: $ cat tests/xorg-dummy.conf Section "Device" Identifier "test" Driver "dummy" EndSection $ Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5 Then, run at least one

[Ubuntu-x-swat] [Bug 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

How can we ensure that this does not break existing 16.04 installs (with or without HWE)? Please add a test plan that covers at least the most widespread hardware (Intel, Nvidia, fglrx, free/proprietary drivers) and an overview of the regression potential based on the changes in the new libdrm

[Ubuntu-x-swat] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

I don't see anythign left to sponsor here, so unsubscribing sponsors now. Please re-subscribe when you upload further patches. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu.

[Ubuntu-x-swat] [Bug 1636397] Re: Fix modesetting slave output names

unity8 tests have always been brittle; the autopilot ones (which use X) succeeded, while the QML ones (which don't use X) didn't, so this appears unrelated. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1636397] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1590553] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1581076] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1613708] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1591356] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1617925] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1617932] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1619142] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1577735] Update Released

The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a

[Ubuntu-x-swat] [Bug 1600124] Re: Adjust KBL PCI-ID's

** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1600124 Title: Adjust KBL PCI-ID's To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 1483276] Re: Unable to launch xdiagnose through the Activities Overview in the normal way

Hello Nikita, or anyone else affected, Accepted xdiagnose into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdiagnose/3.8.4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Ubuntu-x-swat] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

I removed nvidia-graphics-drivers-340 340.96-0ubuntu3.16.04.1 from xenial-proposed. ** Tags removed: verification-failed verification-needed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

[Ubuntu-x-swat] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

** Tags removed: verification-done ** Tags added: verification-done-xenial verification-needed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1577735 Title: Add missing SKL/BXT PCI-ID's To

[Ubuntu-x-swat] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

OK, thanks for the update. Releasing xenial, trusty still needs to be tested. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1577735 Title: Add missing SKL/BXT PCI-ID's To manage

[Ubuntu-x-swat] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

Which Ubuntu version did that apply to? 2.4.67 is in both trusty- and xenial-proposed. Also, if .67 is already on "the image" and does not fix the bug, then this can't be verification of this SRU as this updates *to* .67. Version 2.4.68 is only in yakkety. -- You received this bug notification

[Ubuntu-x-swat] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

@Timo: Please explain what you tested, and for which releases. Don't just flip the tag to v-done (this has bitten us several times in the past already). Thanks! ** Tags removed: verification-done ** Tags added: verification-neededd ** Tags removed: verification-neededd ** Tags added:

[Ubuntu-x-swat] [Bug 1566487] Update Released

The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you

[Ubuntu-x-swat] [Bug 1076414] Proposed package removed from archive

The version of nvidia-settings-experimental-304 in the proposed pocket of Precise that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1076414] Proposed package removed from archive

The version of nvidia-settings-experimental-304 in the proposed pocket of Precise that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1076414] Proposed package removed from archive

The version of nvidia-settings-experimental-310 in the proposed pocket of Precise that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1076414] Proposed package removed from archive

The version of nvidia-settings-experimental-310 in the proposed pocket of Precise that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1566487] Re: Container apps should use same keyboard layout as Unity 8

Please test the -proposed package, it blocks the next SRU that is waiting in the queue. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1566487 Title: Container apps should use

[Ubuntu-x-swat] [Bug 1566487] Re: Container apps should use same keyboard layout as Unity 8

Hello Christopher, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.3-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Ubuntu-x-swat] [Bug 1562033] Re: package xinit 1.3.4-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Hello Rachel, or anyone else affected, Accepted xinit into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xinit/1.3.4-3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

Hello Jason, or anyone else affected, Accepted llvm-toolchain-3.8 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-3.8/1:3.8-2ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Ubuntu-x-swat] [Bug 1566975] Re: AssertionError on .proc.driver.nvidia.gpus.0000:01:00.0

Whoops, this is in apport after all -- xdiagnose's hook calls apport.hookutils.attach_file_if_exists(). ** Changed in: xdiagnose (Ubuntu) Status: Triaged => In Progress ** Changed in: xdiagnose (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Package changed: xdi

[Ubuntu-x-swat] [Bug 1566878] Re: Alt-backtick regression

Since yesterday's dist-upgrade I'm getting [ 4305.170] (EE) Error compiling keymap (server-A24141C1DFD907420EB8836C380C7C1C62283A5E) [ 4305.170] (EE) XKB: Couldn't compile keymap errors in Xorg.0.log. Also, in qemu guests the keys are now totally garbled, particularly the cursor keys, Home,

[Ubuntu-x-swat] [Bug 1566975] Re: AssertionError on .proc.driver.nvidia.gpus.0000:01:00.0

This needs to be fixed in xdiagnose's apport hook - ':' is an invalid character in key names. ** Project changed: apport => xdiagnose (Ubuntu) ** Changed in: xdiagnose (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1558820] Re: [MIR] libva

I promoted the two. ** Changed in: libset-scalar-perl (Ubuntu) Status: Incomplete => Fix Released ** Changed in: libva (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libset-scalar-perl in

[Ubuntu-x-swat] [Bug 1541369] Re: remove stale xorg drivers from the archive

Removed the lot. ** Changed in: xf86-input-multitouch (Ubuntu) Status: New => Fix Released ** Changed in: xserver-xorg-input-aiptek (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-aiptek (Ubuntu) Status: Incomplete => Fix Released ** Changed in:

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

For the record, the archive grep finished now, so the above tasks are complete. ** Changed in: console-setup (Ubuntu) Importance: Low => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu.

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

** Changed in: dcbd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart-only option

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

** Also affects: dcbd (Ubuntu) Importance: Undecided Status: New ** Changed in: dcbd (Ubuntu) Importance: Undecided => High ** Changed in: dcbd (Ubuntu) Status: New => In Progress ** Changed in: dcbd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti)

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: rfkill (Ubuntu) Importance: Undecided Status: New ** Also affects: xdiagnose (Ubuntu) Importance: Undecided

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

** Changed in: rfkill (Ubuntu) Status: New => Fix Committed ** Changed in: rfkill (Ubuntu) Importance: Undecided => Low ** Changed in: xdiagnose (Ubuntu) Importance: Undecided => Low ** Changed in: lxc (Ubuntu) Importance: Undecided => Low -- You received this bug notification

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

lxc has DEB_DH_INSTALLINIT_ARGS = --upstart-only which is a double no-op, as DEB_DH_INSTALLINIT_ARGS is only used by cdbs and lxc does not use that. ** Changed in: lxc (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu-X, which

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

** Also affects: nis (Ubuntu) Importance: Undecided Status: New ** Changed in: nis (Ubuntu) Status: New => Triaged ** Changed in: nis (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option

Progress ** Changed in: debhelper (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart

[Ubuntu-x-swat] [Bug 1512274] Re: Sync libvdpau 1.1.1-3 (main) from Debian sid (main)

This bug was fixed in the package libvdpau - 1.1.1-3 Sponsored for Oibaf (oibaf) --- libvdpau (1.1.1-3) unstable; urgency=medium [ Luca Boccassi ] * Cherry-pick patch for DRI_PRIME crash. (Closes: #802625) * Upload to unstable. -- Andreas Beckmann Thu, 29

[Ubuntu-x-swat] [Bug 1473800] Re: restarting logind during systemd update causes screen to lock

** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed ** No longer affects: xorg-server (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu-X, which is subs

[Ubuntu-x-swat] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

** Changed in: libx11 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when

[Ubuntu-x-swat] [Bug 1473800] Re: restarting logind during systemd update causes screen to lock

This sounds related: http://cgit.freedesktop.org/xorg/xserver/commit/?id=dc48bd653c7e1013e2d69e3f59ae3cbc0c893473 -- Seems current X.org does not like logind to be restarted, but that's what we do right now in the systemd package (so that after a dist- upgrade you actually run the current

[Ubuntu-x-swat] [Bug 1483695] [NEW] fails to build module in wily-proposed: gcc-4.9: Command not found

Public bug reported: As shown by the test regression of http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers- common/wily/amd64/ , fglrx and fglrx-updates fail to build the module in wily-proposed: Setting up fglrx-core (2:15.200.1-0ubuntu2) ... update-alternatives: using

[Ubuntu-x-swat] [Bug 1483695] Re: fails to build module in wily-proposed: gcc-4.9: Command not found

This comes from /lib/modules/fglrx/build_mod/make.sh parsing the kernel compiler from /proc/version, in set_GCC_version(). ** Changed in: fglrx-installer-updates (Ubuntu Wily) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1483695] Re: fails to build module in wily-proposed: gcc-4.9: Command not found

This comes from /lib/modules/fglrx/build_mod/make.sh parsing the kernel compiler from /proc/version, in set_GCC_version(). ** Package changed: fglrx (Ubuntu Wily) = fglrx-installer (Ubuntu Wily) ** Changed in: fglrx-installer (Ubuntu Wily) Status: New = Triaged -- You received this bug

[Ubuntu-x-swat] [Bug 1443345] Re: [Dell Insprion 3646] Double cursor appeared when rotating the display back to normal [8086:0f31]

Hello Po-Hsu, or anyone else affected, Accepted xserver-xorg-video-intel into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /xserver-xorg-video-intel/2:2.99.914-1~exp1ubuntu4.5 in a few hours, and then in the -proposed repository. Please

[Ubuntu-x-swat] [Bug 1378188] Re: [GNOME3 Staging PPA] strange shadow rendered where client-side decorations are used

Hello Erich, or anyone else affected, Accepted xserver-xorg-video-intel-lts-utopic into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel-lts- utopic/2:2.99.914-1~exp1ubuntu4.5~trusty1 in a few hours, and then in the

[Ubuntu-x-swat] [Bug 1432194] Re: Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics 5500

Hello seth, or anyone else affected, Accepted into utopic-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use

[Ubuntu-x-swat] [Bug 1443345] Please test proposed package

Hello Po-Hsu, or anyone else affected, Accepted xserver-xorg-video-intel-lts-utopic into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel-lts- utopic/2:2.99.914-1~exp1ubuntu4.5~trusty1 in a few hours, and then in the

[Ubuntu-x-swat] [Bug 1432194] Please test proposed package

Hello seth, or anyone else affected, Accepted xserver-xorg-video-intel-lts-utopic into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel-lts- utopic/2:2.99.914-1~exp1ubuntu4.5~trusty1 in a few hours, and then in the

[Ubuntu-x-swat] [Bug 1447143] Re: [SKL, i915_bpo] Rotation doesn't work

Hello Timo, or anyone else affected, Accepted into utopic-proposed. The package will build now and be available in a few hours in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use

[Ubuntu-x-swat] [Bug 1436952] Re: X crashes on some runs of Kubuntu live image returning in SDDM login

Is that still true on current vivid daily images? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1436952 Title: X crashes on some runs of Kubuntu live image returning in SDDM login To manage

[Ubuntu-x-swat] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

** No longer affects: lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1441883 Title: 15.04 Vivid Vervet won't boot after uninstalling lightdm To manage notifications about

[Ubuntu-x-swat] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

Didier kindly offered to work on the xdiagnose part. It's not yet clear whether we also need to change lightdm. ** Changed in: xdiagnose (Ubuntu) Assignee: (unassigned) = Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

This is due to xdiagnose's Requires=display-manager.service OnFailure=failsafe-graphical.target ** Also affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Changed in: xdiagnose (Ubuntu) Status: New = Triaged ** Tags added: systemd-boot -- You received this bug

[Ubuntu-x-swat] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

** Changed in: xdiagnose (Ubuntu) Status: Triaged = Fix Committed ** Changed in: lightdm (Ubuntu) Importance: Medium = Low -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1441883

[Ubuntu-x-swat] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

For the record, systemd actually checks for docked/undocked events, so in a VT you should not actually get this behaviour. Only under Unity, because unity-settings-daemon doesn't seem to check for dock events in particular but just checks the connected monitors. Can you confirm this? ** Package

[Ubuntu-x-swat] [Bug 1439191] [NEW] [vivid regression] X.org fails to start on i386 cirrus

Public bug reported: This was spotted by systemd's tests (which involve lightdm) starting to fail. Cirrus cards (as provided by QEMU) still worked fine until at least 2015-03-11 (https://jenkins.qa.ubuntu.com/job/vivid-adt- systemd/119/), but started to fail now. Start a current i386 vivid image

[Ubuntu-x-swat] [Bug 1415958] Re: Laptop + external display does not suspend on lid close

This might actually be on purpose? $ systemd-inhibit [...] Who: martin (UID 1000/martin, PID 2278/unity-settings-) What: handle-lid-switch Why: Multiple displays attached Mode: block I for one really welcome this. Finally my laptop stopped suspending when it's sitting in the

[Ubuntu-x-swat] [Bug 1438306] Re: External monitors receive no signal over DisplayPort

It's worth testing this with earlier kernels; do you have one where this was known to work still? You shold still have some older kernels in the grub boot menu, under Advanced options. ** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu) -- You received this bug notification because you are

[Ubuntu-x-swat] [Bug 1438306] Re: External monitors receive no signal over DisplayPort

Oh wait -- you are saying that the external monitor does not receive a signal at any point in time? I thought the external monitor would stop working *during/after* running dist-upgrade, and start working again after a reboot. That sounds like a kernel/video driver/X.org regression then,

[Ubuntu-x-swat] [Bug 1421205] Re: Keyboard Volume up/down keys not work with pc105

Reassigning to X.org's evdev driver then. If evtest gets the correct events, then kernel, keymaps, and evdev are alright, but it seems the press events somehow get lost in X.org's input driver. ** Package changed: systemd (Ubuntu) = xserver-xorg-input-evdev (Ubuntu) -- You received this bug

[Ubuntu-x-swat] [Bug 1427924] Re: autopkgtest failures if nvidia dkms module fails to build

That's pretty much exactly what the u-d-common tests are supposed to detect -- the new kernel broke the -304 nvidia driver. I talked about that to Alberto last week, but good to have a bug now. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New = Won't Fix ** Changed in:

[Ubuntu-x-swat] [Bug 1427924] Re: autopkgtest failures if nvidia dkms module fails to build

Right. For the record, the plan is to enable reverse test dependencies, so that u-d-common can test-depend on the kernel and will be triggered on new kernel uploads (https://bugs.debian.org/779559) ** Bug watch added: Debian Bug tracker #779559

[Ubuntu-x-swat] [Bug 1418262] Re: apport hook to detect wayland sessions

Of course the hook needs to do some runtime detection (like checking the equivalent of $DISPLAY) before it sets the tag. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to weston in Ubuntu. https://bugs.launchpad.net/bugs/1418262 Title: apport

[Ubuntu-x-swat] [Bug 1418262] Re: apport hook to detect wayland sessions

I propose that weston (or another typical wayland package) ships something like /usr/share/apport/general-hooks/weston.py (or wayland- session.py perhaps) which does the appropriate detection, and does report.setdefault('Tags', '') report['Tags'] += ' wayland-session'

[Ubuntu-x-swat] [Bug 1418262] Re: apport hook to detect wayland sessions

So I was told that weston isn't actually installed; the wayland libs are in sync with Debian, so we can also put it into apport. But I want to point out that I cannot maintain that hook -- if the logic changes, I depend on external contributors to update it for me. ** Package changed: weston

[Ubuntu-x-swat] [Bug 1414930] Re: Buttons of Synaptics trackpad doesn't work

systemd 219 is planned in about two weeks which will contain this. ** Changed in: systemd (Ubuntu) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu) Status: New = Fix Committed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You

[Ubuntu-x-swat] [Bug 1302270] Re: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied

Jamie, Daniel, did you ever get this after the fix in bug 1302264? This is the typical symptom of logind not working, so if you have that situation can you please check for a logind crash /var/crash? ** Changed in: compiz Status: Confirmed = Invalid ** Changed in: unity Status:

[Ubuntu-x-swat] [Bug 1400682] Re: Add xdiagnose fallback when display-manager fails to start

Done in https://launchpad.net/ubuntu/+source/xdiagnose/3.7.1 Thanks Didier! ** Package changed: systemd (Ubuntu) = xdiagnose (Ubuntu) ** Changed in: xdiagnose (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed

[Ubuntu-x-swat] [Bug 1374929] Re: Rebooting after installation of Nvidia , system doesn't go directly X-window mode

That systemd error message is unrelated, mostly cosmetic, and fairly harmless. reassigning back ** Package changed: systemd (Ubuntu) = xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu.

[Ubuntu-x-swat] [Bug 1360241] Re: [Regression] LLVM ERROR: Do not know how to split the result of this operator! in executing Ubuntu UI Toolkit tests on x86

Similar to https://launchpadlibrarian.net/182954654/buildlog_ubuntu- utopic-i386.messaging- app_0.1%2B14.10.20140822-0ubuntu1_FAILEDTOBUILD.txt.gz ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu.

[Ubuntu-x-swat] [Bug 408903]

Ah, thanks for the heads-up! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 408903]

Current kernels have KEY_MICMUTE==248, i. e. X.org should be perfectly able to recognize this. Apparently this was done in 2011 already. Can we update xkeyboard-config to also recognize KEY_MICMUTE in addition to F20, so that it works with both kinds of udev/kernel keymaps for a while? After that

[Ubuntu-x-swat] [Bug 1298668] Re: Spanish numpad unusable on most applications

Can you please be a little more specific how the keys misbehave? I. e. which keys did you press, what did you expect to happen, what happened instead? This isn't clear (at least to me, I'm not an X.org specialist) from the xmodmap lines. Thanks! ** Package changed: systemd (Ubuntu) =

[Ubuntu-x-swat] [Bug 1280155] Re: test for /usr/bin/xrandr when upgrading from lts

http://bazaar.launchpad.net/~auto-upgrade-testing-dev/auto-upgrade- testing/trunk/revision/96 ** Changed in: auto-upgrade-testing Status: New = Fix Released ** Changed in: xorg-lts-transitional (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1280155] Re: test for /usr/bin/xrandr when upgrading from lts

** Changed in: auto-upgrade-testing Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1280155 Title: test for /usr/bin/xrandr when

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

Works nice now with ~ppa8, thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278737 Title: Upgrade to trusty fails from precise backported enablement stacks To manage notifications about

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

With https://launchpad.net/~canonical-x/+archive/x-staging it looks much better, but there are still some problems: Investigating (0) xserver-xorg-glamoregl-lts-saucy [ amd64 ] 0.5.1-0ubuntu4.2~precise2 - 3:1~ppa2 ( oldlibs ) Broken xserver-xorg-glamoregl-lts-saucy:amd64 Depends on

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

Tests with 3:1~ppa5, the previous two problems are now gone. This new one appeared now, presumably due to some multi-arch confusion? I tested lts-{quantal,raring,saucy} → trusty, same error on all of them: The following packages have been kept back: xserver-xorg-video-geode-lts-quantal:i386

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

Above tests were on amd64. On i386 the upgrade now works flawlessly with 3:1~ppa5. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278737 Title: Upgrade to trusty fails from precise

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

** Attachment added: apt-get dist-upgrade output with debug for ppa5 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278737/+attachment/3977306/+files/debug.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu.

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

That's the full log for lts-raring → trusty i386 dist-upgrade with the PPA enabled. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278737 Title: Upgrade to trusty fails from precise backported

[Ubuntu-x-swat] [Bug 1278737] Re: Upgrade to trusty fails from precise backported enablement stacks

Tested with 3:1~ppa7 now. On apt-get update you now get several dozen warnings: W: Unknown Multi-Arch type 'no' for package 'libdrm-dev-lts-quantal' W: Unknown Multi-Arch type 'no' for package 'xserver-common-lts-quantal' You probably meant Multiarch: same? Other than that these have exactly

[Ubuntu-x-swat] [Bug 1278737] [NEW] Upgrade to trusty fails from precise backported enablement stacks

Public bug reported: If you upgrade from Ubuntu 12.04.x LTS to trusty, the upgrade fails because of the various *-lts-{quantal,raring,saucy,trusty} packages. There is currently no upgrade path, so you get in e. g. https://jenkins.qa.ubuntu.com/view/Trusty/view/All/job/upgrade-ubuntu-

[Ubuntu-x-swat] [Bug 1266023] Re: Merge with Debian

This was already uploaded: https://launchpad.net/ubuntu/+source/libxcb/1.10-2ubuntu1. This requires some transitioning (see http://people.canonical.com/~ubuntu-archive /proposed-migration/update_output.txt), unsubscribing sponsors as there is nothing further to do for them at the moment. Please

[Ubuntu-x-swat] [Bug 1247502] Re: Merge libxvmc 2:1.0.8-1 (main) from Debian unstable (main)

Uploaded, thanks! ** Changed in: libxvmc (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxvmc in Ubuntu. https://bugs.launchpad.net/bugs/1247502 Title: Merge libxvmc 2:1.0.8-1 (main) from

[Ubuntu-x-swat] [Bug 1187969] Re: 13.04: Reverting from fglrx in Additional Drivers results in unknown bad state

** Package changed: ubuntu-drivers-common (Ubuntu) = fglrx-installer (Ubuntu) ** Summary changed: - 13.04: Reverting from fglrx in Additional Drivers results in unknown bad state + uninstalling fglrx results in unknown bad state -- You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 1067104] Re: Additional drivers not showing

As gorgekara found out in the previous comment, the problem was that at that time there was no fglrx driver available for current X.org. In current Ubuntu releases it works again, so closing this. ** Package changed: ubuntu-drivers-common (Ubuntu) = fglrx-installer (Ubuntu) ** Changed in:

[Ubuntu-x-swat] [Bug 763331] Re: There should be easy way to install VA-API helper packages

** No longer affects: jockey -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/763331 Title: There should be easy way to install VA-API helper packages To manage notifications about

[Ubuntu-x-swat] [Bug 1068584] Re: Ubable to install proprietary Nvidia drivers with software-properties-gtk in Quantal (upgraded from Precise)

** Package changed: ubuntu-drivers-common (Ubuntu) = nvidia-graphics- drivers-304 (Ubuntu) ** Package changed: nvidia-graphics-drivers-304 (Ubuntu) = nvidia- graphics-drivers-310 (Ubuntu) ** Summary changed: - Ubable to install proprietary Nvidia drivers with software-properties-gtk in Quantal

[Ubuntu-x-swat] [Bug 1188123] [NEW] Xorg crashed with SIGABRT in OsAbort()

Public bug reported: Reproducer: - create a fresh test user - login as that user (Unity session) - Open all things from the launcher - Open the dash (I used the windows key) - type london, remove and add a few characters and wait a bit - session crashes ProblemType: Crash DistroRelease: Ubuntu

[Ubuntu-x-swat] [Bug 859101] Re: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete)

Copying info from my duplicate bug. This is perfectly reproducible everywhere, so this is triaged. As detected by ubuntu-driver-common's autopkgtest [1], current fglrx fails to build on saucy. -- 8 - $ cat /var/lib/dkms/fglrx/9.010/build/make.logDKMS make.log for

[Ubuntu-x-swat] [Bug 1185285] Re: [saucy] fglrx fails to build against linux 3.9.0 (missing version.h)

This is not a duplicate. Bug 859101 appeared in oneiric already and is about a completely different issue in the fglrx sources. ** This bug is no longer a duplicate of bug 859101 fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete) **

[Ubuntu-x-swat] [Bug 859101] Re: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete)

Actually not, I'm sorry. Daniel mis-duplicated my report. ** Changed in: fglrx-installer (Ubuntu) Status: Triaged = Confirmed ** Changed in: fglrx-installer-updates (Ubuntu) Status: Triaged = Confirmed -- You received this bug notification because you are a member of Ubuntu-X,

  1   2   3   4   5   6   7   8   9   >