This seems to work for me.
X.Org version: 1.17.2
resolution:100x100 dots per inch
Actual resolution seems to be more like 109 dpi but it's certainly not
fixed at 96.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
htt
seems upstream is still broken and ubuntu has not patched this
--
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.launchpad.net/bugs/1039523
Title:
Mouse Scroll Wheel not working in spice vm guests
Patch has been posted here and on the xorg-devel list.
Feel free to rebase/resend/nag somebody with commit access until it's
applied.
--
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/589485
Was this fixed already?
There is a multitude of patches but bug is still marked as new.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vesa in Ubuntu.
https://bugs.launchpad.net/bugs/531736
Title:
VESA driver should fail t
actually, the X server starts in some ridiculously small resolution in
which gm screen is shown but when I log in the screen resolution is
changed to the highest
** Summary changed:
- X server starts in ridiculously high resolution
+ X session starts in ridiculously high resolution
** Package ch
They do in fact work but they conflict with the existing ubuntu patches
and dpkg-buildpackage somehow 'solved' the conflict by not applying the
patches.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283980/+files/ProcModules.txt
--
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
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283976/+files/DpkgLog.txt
--
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.launchpad.n
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283983/+files/XorgLog.txt
--
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.launchpad.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283978/+files/ProcCpuinfo.txt
--
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
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283979/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bu
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283984/+files/XorgLogOld.txt
--
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.launc
apport information
** Attachment added: "xinput.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283986/+files/xinput.txt
--
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.launchpad.net/
apport information
** Attachment added: "peripherals.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283985/+files/peripherals.txt
--
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
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283975/+files/Dependencies.txt
--
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.l
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283972/+files/BootDmesg.txt
--
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.launchp
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283974/+files/CurrentDmesg.txt
--
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.l
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283981/+files/UdevDb.txt
--
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.launchpad.net/
apport information
** Attachment added: "BootLog.gz"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283973/+files/BootLog.gz
--
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.launchpad.net/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283982/+files/UdevLog.txt
--
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.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1039523/+attachment/3283977/+files/Lspci.txt
--
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.launchpad.net/bu
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
DistUpgraded: 2012-08-30 11:28:54,407 DEBUG enabling apt cron job
DistroCodename: precise
DistroRelease: Ubuntu 12.04
DistroVariant: ubuntu
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
Bus 001 Device 002: ID 0
The redhat patches do not work for me athough they are supposed to
address exactly this problem.
** Tags added: apport-collected referred-by-support running-unity ubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in
--
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/1043742
Title:
X server starts in ridiculously high resolution
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
** Description changed:
I don't know if the vmware graphics communicates the real size of the
window in which the virtual machine runs.
However, in absence of such information (or failing to communicate it)
- starting in full HD or what is not a good default.
+ starting in 2360x1770 not a
Public bug reported:
I don't know if the vmware graphics communicates the real size of the
window in which the virtual machine runs.
However, in absence of such information (or failing to communicate it)
starting in full HD or what is not a good default.
ProblemType: Bug
DistroRelease: Ubuntu 12
However you look at it this is a bug.
Xorg changed from working to bogus and broken behaviour.
--
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/521877
Title:
[gm45] wrong scre
(In reply to comment #66)
> Okay, I meant to post this a while ago and forgot, but the recent churn has
> reminded me to do so. I'll start with the tl;dr:
>
> I don't think this bug matters anymore.
>
> It's been over a year since this bug was opened, and during that time I've
> come to the conc
Guess this is an invite to leave for Wayland or whatever. My current
screen is 96 dpi (give or take a pixel) so I could care less but the
moment I switch to a display with different resolution I will have to
put up with this Xorg's insanity as well.
If Xorg is going to be bug-compatible with Windo
Xorg reports wrong screen size by design. See bug 23705
--
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/201491
Title:
Screen DPI detected incorrectly by xdpyinfo
To manage notifications a
Isn't the issue here that the emulated card has too low video memory
forcing 800x600 when the driver selects the default 24bpp depth?
This is an issue with some very old real hardware too.
I guess X could account for that but due to its architecture every
driver would likely have a separate check
apport information
** Tags added: apport-collected
** Description changed:
To reproduce:
Connect tablet.
Press the first pad button above a terminal.
Moving the cursor now changes selection as if the button was down
although it is up.
ProblemType: Bug
DistroRelease: Ubu
I am still getting stuck buttons sometimes so this has improved but is
not fixed completely.
--
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/843681
Title:
tablet pad buttons stuck
To
** Attachment added: "xsetwacom properties"
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/843681/+attachment/2366427/+files/pad-xset
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.la
** Attachment added: "xinput properties"
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/843681/+attachment/2366411/+files/pad-props
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.laun
⎡ Virtual core pointer id=2[master pointer
(3)]
⎜ ↳ Wacom Bamboo eraser id=13 [slave pointer (2)]
⎜ ↳ Wacom Bamboo cursor id=14 [slave pointer (2)]
⎜ ↳ Wacom Bamboo pad id=15 [slave p
Public bug reported:
To reproduce:
Connect tablet.
Press the first pad button above a terminal.
Moving the cursor now changes selection as if the button was down
although it is up.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-input-wacom 1:0.11.0-0ubuntu1
ProcVersionSigna
--
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/843681
Title:
tablet pad buttons stuck
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-inp
On 14 September 2010 21:28, rusivi1 <17...@bugs.launchpad.net> wrote:
> Thank you for posting this bug.
>
> Does this occur in Lucid?
>
I cannot tell, the PSU for the system broke and I don't have a
replacement.
--
cannot configure X for graphics card with 1MB ram
https://bugs.launchpad.net/bugs
yes, it's been fixed.
I forgot to CC the uploader, sorry about that,
** Changed in: mesa (Ubuntu)
Status: Invalid => Fix Released
--
[xorg-edgers] packaging needs update for r300g dri module rename
https://bugs.launchpad.net/bugs/626243
You received this bug notification because you are
What do you want to know about this issue that the report is marked
incomplete?
You only asked for irrelevant information so far.
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
[xorg-edgers] packaging needs update for r300g dri module rename
https://bugs.launchpad.net/bugs/626
This is not about driver failing but about packaging.
Applies to any r300 device and I have no Xorg.log because I did not
restart X, it's not needed to use the package.
--
[xorg-edgers] packaging needs update for r300g dri module rename
https://bugs.launchpad.net/bugs/626243
You received this bu
On 29 August 2010 14:01, Bryce Harrington <626...@bugs.launchpad.net> wrote:
> Hi Michal,
>
>
> Please attach the output of `lspci -vvnn` too.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> **
Public bug reported:
libgl1-mesa-dri 7.9.0~git20100827+gallium+r300
.fa2deb3d-0ubu
The r300g dri module has been renamed from radeong to r300.
Currently the dri directory has not r300 module, the dri-classic has
one.
Using the one from dri-classic results in OpenGL rende
I don't have the card at hand so I cannot easily re-test.
However, the card is not of some hybrid type ad it is detected
correctly, the X driver just fails to initialize it on some hardware.
--
GeForce 6200 - X server refuses to start
https://bugs.launchpad.net/bugs/370234
You received this bug
What you are seeing is different. For you no driver loads, and you
probably need an updated intel driver for that device.
For me the nv (or nvidia) driver loads but fails to drive the card.
--
GeForce 6200 - X server refuses to start
https://bugs.launchpad.net/bugs/370234
You received this bug
2009/8/1 Bryce Harrington :
> Since the hardware is no longer available for doing troubleshooting
> with, we'll have to close the bug for now. However please feel free to
> reopen if you or anyone else has the same HW and can reproduce this
> issue using the latest development version of Ubuntu an
2009/7/11 Tormod Volden :
> Michal, a quirk for your hw combination was now added upstream. You can
> find test packages at https://launchpad.net/~xorg-edgers/+archive
> /drivers-only
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Confirmed => Fix Committed
Unfortunately I cann
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/27093273/Xorg.0.log
--
CRT display not detected
https://bugs.launchpad.net/bugs/379803
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
Actually, the monitor has two inputs and DDC only works on the second
input, not the first.
Probably hardware issue with the monitor, and very confusing one.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invalid
--
CRT display not detected
https://bugs.launchpad.net/bugs/
Public bug reported:
Binary package hint: xserver-xorg-video-ati
The CRT display is configured in 1024x...@60hz
The display works normally with another card.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-ati 1:6.12.1-0ubuntu2
ProcEnviron:
LANG=en_US
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27093005/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/27093006/LsHal.txt
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/27093007/LsMod.txt
** Attachment added: "LsPc
I guess I got this filed under the wrong package. It is not really nv
specific.
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Incomplete => New
** Package changed: xserver-xorg-video-nv (Ubuntu) => xorg-server
(Ubuntu)
--
low graphics mode stomps on itself
https://bugs.launchpad.
** Bug watch added: freedesktop.org Bugzilla #12544
https://bugs.freedesktop.org/show_bug.cgi?id=12544
** Also affects: xserver-xorg-driver-ati via
https://bugs.freedesktop.org/show_bug.cgi?id=12544
Importance: Unknown
Status: Unknown
--
X locks up - wrong agp mode
https://bugs.l
54 matches
Mail list logo
