Thanks for looking so quickly. I'm almost certain the problem will go
away without the nvidia driver because the nouveau driver didn't
recognise the hardware when I booted off the USB installer, so reverse
prime won't work and there will be no external monitor, which is a
completely new problem.
Public bug reported:
With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the
laptop display) and an external monitor connected via the nvidia card on
a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with
no apps running.
If I put the laptop in discrete
Could this be the problem described here:
https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen-
on-external-outputs-in-hybrid-graphics-mode/157800
ie (and this is the case if the external display is connected to the
NVIDIA card):
"Using amdgpu as a display offload source is
Public bug reported:
When I press the screen backlight up/down buttons, gnome-shell pops up
the backlight control window saying that the backlight is being
adjusted, but the actual screen brightness does not change.
The problem is that gnome is adjusting
** Also affects: libglvnd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1768390
Title:
BadMatch error in X_GLXSwapBuffers running
I had this problem, too. journalctl -b|grep glamor showed this:
/usr/lib/gdm3/gdm-x-session[2205]: (EE) modeset(0): glamor
initialization failed
which is why gnome-shell was falling back to llvmpipe. However, there
was some funny business going on with my libGL installation, because ldd
*** This bug is a duplicate of bug 1704765 ***
https://bugs.launchpad.net/bugs/1704765
Are you sure this is a duplicate? The other bug is about specifically
about dragging from the desktop to nautilus, and some people report it
happening in X as well as in Wayland. This bug only occurs in
The bug isn't in X server, but is related to EGL graphics drivers being
installed incorrectly by ubiquity.
** Package changed: xorg-server (Ubuntu) => ubiquity (Ubuntu)
** Summary changed:
- wayland session in Ubuntu 18.04 chooses LLVMpipe software driver on hybrid
graphics system
+
FWIW, removing libglvnd0 fixed the problem (libegl1 does depend on it,
but it isn't installed in artful either - libegl1-mesa is).
So the bug is actually:
a) the upgrade from artful to bionic installed libglvnd0 and libegl1
when they aren't needed;
b) having libglvnd0/libegl1 installed breaks
One difference between artful and bionic is that bionic has libglvnd0
installed (and libegl1 depends on it, so I can't really remove it).
Artful doesn't have it installed. I read in one bug report (for Arch or
Fedora? I can't find it now) with similar symptoms (ie no wayland
session) that libglvnd
I tried purging nvidia and bumblebee and reinstalling all the libs that
I could find related to GL, eGL, and mesa, but gdm3 still starts using
llvmpipe and the VMWare driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
And I only saw your feedback after I put my last comment in... :O
The lspci -k command run from artful shows this:
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev
ff)
Kernel modules: nvidiafb, nouveau, nvidia_387_drm, nvidia_387
I've got all those
Public bug reported:
In a gnome-shell Wayland session:
1. Open nautilus.
2. Open geeqie and navigate to a folder with images, ensuring that the
dire.
3. Try to drag a file from the directory list on the left to the
nautilus window.
Expected result: the file is copied to the folder in the
Actually, it's still not quite perfect in gimp even with version 3.2,
eg:
* Open an image
* Select eg the rectangle select tool
* Select an area with the stylus
* At this point, the mouse usually doesn't work any more - eg try and select an
area with the mouse or try and select another tool
Marvellous, that new version fixes a couple of issues in gimp - right-
click drag using the stylus now scrolls, both the mouse and stylus
cursor change to the selected tool now, and the mouse now works after
using the stylus without having to click on another xwayland app first.
I guess I should
Also, on wayland apps, the tablet stylus' right click works in the
menubar but not the window contents. So if I right-click on gnome-
terminal's menubar, I get the window menu, as expected, but if I right-
click inside the window, nothing happens (I should instead see the
window menu).
I imagine
Cool, the tablet works great now using that test version on Xwayland
apps like gimp and firefox and chrome.
It's not quite perfect yet - drag doesn't work with Wayland apps. Using
the tablet stylus, I can drag a chrome or firefox window by its menubar,
but not nautilus or gnome-terminal. And
Just for fun, I tried applying the 9 patches I found against the
xwayland source package and building/installing it (./configure, make,
and sudo make install, as per the INSTALL file), but I don't think it
installs properly, because "which Xwayland" says
"/usr/local/bin/Xwayland", as it should,
I'm happy to test any patches for you if you can't find your tablet!
--
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/1712571
Title:
xwayland does not support wacom tablets
To manage
Public bug reported:
When running a session under Wayland, my Wacom tablet does not work
properly in applications using xwayland (the cursor moves, but clicking
does not work).
This is a known issue that apparently has been fixed in xorg-server 1.20
branch - see the upstream bug at
Is this a modesetting driver issue? I believe I've seen this happen when
hotplugging an external monitor. It only happens for me with the modeset
driver, though, not the intel driver. The modesetting driver is
excellent for some things (eg it doesn't tear on the external monitor
like the intel
I don't see this any more in 4.8-0 final.
--
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/1615540
Title:
Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in
OsAbort()
To
So I can confirm that adding the extra modeline works, eg I now have
2560x1440@60 Hz both appearing in xrandr and working on the laptop
monitor using the modeset driver.
(There's a separate bug for the modeset driver whereby if you change the
mode, eg from 1920x1080 to 2560x1440, the new screen
Ok, thanks for the info re dpkg-buildpackage.
xf86DefModeSet.c is created by hw/xfree86/common/modeline2c.awk. If you
run dpkg-buildpackage, you'll find it two places:
$ find -name xf86DefModeSet.c
./build-main/hw/xfree86/common/xf86DefModeSet.c
./build-udeb/hw/xfree86/common/xf86DefModeSet.c
>From https://bugs.freedesktop.org/show_bug.cgi?id=97163#c15, I think
it's just a matter of some modelines missing from the xf86DefaultModes
array in xf86DefModeSet.c, eg I suspect that adding this:
/* 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz */
{MODEPREFIX,
No, the issue didn't occur in Xenial, which defaults to the intel
driver. (The intel driver doesn't have these issues.)
Just to be clear - it is possible that the issue is resolved with the
later BIOS, but I won't know until I can test the known bad
configuration again. (Unfortunately, I can't
The output of those commands are: 1.2.13 and 08/08/2016.
I can't test the same configuration that I originally tested for another
week, but on another 1680x1050 monitor it did work, eventually. I had to
restart lightdm several times because things happened like the mouse
click no longer working,
Just a note that I still get this occasionally in Ubuntu 16.04 and
16.10, usually after moving to a new series of the nvidia driver, and my
case the problem is that nvidia overwrites the
/usr/lib/xorg/modules/extensions/libglx.so and /usr/lib/x86_64-linux-
gnu/libGL.so files (eg "ldd
Just FYI, I proposed a patch at
https://bugs.freedesktop.org/show_bug.cgi?id=97163. I can't test it
beyond checking it compiles without warnings because when I built my own
xserver xorg-server_1.18.4 and installed it to the default prefix
(/usr/local/bin), X crashed. This was without any changes
Public bug reported:
I have an external 1920x1080 monitor attached to my laptop, which has a
3840x2160 display. When I run them both at their native resolutions, the
laptop display only works in the top quarter of the desktop, except for
the unity launcher and unity top bar. Anything that leaves
I don't think this is a duplicate of
https://bugs.launchpad.net/bugs/1543192. Although it triggers a crash at
the same point, the underlying cause of this bug is an incompatibility
between the modesetting driver and kernel 3.8-rc3. (Unless the
underlying bug is in the kernel and it triggers the
Is that the right place? The modesetting driver is incorporated into
xserver now, so the versions it offers to report against are very old.
I reported it anyway (against git) at
https://bugs.freedesktop.org/show_bug.cgi?id=97163, in case it helps.
** Bug watch added: freedesktop.org Bugzilla
Thanks for the info.
So it turns out that the problem is that the modesetting driver is
pruning these modelines because it thinks their vertical refresh is
greater than the max vrefresh.
The function in question is
hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(), and it
is
Another Ubuntu Perthian! Excellent! I checked another laptop and the
kernel only listed the native resolution of the screen on that as well,
so perhaps the issue is in xserver/modeset after all. But out of
curiosity, what role is the kernel supposed to take here? It does list
all the modes for my
The output is the same for the 4.7.0 kernel.
--
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/1606103
Title:
modeset driver does not detect all screen resolutions
To manage notifications
This is the output for kernel 4.6.4-040604-generic (running back on
Ubuntu 16.04, but I guess that shouldn't make any difference if we're
just reading the kernel info):
/sys/class/drm/card0-eDP-1/modes:3840x2160
(There's a bunch of other modes but they are all for the various
resolutions on the
To clarify my comment about 'ubuntu-bug xorg-server' not working, I had
to do 'ubuntu-bug xorg-server-source', although it seems to have
actually reported it against xorg-server in the end.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
My laptop's 4K screen (Dell XPS 15 9550) has these resolutions,
according to the intel driver:
3840x2160 60.00 +
3200x1800 60.00
2880x1620 60.00
2560x1440 60.00*
2048x1536 60.00
1920x1440 60.00
1856x1392 60.01
1792x1344
@madbiologist: thanks for looking into it. I haven't upgraded to the A12
BIOS because the list of fixes and enhancements was very small and only
mentioned it was a fix for some issues when upgrading to Windows 8.
(Additionally, Dell doesn't provide a way to update the BIOS from Linux
for this
** This bug is no longer a duplicate of bug 1246013
Would be nice for libgl1-mesa-dev to be multiarched
--
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/949606
Title:
64 bit dev packages
The bug doesn't impact the default configuration, the
solution/workaround is easy don't bind scroll events to workspaces
changes...
Sorry, but I don't understand what you mean by that: do you mean there
is an easy solution/workaround that a user can apply? Or that because
the solution is easy it
IMHO, this is quite an annoying regression.
Just in case it's not obvious what the effect is, there are steps to
reproduce it at
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1240957: you just
have to run two apps like gnome-terminal and nautilus and try using the
mouse wheel to scroll
IMHO, this is quite an annoying regression.
Just in case it's not obvious what the effect is, there are steps to
reproduce it at
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1240957: you just
have to run two apps like gnome-terminal and nautilus and try using the
mouse wheel to scroll
IMHO, this is quite an annoying regression.
Just in case it's not obvious what the effect is, there are steps to
reproduce it at
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1240957: you just
have to run two apps like gnome-terminal and nautilus and try using the
mouse wheel to scroll
IMHO, this is quite an annoying regression.
Just in case it's not obvious what the effect is, there are steps to
reproduce it at
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1240957: you just
have to run two apps like gnome-terminal and nautilus and try using the
mouse wheel to scroll
Public bug reported:
I upgraded to 13.04 now when I suspend, it will not recover. It locks up
and I have to do a hard boot.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
I've seen it happen with kernel 3.8-rc2 and SNA using the latest intel
driver from git.
The hang isn't always the same:
* Sometimes it locks the computer up completely, requiring a hard
reboot.
* Sometimes it locks X, but CTRL-ALT-F1 and back unlocks it.
* Sometimes it resolves itself without
fwiw, I just ran into the fubar keyboard problem with vmplayer 5.0.1 in
Ubuntu 12.10, but found a workaround. Every single time that my mouse
went into the vmplayer window, vmplayer trashed all the modifier keys so
that CTRL, SHIFT, ALT all stopped working. xmodmap showed:
shift
lock
I found a workaround for my problem - it was an xmodmap setting that
vmplayer didn't handle properly and was trashing. In case it is of
interest, I posted the workaround at
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/195982/comments/226.
--
You received this bug notification
I'm going to guess that is related: I find with vmwareplayer v5.0.1
build-894247 in Ubuntu 12.10 that as soon as I move the mouse over a
vmwareplayer window and back again, it breaks the keyboard mapping in
Unity and gnome-shell. In both unity and gnome-shell, CTRL stops working
altogether; in
Yes, I've been running v2.20.14 from git (using SNA, not UXA) for a few
days on Quantal and so far I hasn't seen that other bug I mentioned - it
hasn't fatally locked up after the screensaver kicks in. However, it has
experienced *this* particular bug a few times, ie where the screen locks
but I
I still experience this bug, even with the latest intel driver from git,
xf86-video-intel-2.6.99.902. I would use SNA but it has an even more
annoying bug after the screen saver unlocks where unity just shows me a
black screen and mouse cursor, and I have to physically restart unity to
get it
I have found that the 304.51 driver mostly fixes the issue for me,
unless I run the 3d application from a btrfs partition (which does seem
odd, but there you go).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
304.51 is the least crashy version for me. It was really easy to
reproduce the crash with both 304.43 and 304.48, but on 304.51 it only
happens occasionally.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
@Dmitrijs: To find which method is being used, do:
grep AccelMethod /var/log/Xorg.0.log
I find also that the titlebars of non-focused windows are often light
grey instead of black when using SNA.
And to change methods, put this in your xorg.conf to set the
acceleration method and then restart
Forcing a revert to the 304.43 driver breaks things for me, because
304.51 has a fix that stops the nvidia driver crashing the kernel so
frequently. Isn't modifying xorg.conf a better solution than forcing a
revert?
--
You received this bug notification because you are a member of Ubuntu-X,
I've been using SNA for a couple of weeks now, and it doesn't seem to
suffer from this particular bug.
The bug still occurs in the latest xf86-video-intel driver from git (as
of 27/9/12), though. It generally occurs when focus changes, eg when a
menu or popup window is opening.
--
You received
Ah, I am using xorg-edgers. Perhaps they are trying out SNA as the
default there.
--
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/1041790
Title:
[sandybridge-m-gt2] GPU
Yes, I think the bug doesn't happen with SNA whereas it occurs pretty
regularly with UXA. I've been using SNA for a couple of days now since
it became the default on my system. Does X now look for other xorg.conf
files? I created one called /etc/X11/xorg.conf-intel-sna and symlinked
to it to test
Is SNA turned on by default now? I had a couple of hours freeze-free
with it the other day, but removed my xorg.conf shortly afterwards
because the white titlebars and glitchy 3D graphics were annoying, and
also because with SNA enabled the backlight didn't come on after the
screensaver turned it
Yes, you're right, those NVRM messages are fine - they just say that the
driver found a couple of nvidia GPUs. I was wondering if you were
getting Xid errors or the 'attempted to yield the CPU in atomic mode'
mentioned earlier in the thread. Your issue might still be an nvidia
problem - if the
OK, it is fixed now in nvidia-current 304.43-0ubuntu2.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Fix Committed = New
--
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/1043054
Title:
nvidia-current
For me, the nvidia drivers have been getting progressively more likely
to crash with each release. 304.43 is the worst nvidia driver yet. It
used to be only one 3d app that reliably crashed it, but now it crashes
quickly even with 3d apps that ran OK with previous versions of the
driver. And
This isn't a duplicate of #1037483, which is about Precise. This bug is
about Quantal.
However, 304.43 does build correctly on my Quantal system (and on
novak's), so this bug does appear to be fixed.
** This bug is no longer a duplicate of bug 1037483
Needs NVIDIA driver 304.43
** Changed
For me, the nvidia 304.43 driver still crashes X with Xid errors,
'attempted to yield the CPU while atomic', and 'GPU has fallen off the
bus' errors all appearing in the syslog. So it isn't fixed here.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
nvidia-current v304.43-0ubuntu1 fails to build because nvidia have added
a macro NV_ACPI_OS_WAIT_EVENTS_COMPLETE that takes the 3.6 kernel into
account already. So buildfix_kernel_3.6.patch fails to apply when you
try to install nvidia-current v304.43-0ubuntu1.
Since the
But I don't want to install xorg-edgers. I have built the module by
applying the fix to dkms.conf.
Have you actually committed the fix to dkms in the nvidia-graphics-
drivers package? When will the fixed version of nvidia-current come out?
--
You received this bug notification because you are a
Public bug reported:
X locks up periodically for a 2 to ten seconds at a time and this crash
log gets generated. It's significantly more than several times a day but
not quite continuous.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
Uname:
--
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/1041790
Title:
[sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
To manage notifications about this bug go
** Changed in: nvidia-drivers-ubuntu
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1032672
Title:
fglrx-updates broken dependency with
OK, with the new Xserver 1.12.99.905-0ubuntu2, nvidia-current 304.37
does load OK, at least for bumblebee. I was keen to try it out to see if
it would crash with the Attempted to yield the CPU while in atomic or
interrupt context that plagued it in Precise while playing opengl
games. Sadly, it
Public bug reported:
nvidia-current 304.32 and 304.37 currently fail to build with xserver-
xorg-core 2:1.12.99.905-0ubuntu2 installed because they depend on xorg-
video-abi-11 or 12.
As noted in the comment, commenting out this VIDEODEP= line in
debian/rules fixes the problem:
# Comment out
For the nvidia-graphics-drivers package, commenting out this VIDEODEP
line in debian/rules fixes the problem:
# Comment out the following line to re-enable automatic ABI detection
VIDEODEP = xorg-video-abi-11|xorg-video-abi-12|xorg-video-abi-13,
xserver-xorg-core (= 2:1.11.99.901)
--
You
See also bug #1032672, which is about a similar problem in fglrx, but
some people with nvidia cards have also reported this issue there.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I have reported this issue for nvidia-graphics-drivers in bug #1041652,
since this bug is about fglrx.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1032672
Title:
fglrx-updates
Is the bug actually in the nvidia driver or in the xserver? X has now
applied the ABI bump (http://lists.x.org/archives/xorg-
announce/2012-August/002059.html) with the patch that Aaron requested
pertaining to this crash, and xserver-xorg-core is now at
2:1.12.99.905-0ubuntu1 so it should have the
I just tried 304.37 and it doesn't fix X crashing for me. My test case
is running a game using bumblebee until the GPU has fallen off the bus
problem occurs. With 304.37, I didn't get the GPU has fallen off the
bus error in the log, but video output froze and when I tried to
terminate the process,
I still see the problem with mesa 8.0.3:
Polygons in scene: 62464
Visual ID of window: 0xbd
Context is Direct
OpenGL Renderer: Mesa DRI Intel(R) Sandybridge Mobile
2.389327 frames/sec - 2.666489 Mpixels/sec
1.590925 frames/sec - 1.775473 Mpixels/sec
1.599480 frames/sec - 1.785020 Mpixels/sec
--
** Description changed:
When I run google-earth 6.2.1.6014-r0 using the Sandy Bridge GPU, X
freezes while zooming in on a location. For instance this happens when I
type 'Caversham WA' into the Google Earth search: X freezes about half-
way through the animation.
+
+ Workarounds are:
+
See the upstream bug mentioned in the commit. In
https://bugs.freedesktop.org/show_bug.cgi?id=47535#c14 it says Linus
merged the patch into the upstream kernel, and Greg picked it up for 3.3
stable. Hopefully should be landing in a distro near you. :), which
might not help 3.2, of course.
I just
It looks like this is a kernel issue rather than a xserver issue, as
kernel commit 3a69ddd6f872180b6f61fda87152b37202118fbc fixes the problem
for me:
commit 3a69ddd6f872180b6f61fda87152b37202118fbc
Author: Kenneth Graunke kenn...@whitecape.org
Date: Fri Apr 27 12:44:41 2012 -0700
drm/i915:
The attached patch stops the crash with the 3.2.16 kernel, so it should
work with the Ubuntu 3.2 kernel as well.
** Patch added: patch for 3.2
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/975689/+attachment/3114281/+files/fix-intel-gpu-crash-3.2.diff
--
You
Here's a log of dmesg, Xorg.0.conf, and i915_error_state while X was
frozen.
The system did actually recover partially after a minute this time.
Unity crashed (I guess because the 3d acceleration was disabled when the
GPU lockup was detected) so all I could do was reboot via a tty console.
**
Public bug reported:
When I run google-earth 6.2.1.6014-r0 using the Sandy Bridge GPU, X
freezes while zooming in on a location. For instance this happens when I
type 'Caversham WA' into the Google Earth search: X freezes about half-
way through the animation.
This happens in Unity, Unity2d, or
** Attachment added: Xorg.0-crash.log
https://bugs.launchpad.net/bugs/975689/+attachment/3020276/+files/Xorg.0-crash.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
This also looks like a duplicate of bug #944627.
(Also, for the record, glxspheres is not made specifically for bumblebee
- it is bundled with VirtualGL.)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
This looks like a duplicate of bug #944627.
It is most definitely a problem when just running the intel driver as
well as when running the nvidia driver. However, the intel driver
performs at least 20 times more slowly compared to Ubuntu 11.10 (on my
PC right now it is running over a hundred
The problem is that the patch doesn't allow for any acceleration or
clipping that X normally supplies, so it is unlikely to be committed.
If you are having trouble building wine on ubuntu 12.04, there are some
workarounds you can try that I detailed in
FYI, I uploaded a patch for wine
(http://bugs.winehq.org/attachment.cgi?id=39256) that either fixes it
(if XI2 is intentionally returning absolute values) or works around the
problem (if it's a regression in xserver).
--
You received this bug notification because you are a member of Ubuntu-X,
@Aaron: Thanks for the feedback. Is there a way to help with debugging?
I submitted bug reports to the nvidia forums on two occasions
(http://www.nvnews.net/vbulletin/showthread.php?t=167848#post2495268
from October and
http://www.nvnews.net/vbulletin/showthread.php?t=163468#post2444989 from
@Aaron: do you by any chance know of documentation that describes the
Xid errors from the nvidia driver? It seems that many people have the
driver crash with a Xid 13 error (and subsequently the GPU falls off the
bus, which crashes the kernel and requires a hard reset), but I can't
find (ie
So the conflicts with have just been incorrectly set - it's not just
because the i386 and amd64 packages supply the same files and therefore
overwrite each other (and purging one of them will affect the other)?
There are a number of packages that fall into this category: is it
something that can
This program illustrates the problem, displaying a window and the output
results (to compile, use: gcc rawmotion.c -o rawmotion -lX11 -lXi).
In xserver 1.11, the raw_values it displays are relative and the
valuators.values are absolute. In xserver 1.10, the two streams are both
relative.
**
--
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/949606
Title:
64 bit dev packages should include 32 bit .so library file
To manage notifications about this bug go to:
Public bug reported:
64 bit dev packages contain a 64 bit version of the library file(s) that
they provide for linking but not a 32 bit version of the library
file(s). In previous versions of Ubuntu, however, it was possible to
compile 32 bit applications using the 64 bit dev packages in by
Some more research shows that the libglu1-mesa-dev package doesn't
include the file /usr/lib/i386-linux-gnu/libGLU.so. Since it conflicts
with the i386 package, shouldn't it include this file also if it is to
include the required 32 bit dev files?
As a workaround, if I have the libglu1-mesa:i386
Additionally regarding the missing packages, I checked a fresh install
of 12.04 in VirtualBox and even though multiarch is enabled and Synaptic
shows a bunch of i386 files, some are missing, like libgl1-mesa-
dev:i386. It seems that the missing packages is a general problem. So is
this worth
So where should wine get the 32 bit GLU dev libraries from?
Normally I'd expect it to be able to install libglu1-mesa-dev:i386 for
this, but a) it doesn't appear in the repositories, and b) it conflicts
with libglu1-mesa-dev.
** Package changed: ia32-libs (Ubuntu) = mesa (Ubuntu)
--
You
Can I add an affects mesa to this bug with a new status? The core
problem remains, which is that Precise does not provide 32-bit GLU dev
libraries on an amd64 platform. Or should I open another bug?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
1 - 100 of 183 matches
Mail list logo
