** Changed in: linux-restricted-modules (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
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/1925522
Title:
Introduce the 465
** Changed in: linux-restricted-modules (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
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/1925522
Title:
Introduce the 465
Still seems to fail:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-
drivers-390/20210331_152743_2b7cd@/log.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Re-triggered ADT run with proposed version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1922099
Title:
nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1922099
Title:
Public bug reported:
This is a scripted bug report about ADT failures while running nvidia-
graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this
is caused by the tested source or the kernel has, yet, to be determined.
Testing failed on:
armhf:
** Changed in: linux-hwe (Ubuntu)
Status: In Progress => Fix Committed
--
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/1881137
Title:
Introduce the new NVIDIA 418-server and
affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu)
Importance: Undecided => Low
** Changed in: linux-hwe (Ubuntu)
Status: New => In Progress
** Changed in: linux-hwe (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
I am adding the block-proposed-bionic before this falls in between
cracks. Right now we ended up in a situation where the nvidia-440
modules were added to the kernel lrm package build but the version used
for the nvidia-390 modules was not updated to the proposed version. The
hope is that having
[ 6732.868007] mce: [Hardware Error]: CPU 0: Machine Check Exception: 4 Bank 4:
b2070f0f
[ 6732.868007] mce: [Hardware Error]: TSC 71912a367e5
[ 6732.868007] mce: [Hardware Error]: PROCESSOR 2:10ff0 TIME 1412263116 SOCKET
0 APIC 0 microcode 41
[ 6732.868007] mce: [Hardware Error]: Run
After a cold boot today. Things looked relatively good for quite a while
(menus, youtube and glmark2). But while running glmark2 (for several
iterations):
[ 5792.435913] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.515102] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.597439] nouveau E[Xorg[1377]]
Ok, so the same happens when running a glmark2 loop with a 3.13 kernel.
So not related to the problem I initially had. I would say that was
quicker to trigger and seems to be gone with the latest kernels in
Utopic.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Fix
Public bug reported:
Needs more investigation but the system feels sluggish (video operations not
always smooth). This morning I had a crash in firefox (may not be related) and
it does not always seem to be reproducible. Yesterday I was able to run
glxgears and play a video stream through
And oddly its only gnome-term. Xterm is ok.
--
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/1298517
Title:
Rendering issues in unity with xserver-modeset
To manage notifications about this bug
I tested today with Xen and cirrus or svga and both show the same bug.
** Attachment added: Screenshot from 2014-04-16 18:37:17.png
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1298517/+attachment/4085585/+files/Screenshot%20from%202014-04-16%2018%3A37%3A17.png
--
You received this
Just to confirm that the work-around described in the upstream bug (set
MESA_GL_VERSION_OVERRIDE=1.4 in /etc/environment) works on my GMA950
based netbook).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
While I did not find the package uploaded to proposed, yet, I took the
packages from the link posted in PM and can confirm that it fixes the
regression I saw.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in
After upgrading to the proposed version jockey-text -l (for example)
starts failing for me. The 0.9.7-0ubuntu7.4 version does work.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu-X,
which is
.tmp.unity.support.test.0:
ApportVersion: 2.0.1-0ubuntu15
Architecture: amd64
CompizPlugins:
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
apport information
** Attachment added: .var.log.jockey.log.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441886/+files/.var.log.jockey.log.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441887/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/1080588/+attachment/3441888/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: Devices.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441890/+files/Devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441891/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441892/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441889/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441896/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441894/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441893/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441895/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441898/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441899/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441900/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441902/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441901/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441903/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441905/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441897/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441907/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441906/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441908/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
apport information
** Attachment added: XorgConf.txt
https://bugs.launchpad.net/bugs/1080588/+attachment/3441904/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
Things also became better with the Cirrus driver and VMs. After being able to
login I noticed that my KVM VM (which runs on a rather power efficient, iow not
too fast, machine) still has occasional crashes of this type. And there you can
see (and have to wait) every graphical goodness like
Ok, seems that the problem is somewhere in the radeon driver in the
kernel as installing a 3.2 kernel would boot with usable graphics.
Though frankly that is still X guys kinda domain to me.
** Attachment added: dmesg from 3.2 (12.04 kernel)
Not seeing this with a machine updated today (2012-09-18) which should
have the new stack by now. So probably fixed along the process. Closing.
** Changed in: xorg (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which
The X crash happens when using the cirrus X driver. For KVM there is a
new modeset driver in Quantal which should avoid this but there are
currently races which cause that not to load properly (see bug
#1038055). However the same problem hits Xen HVM guests and for those
(and likely all real hw
No this is a unity (ubuntu alternate iso) installation. The one major
difference between the working laptop and the broken one is that the
broken one has quantal-proposed enabled (and from there is using the new
X stack).
--
You received this bug notification because you are a member of
Tested today after enabling quantal-proposed and pulling the new X
drivers. Result is the same (corruption/hangs) with acceleration
enabled.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in 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/1032622
Title:
[quantal] ctrl+alt+l fail to start screenserver
To manage notifications about this bug go to:
Public bug reported:
Not sure which package to files this against. But it seems to be related
to activating quantal-proposed (which has the new X stack). Now
ctrl+alt+l fails to bring up the screensaver (while a laptop that is on
quantal but not proposed does work). The shortcut looks still to be
No, volumes keys (up/down/mute) do not work either. While in rhythmbox
play/pause, next, previous do work.
--
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/1032622
Title:
[quantal] ctrl+alt+l
Adding a dummy screen section which sets NoAccel allows to start the
GUI at least in Unity2D mode.
--
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/1029582
Title:
Unusable graphics with ATI
Public bug reported:
Release: Quantal (20120726/alpha3)
Architecture: i386 (but also seen on amd64)
Using the alternate CD installation works ok, but rebooting into the
install I am lucky if I get anything on the screen that resembles the
lightdm screen (screenshot of that case will be
--
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/1029582
Title:
Unusable graphics with ATI RS690M
To manage notifications about this bug go to:
** Attachment added: lightdm.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237468/+files/lightdm.log
--
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/1029582
** Attachment added: x-0.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237469/+files/x-0.log
--
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/1029582
Title:
** Attachment added: x-0-greeter.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237470/+files/x-0-greeter.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: x-0-greeter.log.old
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237471/+files/x-0-greeter.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1029582 ***
https://bugs.launchpad.net/bugs/1029582
** This bug has been marked a duplicate of bug 1029582
Unusable graphics with ATI RS690M
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: xorg (Ubuntu)
Importance: Undecided = High
--
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/1029582
Title:
Unusable graphics with ATI RS690M
To manage notifications about this
** Attachment added: Internal screen
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237502/+files/IMG_20120726_191128.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Though same happens when only the LVTS is used.
** Attachment added: External screen
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029582/+attachment/3237503/+files/IMG_20120726_191054.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
Release: Quantal (alpha2)
Media: Ubuntu alternates i386
After installing when booting into lightdm, graphics are corrupted and
various ways and it is impossible to log in. Switching to a VT and login
there is ok.
** Affects: xserver-xorg-video-ati (Ubuntu)
Importance:
Ok, trying to automatically get report data fails because of:
ERROR: hook /usr/share/apport/package-hooks//source_xserver-xorg-video-ati.py
crashed:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport/report.py, line 799, in
add_hooks_info
symb['add_info'](self,
** Attachment added: dmidecode.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1018396/+attachment/3205665/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: lspci.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1018396/+attachment/3205667/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1018396/+attachment/3205670/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Attachment added: lightdm.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1018396/+attachment/3205669/+files/lightdm.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Reading through the comments and related reports it sounds to me like
from the kernel side only Maverick would have issues. And with Maverick
just about dropping from being supported it makes no sense to try to get
it fixed.
** Changed in: linux (Ubuntu)
Status: Triaged = Won't Fix
--
** Tags added: kt-worked
--
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/745112
Title:
[arrandale] desktop is messed up with external monitors (x86_64)
To manage
I only closed the kernel/linux task, not the xorg one. Maybe I was wrong
with that, in which case it can be set back to open. But it looked like
the remaining problems where not in kernel modules but in the synaptics
driver.
--
You received this bug notification because you are a member of
I may be overlooking something but to me it looks that (at least for the
kernel side), the only change needed would be:
commit 3bfa321e662edf90fb8123a02c987c2965fa50bb
Author: Yan Li yan.i...@intel.com
Date: Tue Nov 30 23:51:03 2010 -0800
Input: synaptics - fix handling of 2-button
You might try to manually download and install the two linux-headers and
the linux-image package of a 11.04 kernel. Or try to check with input-
utils whether the inputs created by the driver produce any event. But
any way, you should open a new report about it as it is a different
quite specific
On 12/10/2010 11:01 AM, Hicks wrote:
Hi again. I have updated Ubuntu Maverick 32 bits to Natty, and the problem
still alive. Can you check it? Regards.
From the things that are in the jockey log it feels like this is not something
which this bug report was about (which was the dkms module did
I think the actual binary package has been just very slow to publish. I
had to do a apt-get update just now to make it appear for generic.
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which
Has added to the lbm repo for Maverick.
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-backports-modules-2.6.35 (Ubuntu Maverick)
Status: In Progress = Fix Committed
--
Wacom Bamboo CTH-661 not recognized
Needs also a minor tweak to the meta package to have a generic package
which updates the specific lbm package.
** Changed in: linux-meta (Ubuntu)
Status: New = Invalid
** Changed in: linux-meta (Ubuntu Lucid)
Status: New = Invalid
** Changed in: linux-meta (Ubuntu Maverick)
On 11/19/2010 11:27 PM, mmiicc wrote:
I've enabled proposed and updated following packages:
- linux-headers-generic-pae
- linux-generic-pae
- linux-image-generic-pae
modinfo wacom: filename: /lib/modules/2.6.35-23-generic-
pae/kernel/drivers/input/tablet/wacom.ko
The newer driver is
@mmiicc, I finally found the bug in the package generation which would
accidentally use the generic module even for generic-pae. Could you
download the replaced package for i386 pae and try whether the tablet
works now? Thanks a lot for testing.
--
Wacom Bamboo CTH-661 not recognized
)
Status: New = In Progress
** Changed in: linux-backports-modules-2.6.35 (Ubuntu)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
** Also affects: linux (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: linux-backports-modules-2.6.35
The same LBM approach is taken for Maverick. I will leave the
development task open for now. As the support is in linux-next and Natty
probably settles with 2.6.37 or later, this would need to get verified
whenever we are close to Natty release.
** Changed in: linux (Ubuntu Maverick)
)
Status: New = In Progress
** Changed in: linux-backports-modules-2.6.35 (Ubuntu Maverick)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
** Changed in: linux-backports-modules-2.6.35 (Ubuntu)
Status: In Progress = Invalid
** Changed in: linux-backports-modules
As long as the change has not become part of the official linux-
backports-modules package you actually may loose support when there is a
newer kernel with a higher abi number. I am right now trying to get this
done. Then you would need to install linux-backports-modules-input-
generic-pae (which
Hm, maybe it just is yet another other id? Could you extract the udevadm
info like in comment #3?
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which is a direct subscriber.
Ok, thanks. So no, it is the same 00d3 model id that should be supported
by the driver. This maybe sounds stupid but as I cannot see what you did
or did not, it can be worth asking. In case you have not rebooted after
installing the package and the tablet was connected all the time, the
old module
Good just checking. :) Actually invalid module format normally is not
the full truth but it should give some more hints when you look at the
output of dmesg (something like disagrees about symbol or anything else
that might be related).
--
Wacom Bamboo CTH-661 not recognized
Doh! I think I know what went wrong. I seem to have forgotten to add the
posinst files to let the installation run depmod. But don't do that right now,
if you could just download the package again (I replaced the files) and install
that version over, it should do it and the path of the wacom
Yes, building the packages is a bit more time consuming without having full
access to the build environment and I was travelling. So I only prepared the
generic packages for testing. I will start them now and upload as soon as I got
them build.
--
Wacom Bamboo CTH-661 not recognized
This is how it *should* work. Better not ask why it did not before
because I don't know. Ok, added the missing flavours too for now.
--
Wacom Bamboo CTH-661 not recognized
https://bugs.launchpad.net/bugs/527912
You received this bug notification because you are a member of Ubuntu-X,
which is a
Ok, at the moment its just generic backports packages for 32 and 64 bit
which can be found at http://people.canonical.com/~smb/lp527912/ For
Maverick I used the kernel module that currently is in linux-next, which
should be in 2.6.37. If someone can confirm that this enabled the non-
working
It should not really be necessary to insert the module by hand. Of
course that requires a 2.6.35-22-generic kernel to be installed and
actively running and you plug the tablet in or boot with it plugged in.
Does modinfo wacom show a path including updates and uname -r a
2.6.36-22-generic?
--
I will put together a similar linux-backports-modules addition for Maverick next
week. The problem is that the other pads had been receiving help from upstream
too. Just the wacom stuff seems to be delayed. I looked into linux-next and it
seems to be queued for 2.6.37. Until then the best option
Yes, this is not surprising. The IDs are only present in the sourceforge
driver, not in the current upstream tree. So MAverick cannot support it.
I was referring to the backports modules package for Lucid which
provides the sourceforge driver.
It is not practical/desirable to mix in a sourceforge
It seems this might be supported by the sourceforge wacom driver which
is currently under review to be added to linux-backports-modules of
Lucid. See http://bugs.launchpad.net/bugs/606278 for details and a link
to test packages.
** Tags added: kernel-candidate
** Tags removed: kernel-needs-review
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
Status: Triaged = In Progress
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
Assignee: (unassigned) = Stefan Bader (stefan-bader-canonical)
--
[MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu Hardy)
Status: In Progress = Fix Committed
--
[MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix
for CVE-2010-3081 breaks fglrx
https://bugs.launchpad.net/bugs/642518
You received this bug notification
** Description changed:
+ SRU Justification:
+
+ Impact: Due to kernel changes for CVE-2010-3081 a function that was an
+ inline before has changed to a GPL only function. The fglrx driver
+ cannot link against this and fails to compile. In fglrx only the old
+ inlines (which have been renamed)
Some comment to the problem and info from discussing this on irc (I have
not read through all comments, so sorry if some facts are duplicated).
The problem we are facing is the fact that for resolving the security
issue, upstream patches changed compat_alloc_user_space from being an
inlined
** Also affects: linux (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu Karmic)
Importance: Undecided
Status: New
--
White screen of death on Dell Studio 15
https://bugs.launchpad.net/bugs/460664
You received this bug
** Changed in: xserver-xorg-video-intel (Ubuntu Karmic)
Status: New = Invalid
** Changed in: linux (Ubuntu Karmic)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Karmic)
Status: New = Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix
1 - 100 of 110 matches
Mail list logo
