[Ubuntu-x-swat] [Bug 1780680] Re: Older version in bionic than in xenial

Older versions in bionic than in xenial, as of now: fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27 linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29 ** Summary changed: - Older version in artful than in xenial + Older version in bionic t

[Ubuntu-x-swat] [Bug 1780680] Re: Older version in artful than in xenial

** Description changed: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~

[Ubuntu-x-swat] [Bug 1772607] Re: Mesa 18.0.5 stable release

Until this is uploaded to bionic, the version in bionic is older than in xenial (bug 1780680), which is going to interfere with upgrades. -- 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/1772607 Tit

[Ubuntu-x-swat] [Bug 1780680] [NEW] Older version in artful than in xenial

Public bug reported: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2

[Ubuntu-x-swat] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

I have the same problem on a ThinkPad Yoga 14 20FY. I can reproduce it with the touchpad disabled as described in this report. However, I find it much easier to reproduce (nearly 100% of the time) with the touchpad enabled, as follows: 1. With my left finger, hold down the trackpoint’s left butt

[Ubuntu-x-swat] [Bug 1237904] Re: Xorg crashed with SIGABRT in OsAbort()

** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- 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/1237904 Title: Xorg crashed with SIGABRT in OsAbort() To manage

[Ubuntu-x-swat] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU

Chrome 40 now sets LIBGL_DRI3_DISABLE=1 automatically on desktop Linux (https://code.google.com/p/chromium/issues/detail?id=415681). ** Bug watch added: code.google.com/p/chromium/issues #415681 http://code.google.com/p/chromium/issues/detail?id=415681 ** Also affects: chromium-browser via

[Ubuntu-x-swat] [Bug 1365086] [NEW] Cannot move touchpad by less than ~50 pixels at a time

Public bug reported: I have a Lenovo Y50 UHD (3840×2160) with a ETPS/2 Elantech Touchpad. When I try to move the cursor by a very small amount (a few pixels), by slowly rolling my finger, there is no movement at all until I’ve moved at least 50 pixels or so. Then the cursor jumps* those 50 pixels

[Ubuntu-x-swat] [Bug 1299499] Re: kwin crashes on desktop startup with wobbly windows enabled

The mesa packages in ppa:tjaalton/test also fix the Chrome WebGL crashes that I started seeing on my Westmere laptop after upgrading the kernel from 3.13.0-19 to 3.13.0-20. ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a

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

** Information type changed from Private to Public ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Project changed: xorg-server => xserver-xorg-video-intel -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-se

[Ubuntu-x-swat] [Bug 993506] Re: nvidia-current 295.40-0ubuntu1: nvidia-current kernel module failed to build

asm/system.h was intentionally dropped upstream in v3.4-rc1~54: http://git.kernel.org/linus/0195c002 So nvidia will need to be updated to deal with this. The other three headers (asm/compiler.h, asm/system_info.h, asm/system_misc.h) are ARM-specific and have never been part of x86. -- You receiv

[Ubuntu-x-swat] [Bug 589485] Re: Ignores physical display size and calculates based on 96DPI

** Bug watch added: freedesktop.org Bugzilla #41115 http://bugs.freedesktop.org/show_bug.cgi?id=41115 ** Changed in: xorg-server Importance: Medium => Unknown ** Changed in: xorg-server Status: Invalid => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #23

[Ubuntu-x-swat] [Bug 825548] xinput.txt

apport information ** Attachment added: "xinput.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280728/+files/xinput.txt -- 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.n

[Ubuntu-x-swat] [Bug 825548] GdmLog.txt

apport information ** Attachment added: "GdmLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280707/+files/GdmLog.txt -- 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.n

[Ubuntu-x-swat] [Bug 825548] GdmLog1.txt

apport information ** Attachment added: "GdmLog1.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280708/+files/GdmLog1.txt -- 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

[Ubuntu-x-swat] [Bug 825548] Dependencies.txt

apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280704/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bug

[Ubuntu-x-swat] [Bug 825548] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280703/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bug

[Ubuntu-x-swat] [Bug 825548] drirc.txt

apport information ** Attachment added: "drirc.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280723/+files/drirc.txt -- 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

[Ubuntu-x-swat] [Bug 825548] locale.txt

apport information ** Attachment added: "locale.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280724/+files/locale.txt -- 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.n

[Ubuntu-x-swat] [Bug 825548] peripherals.txt

apport information ** Attachment added: "peripherals.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280725/+files/peripherals.txt -- 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.

[Ubuntu-x-swat] [Bug 825548] setxkbmap.txt

apport information ** Attachment added: "setxkbmap.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280726/+files/setxkbmap.txt -- 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.laun

[Ubuntu-x-swat] [Bug 825548] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280716/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https:/

[Ubuntu-x-swat] [Bug 825548] DpkgLog.txt

apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280705/+files/DpkgLog.txt -- 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

[Ubuntu-x-swat] [Bug 825548] XorgLog.txt

apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280720/+files/XorgLog.txt -- 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

[Ubuntu-x-swat] [Bug 825548] LightdmDisplayLog.txt

apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280710/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. h

[Ubuntu-x-swat] [Bug 825548] UdevLog.txt

apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280718/+files/UdevLog.txt -- 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

[Ubuntu-x-swat] [Bug 825548] GdmLog2.txt

apport information ** Attachment added: "GdmLog2.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280709/+files/GdmLog2.txt -- 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

[Ubuntu-x-swat] [Bug 825548] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280715/+files/ProcCpuinfo.txt -- 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.

[Ubuntu-x-swat] [Bug 825548] GconfCompiz.txt

apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280706/+files/GconfCompiz.txt -- 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.

[Ubuntu-x-swat] [Bug 825548] LightdmGreeterLog.txt

apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280711/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. h

[Ubuntu-x-swat] [Bug 825548] BootLog.gz

apport information ** Attachment added: "BootLog.gz" https://bugs.launchpad.net/bugs/825548/+attachment/2280702/+files/BootLog.gz -- 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.n

[Ubuntu-x-swat] [Bug 825548] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280713/+files/Lspci.txt -- 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

[Ubuntu-x-swat] [Bug 825548] UnitySupportTest.txt

apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280719/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. htt

[Ubuntu-x-swat] [Bug 825548] xkbcomp.txt

apport information ** Attachment added: "xkbcomp.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280729/+files/xkbcomp.txt ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X

[Ubuntu-x-swat] [Bug 825548] Xrandr.txt

apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280722/+files/Xrandr.txt -- 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.n

[Ubuntu-x-swat] [Bug 825548] XorgLogOld.txt

apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280721/+files/XorgLogOld.txt -- 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.la

[Ubuntu-x-swat] [Bug 825548] xdpyinfo.txt

apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280727/+files/xdpyinfo.txt -- 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.launch

[Ubuntu-x-swat] [Bug 825548] Lsusb.txt

apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280714/+files/Lsusb.txt -- 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

[Ubuntu-x-swat] [Bug 825548] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280717/+files/ProcModules.txt -- 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.

[Ubuntu-x-swat] [Bug 825548] LightdmLog.txt

apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/825548/+attachment/2280712/+files/LightdmLog.txt -- 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.la

[Ubuntu-x-swat] [Bug 825548] Re: Touchpad cursor moves twice as fast horizontally after connecting an external monitor

apport information ** Tags added: apport-collected reproducible ubuntu ** Description changed: - After connecting an external monitor, the touchpad starts moving much - faster in the horizontal direction than in the vertical direction, as if - the screen area had been stretched rather than exten

[Ubuntu-x-swat] [Bug 825548] [NEW] Touchpad moves twice as fast horizontally after connecting an external monitor

Public bug reported: After connecting an external monitor, the touchpad starts moving much faster in the horizontal direction than in the vertical direction, as if the screen area had been stretched rather than extended to include the area of both monitors. This is really disorienting, throws off

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

> fglrx and nvidia install a fake alternative in addition to the one for > your architecture, which is meant to override the second alternative > provided by multi-arch mesa (e.g. by i386 mesa if you're using adm64). > This means that you should only configure the alternative for your arch > for no

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

In comment 13: > Yes, we have to upload a new mesa and set versioned breaks. Assuming that was a reply to comment 12, that wasn’t what I was worried about. Even when a new mesa is uploaded with versioned breaks, it will still have the problem I described: “Hmm, it’s still not possible for me to

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

** Tags added: multiarch -- 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/798049 Title: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative To manage notifications ab

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

Hmm, it’s still not possible for me to install nvidia-current on x86_64 but configure it to not be used, because although x86_64-linux- gnu_GL.conf can be overridden by the mesa version, there is no mesa version of i386-linux-gnu_GL.conf, and nvidia’s i386-linux-gnu_GL.conf includes the 64-bit libr

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

> - Add initial support for multi-arch (LP: #798049). Since regen-from-templates is only called from the ‘clean’ target, this will cause the package to be misbuilt on any architecture that the source package wasn’t built on, if the builder does not call debian/rules clean first. The Ubuntu bu

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative

BTW, my patched nvidia-current is available in https://launchpad.net /~anders-kaseorg/+archive/ppa , if anyone else wants it. -- 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/798049 Title: nvidia

[Ubuntu-x-swat] [Bug 798007] Re: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current

I reopened bug 798049, since it has a patch for nvidia-current. -- 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/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To mana

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-current needs to be migrated to per-architecture gl_conf alternative

The libgl1-mesa-glx Breaks: was made unversioned in bug 798007. The nvidia-current fix is still needed. ** This bug is no longer a duplicate of bug 798007 [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-current needs to be migrated to per-architecture gl_conf alternative

** Patch added: "mesa_7.10.3-0ubuntu1_lp798049.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/798049/+attachment/2170902/+files/mesa_7.10.3-0ubuntu1_lp798049.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribe

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-current needs to be migrated to per-architecture gl_conf alternative

** Patch added: "nvidia-graphics-drivers_275.09.07-0ubuntu1_lp798049.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/798049/+attachment/2170901/+files/nvidia-graphics-drivers_275.09.07-0ubuntu1_lp798049.debdiff -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 798049] Re: nvidia-current needs to be migrated to per-architecture gl_conf alternative

** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/798049 Title: nvidia-current needs to be migrated to

[Ubuntu-x-swat] [Bug 798049] [NEW] nvidia-current needs to be migrated to per-architecture gl_conf alternative

Public bug reported: >From the mesa changelog: mesa (7.10.3-0ubuntu1) oneiric; urgency=low … * Merge multiarch support branch: - Declare Breaks: against old versions of xserver-xorg-core and libgl1-mesa-glx that will look for DRI modules only in /usr/lib/dri. - Fix up the maintain

[Ubuntu-x-swat] [Bug 694010] Re: xterm does not paint its window or accept mouse clicks in compiz

-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. https://bugs.launchpad.net/bugs/694010 Title: xterm does not paint its window or accept mouse clicks in compiz ___ Mailing list: htt

[Ubuntu-x-swat] [Bug 694010] [NEW] xterm does not paint its window or accept mouse clicks in compiz

Public bug reported: Binary package hint: xterm When I run xterm under compiz in natty, it never draws anything to its window; the contents of the window remain frozen at whatever was underneath the window when it started. Furthermore, it does not respond to mouse clicks; any mouse clicks to the

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick, natty

The problem persists with natty kernel 2.6.37-4-generic and nvidia- current 260.19.06-0ubuntu1. ** Summary changed: - Loading the nvidia driver causes kernel oops in maverick + Loading the nvidia driver causes kernel oops in maverick, natty -- Loading the nvidia driver causes kernel oops in mav

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick

That’s indeed a kernel oops, though it is a NULL dereference rather than a page fault. Unfortunately your Call Trace got cut off so it’s difficult to say whether it’s related. Did you hard-reboot immediately after the crash? Next time, wait a few seconds and press Alt-SysRq-s to give the kernel

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick

jsgaarde: It looks like your problem is different. You’re getting [ 48.011528] vmap allocation for size 16781312 failed: use vmalloc= to increase size. [ 48.014897] NVRM: RmInitAdapter failed! (0x26:0x:1028) [ 48.014904] NVRM: rm_init_adapter(0) failed which is a known issue: http

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick

Well, I reported the oops to the NVIDIA Linux forum with a log generated by nvidia-bug-report.sh as requested, but I haven’t gotten a response. If you’re seeing the same problem, perhaps replying to that thread would be helpful. -- Loadin

[Ubuntu-x-swat] [Bug 642518] Re: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: fglrx kernel module failed to build

Qihe: You are correct, that is an infinite loop. Use Evan’s patch instead. Evan: You forgot to add the patch to dkms.conf.in, though. (You probably want to use a clever PATCH_MATCH regex that applies it only for kernels that have arch_compat_alloc_user_space.) -- package fglrx 2:8.723.1-0ubunt

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick

This still hasn’t gone away with nvidia-current 256.44-0ubuntu1, nor 256.52-0ubuntu0sarvatt (from xorg-edgers). I can’t use the nvidia driver unless I boot into kernel 2.6.32. Oops while starting X with nvidia 256.52 on kernel 2.6.35-19-generic: BUG: unable to handle kernel paging request at fff

[Ubuntu-x-swat] [Bug 607399] Re: Loading the nvidia driver causes kernel oops in maverick

** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/52176243/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/52176244/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/52176245/BootDmesg.txt ** Att

[Ubuntu-x-swat] [Bug 607399] [NEW] Loading the nvidia driver causes kernel oops in maverick

Public bug reported: I get this kernel oops every time I start X with the nvidia driver enabled. I think this started happening with the upgrade from 2.6.35-5-generic to 2.6.35-6-generic. ProblemType: KernelOops DistroRelease: Ubuntu 10.10 Package: linux-image-2.6.35-9-generic 2.6.35-9.14 Regres

[Ubuntu-x-swat] [Bug 589485] Re: Ignores physical display size and calculates based on 96DPI

This change was introduced for all RandR 1.2 drivers by http://cgit.freedesktop.org/xorg/xserver/commit/?id=fff00df . (Notably, the nvidia binary driver is not affected.) GNOME does also force X back to 96 DPI when gnome-settings-daemon starts up (bug 157398, bug 246718). It’s even more annoying

[Ubuntu-x-swat] [Bug 600374] Re: nouveau forces screen to 96 DPI

I should also mention that this also happens just by starting X from the console with no clients running inside it (so it is not GNOME resizing the screen or anything like that). It happens with both the stock maverick packages and today’s xorg-edgers PPA. -- nouveau forces screen to 96 DPI http

[Ubuntu-x-swat] [Bug 600374] Re: nouveau forces screen to 96 DPI

** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/51196274/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/51196275/CurrentDmesg.txt ** Attachment added: "DRM.card0.TV.1.txt" http://launchpadlibrarian.net/51196276/DRM.card0.TV.1.txt

[Ubuntu-x-swat] [Bug 600374] [NEW] nouveau forces screen to 96 DPI

Public bug reported: Binary package hint: xserver-xorg-video-nouveau With the nouveau driver, my screen is forced to 96 DPI (as reported by ‘xdpyinfo | grep resolution’), and fonts look too small. This did not happen with the binary nvidia driver, which correctly detects my 129×127 DPI display.

[Ubuntu-x-swat] [Bug 597676] Re: New nvidia driver 256.35 available

nvidia-graphics-drivers (256.35-0ubuntu1) maverick; urgency=low [ Alberto Milone ] * debian/nvidia-current-dev*: - Make the dev package conflict with other dev packages which provide nvidia-dev so as to make it possible to install headers directly in /usr/include. * Adapt the

[Ubuntu-x-swat] [Bug 598368] Re: Nvidia restricted driver, black screen

(Oops, wrong bug, sorry!) ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Fix Released => New -- Nvidia restricted driver, black screen https://bugs.launchpad.net/bugs/598368 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-gra

[Ubuntu-x-swat] [Bug 598368] Re: Nvidia restricted driver, black screen

nvidia-graphics-drivers (256.35-0ubuntu1) maverick; urgency=low [ Alberto Milone ] * debian/nvidia-current-dev*: - Make the dev package conflict with other dev packages which provide nvidia-dev so as to make it possible to install headers directly in /usr/include. * Adapt the

[Ubuntu-x-swat] [Bug 592794] [NEW] Rebuild against new Xorg abi

Public bug reported: nvidia-current Provides xserver-xorg-video-6, but maverick’s xserver- xorg Depends xserver-xorg-video-7, and xserver-xorg-core Breaks xserver- xorg-video-6. nvidia-graphics-drivers needs to be rebuilt to pick up the ABI number change. No source modifications are necessary, s

[Ubuntu-x-swat] [Bug 223170] Re: Trackpad scrolling is jerky and difficult to be precise with

I know this isn’t an Ubuntu bug and has been Won’t Fix for some time, but for anyone else looking for the current status of the upstream work, it seems to be stalled: http://hortont.com/blog/posts/2008/12/18/071607.html -- Trackpad scrolling is jerky and difficult to be precise with https://bug

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

openafs in Debian is using dh_dkms now, so this will be fixed in the next sync. ** Changed in: openafs (Ubuntu) Status: New => Fix Committed -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification be

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

Alberto, you failed to note the patch I posted above here (dkms- template-postinst-cleanup.patch), as well as the source package I posted to bug 432780, and so your new bcmwl package completely skips creating the blacklist file: case "$1" in configure) # Build the kernel module

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

** Changed in: dkms (Ubuntu) Status: Fix Released => New -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu.

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

I noticed while putting together an updated package for bcmwl that the template postinst does exit $? after running common.postinst, which skips the rest of the package postinst including any autogenerated #DEBHELPER# scripts. Mario, can I get you to review this patch, which fixes that and does so

[Ubuntu-x-swat] [Bug 124406] Re: Keyboard keys get stuck and repeat (Feisty, Gutsy)

Adam Jackson has a related kernel commit in 2.6.33-rc5: http://git.kernel.org/linus/30a589fde0162aa4dac7c69803aeee8fbe8d1b82 commit 30a589fde0162aa4dac7c69803aeee8fbe8d1b82 Author: Adam Jackson Date: Tue Jan 5 17:56:04 2010 -0800 Input: evdev - be less aggressive about sending SIGIO notifi

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

** Description changed: Packages in Debian & Ubuntu that are using their own postinstall script should remove the logic from there and instead use /usr/lib/dkms/common.postinst . This script contains sufficient logic to figure out the correct kernels to build for and accounts for allowing

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

The new virtualbox-ose-dkms postinst passes an empty arch argument to common.postinst. Mario, is this what you are recommending, or are you planning to fix the hard-coded architecture map in some other way? -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.laun

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

** Also affects: dkms (Ubuntu) Importance: Undecided Status: New -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

Moshroum: thank you for your feedback, but please remember to follow the code of conduct to maintain a respectful atmosphere. Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind. -- Packages using DKMS sho

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

I assume his complaint is that you hard code a map {amd64 → x86_64, lpia → i686, i386 → i686} that is neither complete nor obviously correct, and if this map ever _does_ need to change, that will currently require shipping more updates to every package that uses dkms. It would be better to keep al

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

What’s wrong with ‘uname -m’? (Is this somehow related to allowing builds on a buildd?) But in any event, why can’t /usr/lib/dkms/common.postinst do the architecture detection itself? There’s no reason the module package itself should have to care about that detail. -- Packages using DKMS shou

[Ubuntu-x-swat] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst

** Also affects: openafs (Ubuntu) Importance: Undecided Status: New -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-instal

[Ubuntu-x-swat] [Bug 453365] Re: dkms should start before gdm if needed for video driver

Filed as bug 497137. -- dkms should start before gdm if needed for video driver https://bugs.launchpad.net/bugs/453365 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. ___ Mailing list: htt

[Ubuntu-x-swat] [Bug 453365] Re: dkms should start before gdm if needed for video driver

> --- debian/gdm.upstart2009-12-11 05:36:55 + > +++ debian/gdm.upstart2009-12-14 20:12:34 + > @@ -9,7 +9,9 @@ > start on (filesystem >and (graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 > or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPL

[Ubuntu-x-swat] [Bug 320639] Re: Touchpad movement problems in 0.99.3

Those two patches were already added in 0.99.3-1ubuntu2; the first is obsolete and the second is still there. But I still think we should set MaxSpeed == MinSpeed to avoid double- accelerating the pointer as of Xorg server 1.6 (comment #28), as the double acceleration makes the pointer difficult t

[Ubuntu-x-swat] [Bug 394262] Re: [Karmic] nvidia DKMS building and installation for kernel 2.6.31-1-generic fails with exit status 10

> PATCH_MATCH[1]="^2.6.3[1]" Why are there brackets in "^2.6.3[1]"? I’ve seen that pattern in many dkms.confs, but it doesn’t do anything; "^2.6.3[1]" is the same regex as "^2.6.31". Perhaps this idea came from a corruption of "^2.6.3[1-9]", which at least matches kernels 2.6.31 through 2.6.39?

[Ubuntu-x-swat] [Bug 320639] Re: Touchpad movement problems in 0.99.3

I just tried version 1.1.2-1ubuntu1 with no extra configuration, and my comment 18 still applies: > However, the pointer is still very hard to control, because the > speed varies wildly between its minimum and maximum. > > Here is some documentation from the Xorg wiki which confirms my > suspici

[Ubuntu-x-swat] [Bug 393924] Re: Does not build o n 2.6.31, os-agp.c:296: error: ‘agp_memo ry’ has no member named ‘memory’

*** This bug is a duplicate of bug 394262 *** https://bugs.launchpad.net/bugs/394262 ** This bug is no longer a duplicate of bug 394343 [karmic] Nvidia DKMS installation fails during boot ** This bug has been marked a duplicate of bug 394262 [Karmic] nvidia DKMS building and installation

[Ubuntu-x-swat] [Bug 394343] Re: [karmic] Nvidia DKMS installation fails during boot

*** This bug is a duplicate of bug 394262 *** https://bugs.launchpad.net/bugs/394262 ** This bug has been marked a duplicate of bug 394262 [Karmic] nvidia DKMS building and installation for kernel 2.6.31-1-generic fails with exit status 10 -- [karmic] Nvidia DKMS installation fails durin

[Ubuntu-x-swat] [Bug 376067] Re: [karmic] Please upgrade nvidia-glx-185 to 185.18.14 version

** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New => Confirmed -- [karmic] Please upgrade nvidia-glx-185 to 185.18.14 version https://bugs.launchpad.net/bugs/376067 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics

[Ubuntu-x-swat] [Bug 333550] Re: dpkg-divert mismatch when upgrading or reinstalling nvidia-glx-180

This is not a dpkg bug; it was a bug in the nvidia packaging that has now been fixed. Please report a separate bug against the fglrx packaging. -- dpkg-divert mismatch when upgrading or reinstalling nvidia-glx-180 https://bugs.launchpad.net/bugs/333550 You received this bug notification because