** Also affects: mesa (Debian)
Importance: Undecided
Status: New
** Also affects: mesa (Fedora)
Importance: Undecided
Status: New
--
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
Public bug reported:
GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on
Ubuntu LTS 20.04
USER@COMPUTER:~$ glxgears
X Error of failed request: GLXUnsupportedPrivateRequest
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 17 (X_GLXVendorPrivateWithRep
A 'backport' of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic should do
the trick as this is fixed by NVidia in nvidia-340.106:
http://www.nvidia.com/Download/driverResults.aspx/130042/en-us
"Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page
Attribute Table (PAT
Dariusz,
Would you like me to update to 14.10 as well and try the utopic patched
kernel? I want to upgrade soon, anyway.
Or do you need my current 14.04 to test trusty stuff?
Hartelijke groet,
Wouter van der Graaf
Dynora / Plangage
+31 78 843 3139
Op 30 okt. 2014 14:26 schreef Dariusz
utput of xinput list, which should show
'ATML1000:00 03EB:842F'.
Lastly, my brightness keys don't work anymore.
When I reboot with official kernel 3.13, everything works again. Of
course, except for MST.
Can you perhaps explain what's going on?
Kind regards,
Wouter
Op 20
I suspect this is a kernel bug, because switching back to older 3.8
kernel makes my trackpad correctly recognized in
/proc/bus/input/devices.
** Summary changed:
- Dell XPS 12 2013 Haswell synaptics trackpad not recognized anymore in Ubuntu
kernel 3.10 and 3.11rc
+ Dell XPS 12 2013 Haswell synap
I've upgraded to the latest saucy 3.11.0-7 kernel, but the trackpad is
still not recognized as Synaptics. In kernel 3.8 it did work as
expected.
** Description changed:
First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8.
Trackpad was functioning correctly (e.g. two-finger sc
Is this perhaps a kernel bug and should this report therefore be
reassigned to the kernel team?
--
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/1219753
Title:
Dell XPS 12
In fact my bug report is based on kernel v3.11-rc7-saucy with 13.10.
Everything in my XPS 12 2013 seems to work fine with current Saucy
development and kernel 3.11rc, *except* the trackpad. Strange that my
Synaptic did work in 3.8 and not anymore since 3.10 and 3.11rc.
--
You received this bug no
** Attachment added: "Output of xinput --list"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799037/+files/xinput
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
** Attachment added: "Output of Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799038/+files/Xorg.0.log
** Attachment removed: "XorgConf.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+a
** Attachment added: "Output of /proc/bus/input/devices"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1219753/+attachment/3799036/+files/devices
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input
Public bug reported:
First I installed stock Ubuntu 13.04 Raring Ringtail with kernel 3.8.
Trackpad was functioning correctly (e.g. two-finger scrolling worked)
and was recognized as Synaptics device in /proc/bus/input/devices.
Due to very new Intel wireless 7260 hardware that did not work in ker
Sorry can't help with that anymore, don't have that laptop anymore. Will
close the bug.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-
Try to follow the steps in this link:
http://askubuntu.com/questions/122209/how-do-i-modify-or-disable-the-
huds-use-of-the-alt-key. By disabling the shortcut key to show the HUD,
I'm now able to hold alt +2 to type @ without adding a ","
--
You received this bug notification because you are a me
I hope this can be fixed, I have the same problem on my laptop with a
separate numeric keyboard (for data input), does someone have a
workaround?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.lau
Evidence suggests this is a problem with the unity-plugin in Compiz,
rather than a problem with TwinView. (No problems with Unity2D, XFCE,
KDE, etc.)
** Changed in: unity (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
whic
I've been experiencing these same problems when extending my desktop.
Cloning the desktop works, but system is unstable for a minute or two.
(As described in bug 877438)
chipset: nVidia Corporation GF104 [GeForce GTX 460] (rev a1)
nvidia-current: 280.13-0ubuntu6
--
You received this bug notifica
I've got the same problem on a nVidia Corporation GF104 [GeForce GTX
460] (rev a1). After cloning the screen the system gets unusable; Compiz
gets a relatively high load (~0.9 on a 6-core). Load gets lower after a
while, system becomes usable again. Some Compiz plugins (desktop-zoom
for example) do
I can confirm that with xserver-xorg-input-wacom 1:0.10.5-0ubuntu1 this
issue has been resolved.
--
Spurious stylus events with serial wacom tablet in lucid
https://bugs.launchpad.net/bugs/532720
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-
I haven't managed to test the git version with the bug fix yet, but I
assume that that will indeed fix it. The upstream bug report is very
similar to this (to the point where I was wondering whether this bug
report had been copied to upstream ;-) ). I am looking forward to
testing 0.10.5. Any ch
No change after BIOS upgrade to 1.15 for X60 tablet. But really, who
thought it would be a good idea to distribute BIOS upgrades for laptops
without optical drives as CD images that don't work on USB drives?
--
Spurious stylus events with serial wacom tablet in lucid
https://bugs.launchpad.net/b
I should have made clearer that the warnings with the stylus only show
up when there is actual contact with the screen. Just moving the
pointer by keeping the stylus a millimeter away from the screen works as
expected and without warnings, but as soon as I try to select (or draw
in xournal) there
** Attachment added: "Screen shot of xournal with lines drawn by touch and
stylus"
http://launchpadlibrarian.net/40255132/wacom-stylus-bug.pdf
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/40254312/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launch
Public bug reported:
When using the stylus on my Thinkpad X60 tablet (serial wacom tablet) in
xournal, it is not possible to draw anything. There seem to be spurious
events in the bottom right corner of the screen (resulting in straight
lines, I will attach a xournal screen shot). Using the styl
Fix confirmed working on thinkpad X60 tablet with xserver-xorg-input-
wacom 1:0.10.3+20100109-1ubuntu2. Stylus is working with some glitches
(will file a different bug), multi-touch is working well.
--
Serial Tablet PCs not supported in lucid
https://bugs.launchpad.net/bugs/522318
You received t
Thanks! On a Thinkpad X60 tablet this works now too, after adding the
additional udev rules (as a separate file 65-xorg-wacom.rules, not at the end
of 69-xserver-xorg-input-wacom.rules for some reason, I am not a udev expert).
The output of xsetwacom is
Serial Wacom Tablet eraser ERASER
Se
I'm seeing the same with the intel driver on a Debian testing system, so
the cause of the issue might be outside the nv driver (since I'm not
using it.)
Fwiw, I mostly hit this problem when I connect an external display
device to my laptop and switch resolutions using the standard Gnome
tools for
This has been fixed now, reinstalling jaunty and installing the latest
karmic updates worked fine. It seems like this was a duplicate of bug
421225 I got the same error messages when trying to run startx from the
console.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Fix Released
--
X
It is hard to tell which one of the two fails, but my best guess would
be X. I can't login to a console to check, because when I press ctrl-
alt-f1 I get a scrambled screen and can't do anything. There are no boot
messages shown, just xsplash and a black screen repeating each other.
** Changed in:
** Tags added: ubuntu-boot
--
X/GDM doesn't start on Karmic Koala
https://bugs.launchpad.net/bugs/434320
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https://launchpad
** Attachment added: "KarmicXorg.0.log"
http://launchpadlibrarian.net/32188926/KarmicXorg.0.log
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/32188927/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/32188928/LsHal.txt
** Attachmen
Public bug reported:
Binary package hint: xorg
On Karmic (either upgraded from Jaunty or using the alpha 6 cd), boot
fails at the point where xsplash should switch to gdm. Xsplash is
displayed normally, but then in the end it keeps flashing to a black
screen and then back to xsplash again. It doe
Looks like this is the same as Debian#496838. Any clue what exactly
causes/fixes this?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => New
--
[i946GZ] Xserver black screen on 3/28/09 update of Jaunty
https://bugs.launchpad.net/bugs/350399
You received this bug notif
34 matches
Mail list logo
