There is also a bug filed in 2015 about the same problem, with a barrage
of recent comments from 18.04 users:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146
I hesitate to mark this a duplicate though, since the 2015 bug is not
necessarily the same.
--
You received this bug
I found a discussion of this bug at
https://askubuntu.com/questions/886593/alt-f4-switches-to-tty4 and a
workaround (kbd_mode -s). No clue to what gets it in the wrong mode to
begin with, though.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Recently the VT switching shortcut keys changed from ctrl+alt+arrowkeys
and ctrl+alt+F-keys to just alt+arrowkeys/f-keys. This conflicts with
many application keybindings, such as Firefox history back/forward.
I don't know which package is to blame, xorg-server is my best
The rest of the functionality works after installing v3.9-rc3-raring
from kernel-ppa. It didn't really work properly in Qt either with the
earlier version, it didn't pass through click events properly to Qt
apps.
--
You received this bug notification because you are a member of Ubuntu-X,
which
Oh, the v3.9-rc4-raring test I did was with quantal.
--
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/1119395
Title:
Touchscree doesn't work on Fujitsu Stylistic Q702
To manage notifications
checked older versions: fingerpaint demo doesn't work in precise, does
work in quantal.
--
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/1119395
Title:
Touchscree doesn't work on Fujitsu
Public bug reported:
Funnily the touchscreen accepts one gesture after boot (drawing the selection
rect on the desktop). Nothing after that.
I don't know if this is through some mouse emulation or if the N-Trig DuoSense
handles both touchpad and touchscreen,
or if the unrecognised input device
Same happens after upgrading to current alpha version of raring. I get
the one touch swipe after reboot.
After looking at xorg log more closely it appears the DuoSense is recognised as
touchscreen and the unknown hid is
recognised as mouse:
[ 3.434] (II) XINPUT: Adding extended input device
Actually it seems this is just some kind of unity bug. Installing libqt4-demos
and running the fingerpaint example
results in perfectly working multitouch!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Ok I have verified that my local fix works, this ErrorF triggers in the
beginning of AttendClient:
void
AttendClient (ClientPtr client)
{
OsCommPtr oc = (OsCommPtr)client-osPrivate;
int connection;
if (!oc) {
ErrorF(osPrivate NULL in AttendClient!);
return;
}
I had
Now I can't reproduce the GPU process crash after restarting, all the
WebGL examples work fine.
I'll open up a new bug with a gdb stack trace of the GPU process if I
get a reproducible crash again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Because it doesn't work with Chrome, like reported in comment #7. It's the same
way on Precise with Chrome + Mesa,
the GPU process crashes. I don't know why it crashes on Chrome but works with
Firefox and Chromium.
There aren't separate WebGL implementations for different video cards in
Chromium is the open source project that Chrome is based on (it includes
further proprietary stuff and Google branding). The version of Chromium
in Precise (18.x) is older than what you get with Chrome from the Google
stable channel (22.x).
--
You received this bug notification because you are a
I was referring to Chrome 22.x from the stable channel. Old Chrome
versions are rare since they're only distributed by Google and are
automatically updated.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
This sounds a little circular. It doesn't work with Mesa - it's
blacklisted by google - not a bug because it's blacklisted?
FWIW it seems to work fine with Chromium from Precise after disabling
the blacklist. Wonder what's different.
--
You received this bug notification because you are a
Public bug reported:
I tried booting the 12.10 beta and touching the screen doesn't do anything.
This is working in my 12.04 install on this laptop.
Hardware is Fujitsu Lifebook T731.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-input-wacom 1:0.16.0+0git9f32b03-0ubuntu1
--
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/1049547
Title:
wacom touchscreen not detected
To manage notifications about this bug go to:
** Description changed:
- I tried booting the 12.10 beta and touching the screen doesn't do anything.
This is working in my 12.04 install on this laptop.
- Hardware is Fujitsu Lifebook T731.
+ I tried booting the 12.10 beta and touching the screen doesn't do
+ anything. This is working in my
This started happening frequently enough that I broke out the xorg sources and
figured out how to associate
the crash address to a line number. (*)
It's crashing at the line where it's dereferencing client-osPrivate, I'd guess
there's a missing null check of client-osPrivate at the start of
I would try a fix but I can't seem to work the build tools these days
(dpkg-source: unrepresentable changes to source, dpkg-source: info:
'dpkg-source --commit' is not supported by the source format '1.0')
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Another possible sighting: http://forum.ubuntu-fr.org/viewtopic.php?id=686861
(only redo_fr looks in his blog which has a similar backtrace, but other
radeon users (plikplok and Kaffee)
report same symptoms)
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
This has happened twice now, both times when machine was unattended and screen
was probably locked.
Looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=821628 including
the divisor 0 get vblank counter failed
warning preceding the crash.
So in Xorg log I get the
--
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/1033242
Title:
X server crashes
To manage notifications about this bug go to:
This still happens in Precise.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Expired = New
** Tags added: apport-collected compiz-0.9 precise running-unity ubuntu
** Description changed:
Binary package hint: xserver-xorg-video-ati
1) The release of Ubuntu you are using,
apport information
** Attachment added: BootLog.gz
https://bugs.launchpad.net/bugs/684591/+attachment/3241857/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241856/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241858/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241859/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241860/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241861/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241862/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241863/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: MonitorsGlobal.xml.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241864/+files/MonitorsGlobal.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: MonitorsUser.xml.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241865/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241866/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241867/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241868/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241869/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241870/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241871/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241872/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241873/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241874/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/684591/+attachment/3241875/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
bootchk: see comment #7, if you use the qt sdk you won't get the ubuntu code
(it's not in upstream yet). You want
to test with the ubuntu-provided qt (fingerpaint demo is in the qt4-demos
package).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I finally got around to following through the config hackery described at
http://www.murraytwins.com/blog/?p=103
(the trick was to remove the existing wacom .conf, i think i earlier just chmod
000'd it but Xorg was running as
root so read it anyway). And it worked, kind of. I got fingerpaint
Marking as confirmed since Brent Fox reproduced this already couple of
months ago.
--
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/901630
Title:
multitouch + qt doesn't work (eg
I now upgraded the laptop to 12.04 and the fingerpaint demo stopped working
even with Xorg.0.log showing
it's using evdev.
--
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/901630
With the N-trig touchscreen (#724831) the Qt fingerpaint demo works with fine
1-5 fingers. So the wacom
touchscreen support should be fixed to handle that as well.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
I got Qt multitouch working on another laptop after a driver fix (see
#724831), so Qt isn't the problem.
--
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/901630
Title:
multitouch + qt
Looks like the wacom driver just converts the touch gestures (eg pinch)
to scroll wheel events, so it's not Qt's fault.
** Package changed: qt4-x11 (Ubuntu) = xf86-input-wacom (Ubuntu)
** Summary changed:
- multitouch + qt doesn't work (eg fingerpaint demo)
+ multitouch + qt doesn't work (eg
Chromium gpu blacklist seems to have gained an entry for this:
{
blacklist: [ webgl ],
description: The Intel Mobile 945 Express family of chipsets is not
compatible with WebGL.,
device_id: [ 0x27AE ],
id: 4,
os: {
type: any
},
I haven't had the chance to try it yet, and I might skip Natty. I didn't
realise I had to respond in order to keep this from expiring. I imagine
the supported until April 2012 in the about dialog means bugs are
still tracked for Maverick?
** Changed in: xserver-xorg-video-ati (Ubuntu)
confirmed by Adam so marking confirmed.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/685321
Title:
webgl doesn't work with chrome
___
Mailing list:
This should be assumed broken in natty unless proven otherwise, since googling
about the problem yields similar reports from over
the years. In fact since iTux chimed in, I'm marking this confirmed. (I'm not
planning to update the machine in question to natty
in the near future).
** Changed
Public bug reported:
Binary package hint: xserver-xorg-video-ati
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
- About Ubuntu.
You are using Ubuntu 10.10
- the Maverick Meerkat - released in October 2010 and supported
until April 2012
2) The version
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/685321
Title:
webgl doesn't work with chrome
___
Mailing list:
Public bug reported:
Binary package hint: xserver-xorg-video-ati
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
- About Ubuntu.
You are using Ubuntu 10.10
- the Maverick Meerkat - released in October 2010 and supported
until April 2012.
2) The version
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/684591
Title:
vga monitor not detected
___
Mailing list:
Public bug reported:
Binary package hint: xorg
xev says my copy and paste keys are generating XF86Copy and XF86Paste as
they should, but they don't do anything in terminal or gnome apps.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu
--
copy and paste keys do nothing
https://bugs.launchpad.net/bugs/683694
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Google published some webgl demos for chromium, but they all hang on gm45. They
work on my
work machine (lucid + nvidia proprietary drivers).
steps to reproduce:
1. get chromium from daily ppa (apt-add-repository
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/655279/+attachment/1673633/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/655279/+attachment/1673634/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Machine freezes on login with Naali. Adding more in additional comment
since launchpad just ate my first writeup (internal error after clicking
submit, back button shows empty report form).
ProblemType: Bug
DistroRelease: Ubuntu
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/645281/+attachment/1622899/+files/Dependencies.txt
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/645281/+attachment/1622900/+files/RelatedPackageVersions.txt
--
lucid + gm45 freeze
(reporting against xserver-xorg-video-intel since using ubuntu-bugon
linux first refused to generate report while intel-drm-next kernel was
installed, and then after i removed it, it crashed on a dangling vmlinuz
link).
so, steps to reproduce on lucid;
* check out and build naali (git clone
67 matches
Mail list logo
