Public bug reported:
After today's artful dist-ugprade, all titlebars are corrupted. The
fonts show only squares.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
.tmp.unity_s
Has there been any updates to this in either the Zesty security channel
or Artful? It's a pretty serious regression.
--
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/1695141
Titl
Confirmed that falling back to nvidia-graphics-drivers-375
375.39-0ubuntu5 fixes the problem.
--
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/1695141
Title:
Recent update broke
% uname -a
Linux subdivisions 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
FWIW, booting 4.10.0-20 hangs on boot so that's not a viable option.
Also, setting Brightness&Lock->Turn screen off when inactive for: Never
does not prevent Ubuntu from sl
Public bug reported:
I just dist-upgraded my Zesty machine and two things broke related to
sleeping the displays. I have a 34" wide panel on the left and a 20"
high resolution Dell on the right.
Everything works fine until the displays sleep, say after a lockscreen
has started. First, the right
Public bug reported:
Unexpected shutdown of Chrome browser after last visit here regarding
the same issue
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: n
Public bug reported:
I had attempted a reboot because system was malfunctioning, at which
system was not recovering from timeouts so I had to shut down manually.
Same error messages as I has sent the last two times today.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Public bug reported:
Hello I had a problem shutting down kept timing out had to manually shut
down. Still getting error messages RE:
main: daemon not run
main: ping failed.
Everything else is in the report sent.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVer
Public bug reported:
I have Ubuntu Nome 16.04.2 64-bit and the same problems persist there is
a report that was sent to you regarding this problem. I keep seeing
this error message in my boot information:
main: daemon not run
main: ping failed
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Packag
Public bug reported:
I stall have bugs and I sent you a report that signifies the problem.
Thank you for your help.,
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKerne
Public bug reported:
I have switched from Ubuntu Mate to Ubuntu Nome and I wish to help you
discover and fix any bugs or problems that may be evidenced within the
Nome Operating System, but also seems to affect Ubuntu Mate.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu
Public bug reported:
Bug report has been added.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Er
Public bug reported:
Extra debug information will be added to the bug report.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.drive
Public bug reported:
Detailed information has been sent after running xdiagnostic tool Ubuntu
16.04 LTS 64-bit
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubu
Public bug reported:
I'm new, and too tired to learn how to look into the bug. I hope the
info the message said would automatically be sent with this is helpful.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Una
I was able to fix this problem on a MacBook Pro 4,1 with a GeForce 8600M GT by
following these instructions:
https://ubuntuforums.org/showthread.php?t=2209602
In this case, installing the current version of Ubuntu (16.04.1) via USB
with a GUID partition table was not a problem.
--
You received
I'm running into the same issue. Has there been any progress on this?
Anyway I can help resolve this?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1563229
Title:
Touchpad recognised as mouse
I'll note that Alt-TAB still works.
--
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/1566878
Title:
Alt-backtick regression
To manage notifications about this bug go to:
https://bugs.launchpad.ne
I narrowed this down by doing a bisect dist-upgrade with disk snapshots.
I.e. take a snapshot, manually upgrade a few packages, reboot, test,
rinse, repeat. The only packages left are the three binary packages
mentioned in the bug report. With the snapshot before upgrading those
packages, Alt-bac
Public bug reported:
dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1 (binary
packages xserver-common, xserver-xorg-core, xvfb) introduces a
regression for Alt-backtick switching between windows of the same
application. Before the upgrade, Alt-backtick works by showing you the
swi
Thanks! Uploaded. BTW, lp:xdiagnose seemed terribly out of date so I
didn't modify it. I'm not sure if there's a current upstream branch for
xdiagnose.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad
As it turns out, xdiagnose was still Depending on Python 2. I completed
the port by switching to --buildsystem=pybuild and dropping all Python
2-isms. I have a diff, attached here, that completes the port to
Python 3 (hence why I re-opened this bug). Before I upload it though,
perhaps Didier co
Today's dist-upgrade, which pulled in new xserver-xorg-core
2:1.17-2-1ubuntu7 and a new unity 7.3.2+15.10.20150921-0ubuntu1 seems to
have restored my full desktop. Closing as invalid for now. Will reopen
if the problem recurs.
** Changed in: xorg (Ubuntu)
Status: Triaged => Invalid
--
Y
A few more data points.
I booted stable Vivid, then dist-upgraded to Wily. When I open the
Displays setting, the highest resolution I'm offered is 16:9 at
2560x1440. There's no option to go to 3440x1440, which is the native
resolution of this monitor.
Debian unstable seems to have no problems d
Hi. Is there anything else I can do to help debug/fix this issue? It's
still a problem with the latest dist-upgrade on wily and it makes my
desktop unusable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
Through a process of disk snapshotting, apt-mark holding certain
packages, and bisecting the dist-upgrade, I've narrowed it down to one
of the following packages. I'm unable to narrow it down any further.
This is the output of `apt-get dist-upgrade --dry-run`
The following packages will be upgrad
This appears to be fixed with today's full dist-upgrade.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
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/1462398
Title:
w
Public bug reported:
I have a 3440x1440 monitor and after today's full dist-upgrade, most of
the screen real-estate is unusable. I see a small rectangular patch in
the lower left corner, and on this patch I can right-button to bring up
the menu. While the rest of the screen will display the curs
After bisecting the dist-upgrade, apt-mark holding various packages
until I found the culprit.
It's either xserver-common, xserver-xorg-core, or xvfb (probably not the
latter).
If I unhold the first two and dist-upgrade, I see the freeze.
** Also affects: xorg-server (Ubuntu)
Importance: Und
Unfortunately, I can't. IIRC, it was a do-release-upgrade from an
earlier version so it was *a lot* of packages.
--
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/1281232
Title:
control/capslock k
I'm not sure why this was marked Incomplete, and while I appreciate the
pointer to the bios update, I don't think it's relevant. This is really
about giving back to the user software remapping of keys and modifiers
in a user friendly way. xmodmap can do it all but it's far from user
friendly. Th
** Also affects: gnome-do (Ubuntu)
Importance: Undecided
Status: New
--
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/1396232
Title:
Xorg freeze
To manage notifications about this bug g
Public bug reported:
gnome-do and Xorg/unity/desktop seem to be incompatible on a fresh
install of either utopic or vivid. This is either tied to 1080p
(1920x1080) or a fresh install of either version. Details as I know
them are provided here.
I have a brand new machine which is running 1080p t
I saw this happen when I tried to log in to my work system this morning,
having been on over the long weekend.
Caps-lock was on, and typing my password was rather awkward as a result.
I have cap-lock bound to Control on this keyboard - there is no key
mapped to caps lock, so it cannot have been t
On Apr 15, 2014, at 06:37 PM, Jakob Bornecrantz wrote:
>This should have been fixed in libgl1-mesa-dri 10.1.0-4ubuntu4, I can't
>see it either, please comfirm.
I'm currently running
libgl1-mesa-dri:amd64 10.1.0-4ubuntu2
and haven't seen it in a while. I'll check again after my next opportuni
With today's dist-upgrade, this problem seems to have gone away. At
least, I can no longer reproduce it with the last given known recipe.
I'll mark this as Incomplete for now and reopen later if necessary.
** Changed in: xserver-xorg-video-vmware (Ubuntu)
Status: Confirmed => Incomplete
-
Hi Jakob. Is there anything else I can do to help push this issue
along? It's so painful ;)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1284134
Title:
Xorg crash
To ma
On Mar 21, 2014, at 11:43 AM, Jakob Bornecrantz wrote:
>Did you fully upgrade the VM?
Yes.
>Tho I no longer need to press enter to close emacs, could this have something
>to do with it?
I'm not sure what this means. Did you try the recipe in comment #5 and
#7?
--
You received this bug notifi
On Mar 20, 2014, at 05:42 PM, Jakob Bornecrantz wrote:
>I'm no longer able to reproduce this bug Barry, Maarten can you?
Oh yes, it's definitely still happening.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
3.13.0-17 seems to be freeze-free, so I'll close this bug for now.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1289410
Title:
On Mar 11, 2014, at 10:15 PM, Joseph Salisbury wrote:
>This issue may have been introduced by the 3.13.6 stable update. Can
>you test the following kernel and see if it also exhibits the bug:
I'm now on 3.13.0-17 and didn't notice the freeze on login after reboot to
this kernel. I'll try a few
% dpkg-query -W xserver-xorg emacs24 xserver-xorg-video-vmware
emacs24 24.3+1-2ubuntu1
xserver-xorg1:7.7+1ubuntu8
xserver-xorg-video-vmware 1:13.0.1.git.20140115.8da9817-0ubuntu2
** Changed in: xorg (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because
Note too that there are certainly other surprising ways to crash X, it's
just that the recipe in #13 is completely reproducible every time.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpa
One other note: I am fully dist-upgraded on Trusty (no held back
packages), but I cannot run the 3.13.0-16-generic #36 kernel because
that exhibits the log in freeze of LP: #1289410. So at grub select
"Advanced options for Ubuntu" and boot the 3.13.0-15.generic kernel.
This allows me to log in and
It's quite easy and reproducible to crash. Here are the steps:
* Log in
* Hit Alt to bring up the launcher
* Start up gnome-terminal
* In the terminal, type `emacs -q`
* In Emacs 24, hit `Ctrl-x Ctrl-c RET` to quit Emacs.
* Go back to the terminal and double click on its menu bar to globally maxi
VMware Fusion 6.0.2 (1398658) on OS X 10.9.2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1284134
Title:
Xorg crash
To manage notifications about this bug go to:
https:/
Problem still exhibits with a rebuild of emacs24. I'm still going to
upload a new Debian merge of emacs24 even though it doesn't fix this
problem. Makes some sense though: it should never be possible for an
application to crash X (or cause some data corruption just by running
that allows some oth
More fun facts:
If, after you start up emacs -q, you immediate quit it, the recipe in #5
still crashes X.
Starting non-X emacs (e.g. `emacs -nw` in a terminal) does not crash X.
Starting multiple terminals does not crash X.
I'm going to try to rebuild Emacs against the current Trusty package se
See also Larry's explanation in the dup bug: LP: #1287148
Maybe the Arch Linux package could be packaged for Ubuntu?
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: Meng Jiao (meng1usa) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
w
% dpkg-query -W linux-image-generic
linux-image-generic 3.13.0.16.20
--
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/1289410
Title:
Xorg freeze
To manage notifications about this bug go to:
Public bug reported:
This may be a kernel bug, and I'll add a bug task for that.
% uname -a
Linux anarchist 3.13.0-15-generic #35-Ubuntu SMP Mon Mar 3 15:54:59 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
With this kernel, I can log in just fine. With -16 however, after I
type my password, the scre
FWIW, neither gnome-terminal nor emacs24 have been updated in a long
while, so this is clearly a regression in the X stack somewhere.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/
I've narrowed it down to some interaction between Terminal and Emacs 24.
You can discount Claws and Gnome Do.
I can reproduce this every time with this recipe:
* reboot
* login
* hit Alt to bring up the launcher
* start up a Terminal
* In the Terminal, enter "emacs -q" to bring up a vanilla Emacs
On Mar 06, 2014, at 11:37 AM, Maarten Lankhorst wrote:
>I don't see a backtrace here.
I have an /etc/X11/core file, but I can't seem to get a backtrace out of it.
ubuntu-bug refuses to file the bug because vmware is involved. Tell me what
you need and I'll happily provide it.
--
You received t
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1284134
Title:
Xorg crash
To manage notific
Any thoughts on this bug? It's making my laptop environment unusable.
:(
** Also affects: xserver-xorg-video-vmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bug
Public bug reported:
I use the Nouveau theme of Gnome-Do, and I bind its invocation to Alt-
Ctrl-Space. Invoking Gnome-Do crashes X and leaves me back at the login
screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic
Another symptom: I have Alt+H rebound to minimize window. This has
worked forever. Now there's a regression where Alt+H will summon the
Help menu. This is even though I have Activate the window menu set to
Disabled and Minimize window set to Alt+H. This used to override the
menu setting, but th
Also: my Emacs window geometry defaults are being partially ignored.
Second window is being mapped taller than the screen.
--
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/1281232
Title:
control/c
It's worse than that. Several apps are not mapping their menus to the
menubar, and several are not inheriting the Ubuntu desktop theme.
Examples include most prominantly firefox and chromium.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Public bug reported:
Probably not an xorg problem, but anyway, after today's dist-upgrade, my
very long standing swap of the control and caps lock keys on my standard
Ubuntu desktop got lost. Now capslock actually is capslock and ctrl is
actually ctrl, despite a my previous settings swapping them
I've put that in and am trying it. Thanks. For the record, gdm is not
istalled in Trusty, so you need to do sudo apt-get install gdm
In my case, I was given the option to make gdm the default during installation.
If not, you need to edit /etc/X11/default-display-manager after installing gdm
-
I'm reopening this because with today's dist-upgrade, the problem has
returned.
** Changed in: xserver-xorg-video-vmware (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubu
Another workaround seems to be:
Open a terminal from the login screen using ++F2 followed by
username and password. Then do:
sudo stop lightdm
sudo lightdm
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.laun
*** This bug is a duplicate of bug 1271186 ***
https://bugs.launchpad.net/bugs/1271186
** This bug has been marked a duplicate of bug 1271186
No 3D acceleration in Trusty - Gallium3D version too new
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
Comment #7 might have been a little misleading. Here's what's
happening. On Trusty right now I have:
% dpkg-query -W libxatracker2
libxatracker2:amd64 10.0.0-1ubuntu4
If however in the course of normal apt-get upgrades, I install:
% rmadison libxatracker2
libxatracker2 | 10.0.1-1ubuntu2 |
Next time, try going into suspend if you can. This always works for me.
Failing that, try ++F2 to bring up a terminal. Log in (your
user name and password) and do 'sudo shutdown -h to shut down properly.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscr
Problem came back after a large update that included a number of xorg
packages ... So the bug is still there as far as I can see at the
current build. I'm happy to carry out further tests.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg i
I had a problem earlier today and wiped the drive with Trusty installed.
I have re-installed and fully updated but no longer see this fault.
Pleas hold until I can see any further problems.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Sorry I didn't read the instruction to update the bios before reporting a
hardware bug of this kind. I can confirm that nothing has changed. The
information requested is:
barry@trusty:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for bar
Thanks for that. I have reflashed the bios to version 1.6 release date
07/11/2013 and will wait to see if the problem is fixed. As the problem
is spasmodic, I will wait a week or so before saying that it is no
longer there.
--
You received this bug notification because you are a member of Ubunt
Confirmed that downgrading restores 3D:
Gallium 0.4 on SVGA3D; build: RELEASE;
--
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/1265406
Title:
libxatracker2 causes OpenGL 2.1 support regression o
By the process of elimination, I've determined that the bug is in binary
package libxatracker2 (source package mesa). If I apt-mark hold that
binary package and dist-upgrade everything else, all is good. If I then
upgrade that package, I end up with broken OpenGL support.
Last known good version
** Package changed: xorg-server (Ubuntu) => mesa (Ubuntu)
--
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/1265406
Title:
X server regression on VMware Fusion with OpenGL 2.1 enabled
To manage no
I'm de-duping this because the X server *should* be choosing Gallium 0.4
on SVGA3D, which it does on older xorg-server versions in Trusty. A
recent update broke this. Targetting xorg-server and I will update it
with some version numbers.
** This bug is no longer a duplicate of bug 1179210
uni
I get no problem when booting into Saucy which I have as a dual-boot
installation.
--
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/1264543
Title:
Trusty boots spasmodically with inactive keyboard
Public bug reported:
Every third or fourth boot, the keyboard is not found although it is
accessible by grub2 and by pressing ++F2 and withing the
terminal. Logout and login from the terminal followed by
++F7 to reaccess X does not bring back the keyboard. My
current workaround is to use suspend
Public bug reported:
module fails to build on 12.04.1, .2 or .3 on absolutely pristine install
(first action).
make.log attached
Video card: Radeon HD 2400 XT
Dual monitors side-by-side
CPU: Intel Core 2-duo
Dell Optiplex 755
Radeon driver scrambles grub startup screen, so thought I would try A
Yay, fixed for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1199403
Title:
Xorg crash
To manage notifications about this bug go to:
https://bugs.launchpad.ne
Samuele, do you have vmware-tools or open-vm-tools installed? I don't.
--
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/1199439
Title:
segfault in xorg-server during install of saucy 32bit
I wonder if this is the same crash that I experienced in LP: #1199403
--
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/1199439
Title:
segfault in xorg-server during install of saucy 32bits
Public bug reported:
Today's saucy update with reboot and X crashes when trying to display
the greeter. I see continual flashes from purple screen to black
console.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu5
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
U
** Branch linked: lp:ubuntu/precise/xf86-input-wacom
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/573275
Title:
tc1100 stylus buttons regression
To manage notifications about this
** Changed in: xf86-input-wacom (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/573275
Title:
tc1100 stylus buttons regression
To manage
Using LUbuntu Precise (12.04) on my TC1100.
Using the stock install, there is absolutely no response whatsoever from
the system when I trigger the three stylus buttons. Not when I cat
/dev/input/*, nor out of xev.
I manually applied the second wcmISDV4.c.patch file listed under patches
on the rig
I can't comment on whether it was fixed or not, but in Precise (xserver-
xorg-input-wacom), it doesn't work.
I've tried triggering all three buttons on my tc1100 while cat'ing
/dev/input/* and none of 'em so much as twitch.
--
You received this bug notification because you are a member of Ubuntu
I can confirm that the wacom stylus buttons do not work under 12.04.
xev does not display any captured data when the buttons are pressed.
I've also tried triggering the buttons while cat-ing /dev/input/event* -
None of them show any data coming from them.
--
You received this bug notification b
Public bug reported:
at the end of my screen i can see the end of the firfox windows ( of course )
but also at the top of my screen( No , im not just losing my sight :))
This is happing with all programs , just firefox is the best example , as seen
most offten.
I think it has to do with the wor
FWIW, the 3.6.0-030600rc4-generic kernel seems supremely unhappy. No
graphics at all.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1039157
Title:
vmwgfx kernel module not
On Sep 05, 2012, at 03:11 PM, Joseph Salisbury wrote:
>Was there a prior kernel version that did not have this issue?
Yes, but I can't remember exactly which version this broke on. It definitely
worked all through 12.04 and in 12.10 up until whatever upgrade I happened to
do on-or-about 2012-08-
Hi Tim,
On Sep 05, 2012, at 04:54 PM, Tim Gardner wrote:
>Barry - its not clear if the attached kern.log in comment #11 is after
>you've added vmwgfx to /etc/modules. At any rate, that module is getting
>loaded about 20 seconds into the boot:
>
>[ 20.863814] [drm] Init
** Summary changed:
- X problems in Fusion guest
+ vmwgfx kernel module not loaded by default
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1039157
Title:
vmwgfx kernel mo
So, with Prf_Jakob's help, I added vmwgfx to /etc/modules and rebooted.
That gave me 3d, no tiny fonts on lightdm, and no llvmpipe based
corruptions. So that's a great workaround, but why isn't vmwgfx being
loaded automatically?
% grep -i 3d /var/log/Xorg.0.log
[ 8.737] (II) vmware(0): Galliu
Hi Robert, 3.5.0-10 exhibits the same problems.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1039157
Title:
X problems in Fusion guest
To manage notifications about this
** Attachment added: "dmsg.txt"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1039157/+attachment/3269687/+files/dmsg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://
Files attached as requested.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1039157
Title:
X problems in Fusion guest
To manage notifications about this bug go to:
https://
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1039157/+attachment/3269686/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://
Now, I went back and ran vmware-install.pl and it seemed to build,
however I got this message:
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
A reboot still gives me the tiny fonts, although the text is a bit more
readable.
As an intermediate step, according to this page
https://help.ubuntu.com/community/VMware/Tools I installed the open-vm-
tools package. That seemed to go okay, but it still doesn't look like
I'm using 3D:
grep -i open /tmp/glxinfo.txt
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Ga
Until the update which broke this, it definitely *felt* like I had 3D
working. Various animations and most noticeably Gnome Do, but it's
definitely not working now. Disabling 3D acceleration in Fusion and
restarting the guest shows the same corruption, tiny font problem, etc.
So I think you're ri
1 - 100 of 144 matches
Mail list logo
