[Ubuntu-x-swat] [Bug 1246820] Re: fglrx-updates 2:13.101-0ubuntu3: fglrx-updates kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected]
Possible fix here: http://forums.opensuse.org/showthread.php/493913-ATI-Proprietary-driver-13-12-installation-fails-in-openSUSE-13-1 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1246820 Title: fglrx-updates 2:13.101-0ubuntu3: fglrx-updates kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1246820/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
Unfortunately, the workaround prescribed, adding hardening-wrapper as a build dependency doesn't always work, and it's not clear why it does work occasionally. First, in order for hardened-cc to do anything at all, DEB_BUILD_HARDENING needs to be set, and second, if it detects '-static' or other position independent executable incompatible arguments, it only prevents itself from adding -pie; it does not filter it out from the command line if it's already there. In these cases, -pie is already present, having been added via DEB_BUILD_MAINT_OPTIONS or some other way in the debian/rules file. The most proper way that I can see to address this would be to rely on the default dpkg-buildflags to get the basic level of protections. Then to get all the protections, build depend on hardening-wrapper and export DEB_BUILD_HARDENING=1 in debian/rules. I've attached a debdiff that I've verified builds on all available architectures for ureadahead, since that package is also hitting this issue. The least invasive workaround would be to export MALLOC_CHECK=2 at build time (i.e. in debian/rules), as this causes glibc to abort without attempting to produce a backtrace when it detects internal malloc corruption. This unfortunately still leaves configure believing that 'gcc -static' doesn't work, but it at least causes builds not to hang. ** Patch added: ureadahead_0.100.0-17.debdiff https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1266492/+attachment/3961491/+files/ureadahead_0.100.0-17.debdiff -- 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/1266492 Title: ld:i386 crashes with -static -fPIE -pie To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1266492/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273997] Re: error: microcode not responding
*** This bug is a duplicate of bug 1272720 *** https://bugs.launchpad.net/bugs/1272720 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1272720, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1273997/+attachment/3961493/+files/CoreDump.gz ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1273997/+attachment/3961495/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1273997/+attachment/3961496/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1272720 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1273997 Title: error: microcode not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1273997/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1271483] Re: No display with radeon driver for Display Port on [AMD Radeon HD 8490][1002:6771]
** Changed in: xserver-xorg-video-ati-lts-raring (Ubuntu) Assignee: Anthony Wong (anthonywong) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1271483 Title: No display with radeon driver for Display Port on [AMD Radeon HD 8490][1002:6771] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati-lts-raring/+bug/1271483/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1243621] Re: AMD Radeon 6480G[1002:9648] No display after resume from suspend with radeon driver
** Changed in: xserver-xorg-video-ati-lts-raring (Ubuntu) Assignee: Anthony Wong (anthonywong) = (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati-lts-raring in Ubuntu. https://bugs.launchpad.net/bugs/1243621 Title: AMD Radeon 6480G[1002:9648] No display after resume from suspend with radeon driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati-lts-raring/+bug/1243621/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
Here's a similar debdiff for e-d-s, confirmed to build on i386. ** Patch added: evolution-data-server_3.10.3-0ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1266492/+attachment/3961568/+files/evolution-data-server_3.10.3-0ubuntu2.debdiff -- 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/1266492 Title: ld:i386 crashes with -static -fPIE -pie To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1266492/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1270985] Re: Xorg crashed with SIGABRT in DamageRegister()
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1270985 Title: Xorg crashed with SIGABRT in DamageRegister() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1270985/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1268215] Re: No screen after upgrade to Trusty
Does it work now with xxv-ati 7.3.0? ** Changed in: xorg-server (Ubuntu) Status: New = Incomplete -- 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/1268215 Title: No screen after upgrade to Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1268215/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1272720] Re: sometimes boot fails
** Information type changed from Private to Public ** Also affects: libpciaccess (Ubuntu) Importance: Undecided Status: New -- 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/1272720 Title: sometimes boot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/1272720/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273211] Re: Xorg crashed with SIGABRT in memset()
** Information type changed from Private to Public ** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel (Ubuntu) -- 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/1273211 Title: Xorg crashed with SIGABRT in memset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273211/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1269928] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
Can you test with xorg 1.15 from ppa:canonical-x/x-staging ? -- 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/1269928 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1269928/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1269928] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
Please stop recommending people to update their bios, it doesn't fix anything and is a risky procedure. -- 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/1269928 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1269928/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1229591] Re: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade
** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- 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/1229591 Title: 8086:0116 [Dell Inspiron 14z (N411z)] Display brightness keys don't generate evdev events after saucy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1229591/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1247624] Re: Laptop screen is turned off, needs shutdown to work again
** Package changed: xorg (Ubuntu) = xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1247624 Title: Laptop screen is turned off, needs shutdown to work again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1247624/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1268215] Re: No screen after upgrade to Trusty
I'm sorry I don't know what is xxv-ati where can I see that ? ** Changed in: xorg-server (Ubuntu) Status: Incomplete = New -- 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/1268215 Title: No screen after upgrade to Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1268215/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273652] Re: apply of multi-monitor setting results in crash
That is not possble! My system do not recognize the crash an no report is created! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1273652 Title: apply of multi-monitor setting results in crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
The attachment ureadahead_0.100.0-17.debdiff seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1266492 Title: ld:i386 crashes with -static -fPIE -pie To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1266492/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273211] Re: Xorg crashed with SIGABRT in memset()
*** This bug is a duplicate of bug 1271628 *** https://bugs.launchpad.net/bugs/1271628 ** This bug has been marked a duplicate of bug 1271628 Xorg crashed with SIGSEGV in memset() -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1273211 Title: Xorg crashed with SIGABRT in memset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273211/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263681] Re: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging
Tried talking about this on IRC (#intel-gfx on FreeNode). It was suggested to me to capture the kernel log after setting drm.debug to 0x5. That produced quite a lot of log output (70 thousand lines in about a minute), and after some trimming I got something that could perhaps be useful: https://gist.github.com/mgedmin/8686551 This is me unplugging the DisplayPort connector: Jan 29 13:49:59 platonas kernel: [ 2041.110857] [drm:i915_hotplug_work_func], running encoder hotplug functions Jan 29 13:49:59 platonas kernel: [ 2041.110861] [drm:i915_hotplug_work_func], Connector HDMI-A-1 (pin 4) received hotplug event. Jan 29 13:49:59 platonas kernel: [ 2041.110863] [drm:i915_hotplug_work_func], Connector DP-1 (pin 4) received hotplug event. Jan 29 13:49:59 platonas kernel: [ 2041.125448] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter i915 gmbus dpb Jan 29 13:49:59 platonas kernel: [ 2041.125457] [drm:intel_hpd_irq_event], [CONNECTOR:16:HDMI-A-1] status updated from 1 to 2 Jan 29 13:49:59 platonas kernel: [ 2041.125464] [drm:intel_hpd_irq_event], [CONNECTOR:20:DP-1] status updated from 2 to 2 Jan 29 13:49:59 platonas kernel: [ 2041.125466] [drm:drm_sysfs_hotplug_event], generating hotplug event This is me plugging it back in (it wasn't detected by gnome-shell; xrandr --current didn't see it): Jan 29 13:50:05 platonas kernel: [ 2046.777640] [drm:i915_hotplug_work_func], running encoder hotplug functions Jan 29 13:50:05 platonas kernel: [ 2046.777655] [drm:i915_hotplug_work_func], Connector HDMI-A-1 (pin 4) received hotplug event. Jan 29 13:50:05 platonas kernel: [ 2046.777661] [drm:i915_hotplug_work_func], Connector DP-1 (pin 4) received hotplug event. Jan 29 13:50:05 platonas kernel: [ 2046.778046] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter i915 gmbus dpb Jan 29 13:50:05 platonas kernel: [ 2046.778051] [drm:intel_hpd_irq_event], [CONNECTOR:16:HDMI-A-1] status updated from 2 to 2 Jan 29 13:50:05 platonas kernel: [ 2046.780633] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x7143003f Jan 29 13:50:05 platonas kernel: [ 2046.789040] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x7143003f Jan 29 13:50:05 platonas kernel: [ 2046.797004] [drm:intel_dp_aux_ch], dp_aux_ch timeout status 0x7143003f Jan 29 13:50:05 platonas kernel: [ 2046.802468] [drm:intel_hpd_irq_event], [CONNECTOR:20:DP-1] status updated from 2 to 2 Jan 29 13:50:05 platonas kernel: [ 2046.830695] crtc 1 : v 7 p(0,-23)@ 2046.796294 - 2046.796779 [e 2 us, 0 rep] This is me running xrandr to force monitor detection: Jan 29 13:50:13 platonas kernel: [ 2054.453968] [drm:drm_mode_getconnector], [CONNECTOR:7:?] Jan 29 13:50:13 platonas kernel: [ 2054.453976] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] Jan 29 13:50:13 platonas kernel: [ 2054.454000] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:7:LVDS-1] probed modes : Jan 29 13:50:13 platonas kernel: [ 2054.454005] [drm:drm_mode_debug_printmodeline], Modeline 10:1366x768 60 74800 1366 1414 1446 1578 768 770 775 790 0x48 0xa Jan 29 13:50:13 platonas kernel: [ 2054.454022] [drm:drm_mode_getconnector], [CONNECTOR:7:?] Jan 29 13:50:13 platonas kernel: [ 2054.454571] [drm:drm_mode_getconnector], [CONNECTOR:13:?] Jan 29 13:50:13 platonas kernel: [ 2054.454576] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:13:VGA-1] Jan 29 13:50:13 platonas kernel: [ 2054.454583] [drm:intel_ironlake_crt_detect_hotplug], ironlake hotplug adpa=0xf4, result 0 Jan 29 13:50:13 platonas kernel: [ 2054.454588] [drm:intel_crt_detect], CRT not detected via hotplug Jan 29 13:50:13 platonas kernel: [ 2054.454766] [drm:gmbus_xfer], GMBUS [i915 gmbus vga] NAK for addr: 0050 r(1) Jan 29 13:50:13 platonas kernel: [ 2054.454773] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter i915 gmbus vga Jan 29 13:50:13 platonas kernel: [ 2054.454777] [drm:intel_crt_get_edid], CRT GMBUS EDID read failed, retry using GPIO bit-banging Jan 29 13:50:13 platonas kernel: [ 2054.454780] [drm:intel_gmbus_force_bit], enabling bit-banging on i915 gmbus vga. force bit now 1 Jan 29 13:50:13 platonas kernel: [ 2054.455160] [drm:drm_do_probe_ddc_edid], drm: skipping non-existent adapter i915 gmbus vga Jan 29 13:50:13 platonas kernel: [ 2054.455163] [drm:intel_gmbus_force_bit], disabling bit-banging on i915 gmbus vga. force bit now 0 Jan 29 13:50:13 platonas kernel: [ 2054.455167] [drm:intel_crt_detect_ddc], CRT not detected via DDC:0x50 [no valid EDID found] Jan 29 13:50:13 platonas kernel: [ 2054.455171] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:13:VGA-1] disconnected Jan 29 13:50:13 platonas kernel: [ 2054.455186] [drm:drm_mode_getconnector], [CONNECTOR:16:?] Jan 29 13:50:13 platonas kernel: [ 2054.455190] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:16:HDMI-A-1] Jan 29 13:50:13 platonas kernel: [ 2054.533988] [drm:drm_edid_to_eld], ELD: no CEA Extension found Jan 29 13:50:13 platonas kernel:
[Ubuntu-x-swat] [Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1271628 Title: Xorg crashed with SIGSEGV in memset() To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1271628/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1270985] Re: [prime] Xorg crashed with SIGSEGV in DamageRegister()
** Summary changed: - Xorg crashed with SIGABRT in DamageRegister() + [prime] Xorg crashed with SIGSEGV in DamageRegister() -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1270985 Title: [prime] Xorg crashed with SIGSEGV in DamageRegister() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1270985/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1192740] Re: GPU hang when using chrome
*** This bug is a duplicate of bug 1041790 *** https://bugs.launchpad.net/bugs/1041790 ** This bug has been marked a duplicate of bug 1041790 [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1192740 Title: GPU hang when using chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1192740/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263681] Re: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging
Chris Wilson said this on IRC: The issue is that after the hotplug interrupt is sent by the hardware, the monitor is not yet ready to respond to the DDC probes and generates a NAK instead - this leads us to conclude that there is nothing on the other end of the connector so it looks like a genuine upstream bug in the Intel graphics kernel driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1263681 Title: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1263681/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274109] [NEW] compiz snapping windows make some windows go bad
Public bug reported: I really dislike the windows snapping to the edges of the screen. So I deactivated snapping windows in compiz config settings manager. But this made Chrome disappear, I had to kill chrome before I could restart it, but then again it went bad. In my Eclipse window, the window resize buttons disappeared. activating snapping windows solved the issues. But I really dislike windows snapping to the edges. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 29 14:15:57 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2014-01-04 (24 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Dell System XPS L322X MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 29 09:27:21 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- 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/1274109 Title: compiz snapping windows make some windows go bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1274109/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 736829] Re: Two finger scrolling on touchpads should be enabled by default
Is this really an issue? It's enabled by default when edge scrolling is not enabled. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Triaged = Invalid ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/736829 Title: Two finger scrolling on touchpads should be enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/736829/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
If you feel like doing the stablerelease update paperwork and verifications, you could get it fixed in saucy (and indirectly lts- saucy). But that would take some efford into finding out the bare minimum to make things work, which is probably too much work. :) ** Changed in: xserver-xorg-video-openchrome (Ubuntu) Status: Confirmed = Fix Released ** Also affects: xserver-xorg-video-openchrome (Ubuntu Trusty) Importance: Low Status: Fix Released ** Also affects: xserver-xorg-video-openchrome (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Assignee: (unassigned) = Dmitry Shachnev (mitya57) ** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Importance: Undecided = Low ** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1261916] Re: Missing letters in spice client session with KVM guest
** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1261916 Title: Missing letters in spice client session with KVM guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
Am 29.01.2014 09:39, schrieb Steve Beattie: The most proper way that I can see to address this would be to rely on the default dpkg-buildflags to get the basic level of protections. Then to get all the protections, build depend on hardening-wrapper and export DEB_BUILD_HARDENING=1 in debian/rules. I've attached a debdiff that I've verified builds on all available architectures for ureadahead, since that package is also hitting this issue. yes that was the fix I had in mind. The least invasive workaround would be to export MALLOC_CHECK=2 at build time (i.e. in debian/rules), as this causes glibc to abort without attempting to produce a backtrace when it detects internal malloc corruption. This unfortunately still leaves configure believing that 'gcc -static' doesn't work, but it at least causes builds not to hang. sure, that would mimic the behaviour we did see before the glibc update, but papering over the original issue. In practice this shouldn't be an issue because we only build static binaries in very few cases. -- 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/1266492 Title: ld:i386 crashes with -static -fPIE -pie To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1266492/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273246] Re: [gen4] gpu hang due to batch overflow
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1273246 Title: [gen4] gpu hang due to batch overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273246/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Assignee: Dmitry Shachnev (mitya57) = Erick Brunzell (lbsolost) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1041790]
*** Bug 74180 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1269928] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
Christopher M. Penalver, the command (synclient) did not make the cursor less jumpy. -- 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/1269928 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1269928/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1269928] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
Maarten Lankhorst, I updated to xorg 1.15, this did not fix the problem. ubuntu@ubuntu:~$ Xorg -version X.Org X Server 1.15.0 Release Date: 2013-12-27 -- 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/1269928 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1269928/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 659793] Re: xserver-xephyr: Couldn't find keyboard driver evdev
Hi, I am not Oliver Breuer, but this bug is definitely still there in package: xserver-xorgVersion: 1:7.7+1ubuntu7 (xserver-xorg-coreVersion: 2:1.14.5-1ubuntu2) (xserver-xephyr Version: 2:1.14.5-1ubuntu2) The package autoconfiguration does somehow not work and omits the evdev functionality for the kdrive xserver contained in this Ubuntu package (likely also in the Debian package). However, when manually compiling with ./configure --enable-kdrive --enable-kdrive-evdev --enable-kdrive-mouse --enable-kdrive-kbd, the compiled Xephyr binary (hw/kdrive/ephyr/Xephyr or build- main/hw/kdrive/ephyr/Xephyr in the build tree) does work as expected with evdev enabled. Therefore, the workaround for people who want the xorg-server (xserver-xephyr binary package) with support for evdev enabled, I recommend compiling manually with the above mentioned configure options manually added to debian/rules. (It seems compiling with DEB_BUILD_OPTIONS=--enable-kdrive-evdev etc. is not supported). For a quick fix under Ubuntu Saucy (with newest Xserver from saucy- updates repository enabled) or Ubuntu Trusty alpha, I included a patch. The package can be compiled the Debian way: mkdir -p ~/src/xorg-server-evdev-patch cd ~/src/xorg-server-evdev-patch wget #(URL to patch) apt-get source xorg-server cd xorg-server-1.14.5 #(or the corresponding package version) patch -p1 ../xorg-server-1.14.5-patch-kdrive-evdev (optional: change package version in debian/changelog not to have the package replaced during later upgrades) dpkg-buildpackage -uc -us -b sudo dpkg -i ../xserver-xephyr_1.14.5-1ubuntu2_amd64.deb ../xserver-common_1.14.5-1ubuntu2_all.deb If someone understands the build system used in xorg-server package better than me, please feel free to fix the bug in the build system's configure script (autodetection does not work, it seems). ** Attachment added: PATCH: Enable evdev support for kdrive-based X-server in Ubuntu package xorg-server https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/659793/+attachment/3961839/+files/xorg-server-1.14.5-patch-kdrive-evdev -- 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/659793 Title: xserver-xephyr: Couldn't find keyboard driver evdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/659793/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1269928] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad
Maarten Lankhorst, thanks for commenting towards this bug report. From personal experience, and others on Launchpad, utilizing the latest BIOS has addressed a myriad of problems, including touchpad issues (myself included). However, if you prefer not to see BIOS updates occur, I'm not going to argue with you. -- 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/1269928 Title: Jumpy Mouse Cursor using Thinkpad X230 Touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1269928/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1254442] Re: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11)
Really don't understand why Precise just received an update to the new driver, while Saucy still nothing... -- 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/1254442 Title: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1263681] Re: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging
** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1263681 Title: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1263681/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 736829] Re: Two finger scrolling on touchpads should be enabled by default
Maarten Lankhorst, thanks for commenting towards this. For me, I would like to have two finger scrolling enabled by default, without having to disable edge scrolling. As well, I could see why others would prefer the same thing, over the status quo. This wouldn't be an issue, given one being knowledgeable enough could enable this by default, as noted in the Bug Description. I'm not aware of any negatives of this change in default behavior, but I'll let one more knowledgeable than I speak towards this. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Invalid = Opinion -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/736829 Title: Two finger scrolling on touchpads should be enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/736829/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274224] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1188123 *** https://bugs.launchpad.net/bugs/1188123 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1188123, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1274224/+attachment/3961911/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961913/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961914/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961915/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961916/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961917/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1274224/+attachment/3961918/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1188123 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1274224 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1274224/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274226] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1188123 *** https://bugs.launchpad.net/bugs/1188123 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1188123, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1274226/+attachment/3961925/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961928/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961940/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961942/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961943/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961944/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1274226/+attachment/3961945/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1188123 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1274226 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1274226/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274241] [NEW] Typo in libpciaccess debian/control
Public bug reported: The libpciaccess debian/control file spells 'independent' incorrectly in 2 places: Description: Generic PCI access library for X Provides functionality for X to access the PCI bus and devices in a platform-independant way. and Description: Generic PCI access library for X - development files Provides functionality for X to access the PCI bus and devices in a platform-independant way. . This package contains the development files for libpciaccess. The fix is to s/independant/independent/g . Reproducible in libpaciaccess 0.13.2-1 ** Affects: libpciaccess (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1274241 Title: Typo in libpciaccess debian/control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/1274241/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1254442] Re: Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11)
Agreed. I added the SRU details, so this bug report should get more attention. ** Description changed: - Please upgrade to new upstream release v. 13.12. This driver supports - Kernels up to 3.12 and Xorg up to 1.14; ie. it should fully work on - Ubuntu 13.10. + Please upgrade to new upstream release v. 13.12. + + [Impact] + + This driver supports Kernel up to 3.11 and Xorg up to 1.14; ie. it + should fully work on Ubuntu 13.10. The version 13.11 Beta V9.4 also fixes the following issues: [372656] : Resolves crash when resizing Konsole [388325] : Resolves brightness adjustment issues [388818] : Resolves kernel module compile failure when CONFIG_UIDGID_STRICT_TYPE_CHECKS is enabled [388335] : Avoids the new GPL symbol acpi_bus_get_device for new kernel support [386897] : Resolves system hang on resume from S4 with OpenGL screen saver running - The changelog for the v. 13.12 is in comment 3 below. - It might make sense to also upgrade the stable package, as the v. 13.11 beta 9.4. is the first version that has native support (without DKMS drivers) for Saucy's Kernel. + The change log for the v. 13.12 is in comment 3 below. + + It might make sense to also upgrade the stable package, as the v. 13.11 + beta 9.4. is the first version that has native support for Saucy's + Kernel. Source and more information can be found from http://support.amd.com/en- - us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx + us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx and + http://support.amd.com/en-us/kb- + articles/Pages/amdcatalyst13-12linreleasenotes.aspx + + + [Test Case] + + After installing the update, users should be able to boot the system as + usual, with no regressions of any kind. + + [Regression Potential] + + Low. The new driver version doesn't add any new features apart from + having a native support for Kernel 3.11. All other changes are bug + fixes. + Thanks. ** Summary changed: - Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) + [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) -- 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/1254442 Title: [SRU] Please upgrade to new upstream release v.13.12 (has support for Saucy's Kernel 3.11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1254442/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1262238] Re: [SRU] Add support for the lts-saucy stack
Precise will have newer version of fglrx-installer-updates than Saucy after this change. Could you please update Saucy's package too? Please see bug 1254442 for the SRU request. Thanks. -- 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/1262238 Title: [SRU] Add support for the lts-saucy stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 659793] Re: xserver-xephyr: Couldn't find keyboard driver evdev
The attachment PATCH: Enable evdev support for kdrive-based X-server in Ubuntu package xorg-server seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/659793 Title: xserver-xephyr: Couldn't find keyboard driver evdev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/659793/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
I think Saucy, and the 13.10 hardware enablement stack for Precise should both be marked won't fix because they're only supported through July of this year. But I'm not qualified to mark it as such. I will continue to test Edubuntu Trusty w/Flashback (Metacity) to watch for any regressions before it's released in April. And as I mentioned in comment #21 the typical Precise end user is wise to just use the archived 12.04.1 images for fresh installs. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274241] Re: Typo in libpciaccess debian/control
It's not really worth a ubuntu delta to fix it but I fixed it in the debian unstable git branch so it'll come in whenever its updated next. Thanks! http://anonscm.debian.org/gitweb/?p=pkg- xorg/lib/libpciaccess.git;a=commit;h=07dfb14eba868d110da6d1eec3f06f6cc299343f ** Changed in: libpciaccess (Ubuntu) Status: New = Fix Committed ** Changed in: libpciaccess (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1274241 Title: Typo in libpciaccess debian/control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/1274241/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1111884] Re: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT
Still happens on current 13.10, all update applied. Sad, after one year... 02:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) ~# uname -a Linux Artemis 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:16:27 UTC 2013 i686 athlon i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/884/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273652] Re: apply of multi-monitor setting results in crash
did you follow the instructions in the link? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1273652 Title: apply of multi-monitor setting results in crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273832] Re: [i915] Lockscreen/lid-close xserver freeze if UXA accel used.
It sounds like the fairly typical error that UXA is eating the vblank notification whilst DPMS off and not informing the client that they are no longer ignored. How about trying Option Triplebuffer false? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1273832 Title: [i915] Lockscreen/lid-close xserver freeze if UXA accel used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1273832/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Assignee: Erick Brunzell (lbsolost) = (unassigned) ** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Status: In Progress = Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274351] [NEW] Dropbox icon is not in panel
Public bug reported: After starting Ubuntu (13.10), Dropbox icon is not in panel. I try to launch it manually, but ask me superuser password. I put in my administrator password but nothing happens. It works when I go to /home .../.dropbox-dist and click on file dropbox. Every time I start Ubuntu I need to do this. The problem is new, from 3 or 4 days ago. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 30 01:36:16 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a84] Subsystem: Hewlett-Packard Company Device [103c:2a84] InstallationDate: Installed on 2013-11-15 (75 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Compaq dx7500 Microtower MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=dad58c2e-08a7-46a8-bc17-e5b420dbdebe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.14 dmi.board.name: 2A84h dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.asset.tag: CZC9345CCL dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd05/11/2009:svnHewlett-Packard:pnHPCompaqdx7500Microtower:pvr:rvnPEGATRONCORPORATION:rn2A84h:rvr1.03:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: HP Compaq dx7500 Microtower dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 29 01:27:08 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputNOVATEK USB Keyboard KEYBOARD, id 9 inputNOVATEK USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 49203 vendor PHL xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- 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/1274351 Title: Dropbox icon is not in panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1274351/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274351] Re: Dropbox icon is not in panel
** Summary changed: - Icon in panel dont work + Dropbox icon is not in panel ** Description changed: After starting Ubuntu (13.10), Dropbox icon is not in panel. I try to launch it manually, but ask me superuser password. I put in my administrator password but nothing happens. It works when I go to /home .../.dropbox-dist and click on file dropbox. Every time I start Ubuntu I need to do this. The problem is new, from 3 or 4 days ago. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 30 01:36:16 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: - Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Device [103c:2a84] -Subsystem: Hewlett-Packard Company Device [103c:2a84] + Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Device [103c:2a84] + Subsystem: Hewlett-Packard Company Device [103c:2a84] InstallationDate: Installed on 2013-11-15 (75 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP Compaq dx7500 Microtower MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=dad58c2e-08a7-46a8-bc17-e5b420dbdebe ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.14 dmi.board.name: 2A84h dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.asset.tag: CZC9345CCL dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd05/11/2009:svnHewlett-Packard:pnHPCompaqdx7500Microtower:pvr:rvnPEGATRONCORPORATION:rn2A84h:rvr1.03:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: HP Compaq dx7500 Microtower dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 29 01:27:08 2014 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 - inputNOVATEK USB Keyboard KEYBOARD, id 9 - inputNOVATEK USB Keyboard KEYBOARD, id 10 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 + inputNOVATEK USB Keyboard KEYBOARD, id 9 + inputNOVATEK USB Keyboard KEYBOARD, id 10 xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 49203 - vendor PHL + product id 49203 + vendor PHL xserver.version: 2:1.14.5-1ubuntu2~saucy1 -- 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/1274351 Title: Dropbox icon is not in panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1274351/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1159562] Re: Triple monitor displays revert to defaults upon login
Hi, this is no longer an issue with the version of Ubuntu I have now: 13.10 I won't have a chance to check with the latest development release of Ubuntu at the moment. I'm too busy I'm afraid! -- 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/1159562 Title: Triple monitor displays revert to defaults upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1159562/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1213338] Re: Displaylink slow graphic performance on Ubuntu 13
I also have this problem, but the funny thing is, if I maximize any window on the display link monitor, the issue of choppy mouse movements goes away. I will clarify that dragging a window around is still choppy, but not nearly as bad.. I even tried setting the background color to 'black' thinking maybe the issue was with a background image, but no such luck. -- 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/1213338 Title: Displaylink slow graphic performance on Ubuntu 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1213338/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1274374] [NEW] iogear display link causes choppy/delayed mouse movement
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1213338?comments=all ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.13.1-031301-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None Date: Wed Jan 29 19:33:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 980 [1028:0342] InstallationDate: Installed on 2014-01-29 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. OptiPlex 380 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.1-031301-generic root=UUID=d34b5c7d-00b9-4d8e-b330-9c9962ed264e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 29 17:14:45 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubuntu -- 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/1274374 Title: iogear display link causes choppy/delayed mouse movement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1274374/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 221112]
(In reply to comment #45) (In reply to comment #44) Until a solution is to be found, could 518c769d be reverted for now? Breaking the very standard behavior of right control It does not break the very standard behavior of right control any more than altrgr breaks the very standard behavior of right alt For me it does. My keyboard has an Alt Gr label on the AltR key, so it indeed is expected to behave differently from Alt_L, but my ControlR key is labeled as Ctrl, just like the ControlL key. And all other keyboards and OSes I ever used did handle ControlR the same as ControlL, as far as I was concerned as a user. Also, I find it more generically problematic to change the behavior of a common key on a widely used keymap. For example the change annoyed me for about a month before I took the time to debug this and edit my keymap -- and I can't imagine what a lambda user could do but learn to deal with it. Also, what is Level5 used for? IIUC, currently nothing but short-nbsp (or at least that I can find, which is practically the same from a user POV), turning Ctrl_R into a virtually useless key. So, what can we do? First, please note, for what is worth, that both Rhythmbox and Totem, which were cited as the applications having a problem with the previous state of things, are not affected anymore. Rhythmbox don't use Control+Space as a shortcut anymore, and Totem seem to react to any space keysym, no matter the modifiers. So, unless there actually are other applications using Control+Space and suffering of the issue (Code::Blocks?), the problem does not even exist anymore. Also, maybe I just don't know how one is supposed to process the events, but those bugs look like an application or toolkit issue to me, is it? Then, practical changes. Before the change, Space behaved like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 20 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | And now we have: Shift* | ControlL | Level3 | Level5 || keysym| XLookupString ||- | |||| 0x20 | 20 X | |||| 0x20 | 20 | X|||| 0x20 | 00 | | X ||| 0x20 | 20 | || X || 0x20 | 20 X | X|||| 0x20 | 00 X | | X ||| 0xa0 | c2 a0 X | || X || 0x100202f | e2 80 af | X| X ||| 0x20 | 00 | X|| X || 0x20 | 00 | | X | X || NoSymbol | X | X| X ||| 0xa0 | (empty) X | X|| X || | (no event on Xev???) X | | X | X || NoSymbol | X | X| X | X || | (no event on Xev???) So. IIUC, the problem is having naked Space emit the same XLookupString that Control+Space, right? The new behavior is emitting lookup string 00 with modifier Control, so I guess this is the fix. So, what about simply changing the original map to have a different lookup string on Control? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Or, if we don't want to have anything useful using Control, what about moving 0x100202f to Level3? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x100202f | e2 80 af X | X||| 0x20 | 00 X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Alternatively, the mapping of ControlR to Level5 could be an option (or a slightly different variant, whatever's better). Anything that could prevent me from manually editing my map to have ControlR again would be totally great. -- You received
[Ubuntu-x-swat] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
I think Saucy, and the 13.10 hardware enablement stack for Precise should both be marked won't fix because they're only supported through July of this year. But I'm not qualified to mark it as such. Done. ** Changed in: xserver-xorg-video-openchrome (Ubuntu Saucy) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1140716]
Created attachment 92710 i915_error_state I'm also getting regular Sandybridge GPU lockups with Mesa 10.0.1 and Linux kernel 3.13. dmesg output: [ 918.876872] [drm] stuck on render ring [ 918.876876] [drm] stuck on blitter ring [ 918.876878] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 918.876879] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 918.876879] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel [ 918.876880] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 918.876880] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 932.923240] [drm] stuck on render ring [ 932.923242] [drm] stuck on blitter ring Unfortunately the crash dump doesn't help - it's an empty file! -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1140716]
*** Bug 74180 has been marked as a duplicate of this bug. *** -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1266492] Re: ld:i386 crashes with -static -fPIE -pie
Here's a patch to glibc to set the default value of MALLOC_CHECK_ to 1 (from 3). By doing so, the malloc specific error passed to malloc_printerr() will still be displayed by default, but libc will not attempt to generate a backtrace, which is what is causing the deadlock to occur. Even if the deadlock weren't a problem, it's also valuable from a security perspective, as attempting to malloc() from the same pool that libc has already detected an attacker has corrupted is likely unsafe, and may grant an attacker a chance to regain control. This is also the reason for adding the MALLOC_CHECK_ variable to the list of environment variables for filtering when setuid/setgid programs are invoked. People wishing to see the backtrace for debugging purposes can get the old default behavior back by setting MALLOC_CHECK_=3 in their environment. I've verified that eglibc builds fine with this change, and that xorg- server 2:1.14.5-1ubuntu2 (not containing the workaround that Martin added in 2:1.14.5-1ubuntu3, thus would normally trigger the ld/glibc hang on i386) also builds fine when built against eglibc with this patch on all arches. Fixing this of course doesn't address the binutils bug where ld is corrupting malloc space, or the dpkg-buildflags hardening flaw around -static and -pie (doko, is there a bug already for that?), but it will stop builds from hanging. Note that I don't have upload privileges, so all my patches will need to be sponsored. ** Patch added: local-no-malloc-backtrace.diff https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1266492/+attachment/3962383/+files/local-no-malloc-backtrace.diff -- 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/1266492 Title: ld:i386 crashes with -static -fPIE -pie To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1266492/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1273403] Re: [Dell XPS 13 9333] Touchpad not detected correctly
Similar to bug 1265885. FTR, I tried the blacklist trick and it worked. -- 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/1273403 Title: [Dell XPS 13 9333] Touchpad not detected correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1273403/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
