Public bug reported:
Apologies if I have misfiled this bug - this is a report of an issue
affecting Wayland in Ubuntu 24.04 beta.
Using 24.04 beta logging in with Wayland. Nautilus has very significant
performance issues. Doesn't happen when logging in with Xorg instead of
Wayland.
Opening
Following Timo's instructions, aptitude upgraded those two packages
(along with three additional packages aptitude auto-selected) on one
test system:
[UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 ->
22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libgbm1:amd64 22.2.5-0ubuntu0.1~22.04.2 ->
I can install nvidia-390 and it works on my Kubuntu 23.10 laptop
monitor, however the external monitor is not detected and does not work.
If I remove Nvidia 390 as well a bumblebee-NVIDIA, the external monitor
works without a problem.
--
You received this bug notification because you are a
OK just a question about pinning since we would prefer to minimize
changes to user systems. When we follow the instructions from Steve's
message on:
https://wiki.ubuntu.com/Testing/EnableProposed
which sets the pin priority for proposed to 400, the page says to run a
simulated apt upgrade to
Okay we'll wait for a later build.
--
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/2020604
Title:
After Mesa upgrades, Chrome won't show graphics
To manage notifications about this bug go to:
Thank you very much Steve (and Timo and everyone else that has helped).
We will test it on a few systems this weekend.
--
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/2020604
Title:
After Mesa
This hasn't happened to me in a while, so I think it is fixed, at least
when using the latest 515 Nvidia drivers.
--
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/1970808
Title:
[nvidia]
Yes, the mouse cursor does get frozen.
The bug occurred and I was able to ssh into the computer. I've attached
the results of `ps auxw` as you requested.
** Attachment added: "locked-screen-ps-auxw.txt"
Public bug reported:
See attached screenshot.
The corrupted text and images are only appearing in the Ubuntu desktop
environment (like the login screen, dock, and the bar at top of the
screen). Applications like Nautilus, the Terminal app, and Chrome are
not affected.
Maybe an Nvidia issue?
Sounds good — yes, I will try to ssh into it next time it happens.
--
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/1970808
Title:
[nvidia] Lock screen is frozen
To manage notifications
** Description changed:
I often have to forcibly power down my PC because of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the
most recent time I did that, when the computer restarted, the resolution
is stuck on 1024x768 even though I am on a 1920x1080
Public bug reported:
I often have to forcibly power down my PC because of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970808. Well, the
most recent time I did that, when the computer restarted, the resolution
is stuck on 1024x768 even though I am on a 1920x1080 monitor. I
The permanent fix described by
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1568604/comments/261 works for me.
sudo apt-get purge xserver-xorg-video-intel*
sudo reboot
Note the poster of this fix has a follow up comment about the broader video
driver removal also
After updating Ubuntu Budgie 20.10 today (5.8.0-44-generic #50-Ubuntu) I
notice this doesn't happen for me anymore. It is possible that it just
hasn't happened yet, but prior to today, I could reliably reproduce this
every time by resizing a window for a few seconds until flickering
started. I
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911219/+attachment/5453074/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
Also freezes when trying to open Libre Office new documents
Not sure if it is the video that is causing issues
Mouse and keyboard seems to be frozen and cant do anything without a
hard reboot
Some times the video keeps playing even if everything is frozen.
ProblemType:
I am also having a very similar problem on my Dell Inspiron 5390 runnin
ubuntu 20.04.1 LTS. The output from running xinput reads:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳
Public bug reported:
When resizing a window with the mouse by dragging the edge or corner,
the window begins to flicker. It only flickers when actively being
resized, and when I stop dragging, it looks normal. This behavior is
does not occur on same pc in 20.04.
ProblemType: Bug
DistroRelease:
*** This bug is a duplicate of bug 160264 ***
https://bugs.launchpad.net/bugs/160264
I have this exact bugg on Kubuntu 20.4 LTS.
It's not the same as #160264 as (like other people here) I get a black
screen, not a white one.
No response from any Fn+Fx keys, only fix is a hard boot.
--
You
Im having a similar problem. I have a ThinkPad T520, running xfce 4.12
on ubuntu 18.04.
I have tried this command with and without '--auto':
'xrandr --output LVDS-1 --auto --same-as DP-1-1'
Here is my xrandr output:
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
LVDS-1
I am using xfce 4.12 on Ubuntu 18.04 and am having a similar issue.
However, on startup, my laptop screen is mirrored on the intended
external monitor just before I reach lightdm. xrandr detects the monitor
however running 'xrandr --output <> --same-as <>' results in no effect
with no error
Public bug reported:
my home and login screen looks like i had taken LSD vivid distorted
colours. and just solid color on normal start-up.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux
Confirmed duplicate and working with the proposed version. Not sure how
I missed 1767559, sorry!
** Changed in: libinput (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
Public bug reported:
I have had quite some issues with the touchpad on my 2013 DELL XPS 13
since installing 18.04. It worked fine on previous versions.
Typical observations:
- lag
- cursor movements being interrupted
- more lag
- single/double tap not being detected consistently
- did I
I didn't make any config changes but I no longer see this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1749878
Title:
GDM doesn't accept mouse clicks in Wayland mode
To manage
Bug and workaround https://bugs.launchpad.net/ubuntu/+source/nvidia-
graphics-drivers-340/+bug/1741671/comments/14 confirmed on older NVidia
ION machine with nvidia-340 on kernel 4.13.0-26.
Thanks guys!!
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
will not update
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Greetings! Thank you for the prompt reply and request to run some code for
testing. I am a total beginner and am trying to get away from Windows, so I
really don´t know what to do in Ubuntu. Is there a way to access a
blow-by-blow instruction as to what and how I should do?
Keep well,
Thanks for the prompt reply, Jamie!! I have been a Windows user since version
1 they reply you sent me might as well be in Urdu, unfortunately. Besides I am
a total beginner here. Is there something in the contents that I should do, or
will the Canonical people eventually write some code in
Does somebody know will this bug affect to Ubuntu 16.0.2 that will be released
in a week
(http://news.softpedia.com/news/ubuntu-16-04-2-lts-delayed-until-february-9-due-to-serious-boot-regression-512445.shtml)?
Or they have a time to fix it?
As I know, it will include new mesa etc.
I checked
Public bug reported:
Unsure what causes this, but noticed a couple of issues recently that
cause temporary or persistent GUI lockups. I can usually get to a
different TTY to look at whats going on and find log entries like below
in the syslog. They often seem to occur in batches. So far most
11.2.0~rc3-0ubuntu0.2 working fine for me with a Radeon R7 250. Tested
SuperTuxKart, 0AD, Civ5, Sublevel zero.
--
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/1548845
Title:
[FFe] mesa 11.2.0
Public bug reported:
I am a totally new user and I do not know my way around. All I was
doing was updating my system, formatting an HDD and playing Mahjongg
when all these messages showed up.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-updates 2:15.200-0ubuntu0.6
I believe this issue is the same as Gramps bug:8471: Windows Transparent
- UI modals for both People and Notes have transparent backgrounds
https://gramps-project.org/bugs/view.php?id=8471
Fixed in Gramps 4.2.1
** Bug watch added: gramps-project.org/bugs/ #8471
** Attachment added: "Screenshot from 2015-06-07 11-59-24.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460539/+attachment/4507974/+files/Screenshot%20from%202015-06-07%2011-59-24.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
my downloaded movies are fine when started but then they start doing a
slow motion thing
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
Uname: Linux 3.13.0-41-generic i686
and did not see
the behaviour on 3.16.0-24.32 before that. I don't see any xorg/unity
changes in the same time. I tried to find suspicious differences:
sam@wildthing:~/dev/ubuntu-utopic (master=)$ git lg
Ubuntu-3.16.0-24.32..Ubuntu-3.16.0-25.33 | grep -i -e usb -e hid -e blue -e
logitech -e mouse
Christopher, I've already replied to that comment. The BIOS version is
clearly not the issue. Further, the bug is confirmed by another user.
--
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/1371853
Problem still occurs with Microsoft XBox controller wireless receiver
unplugged.
--
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/1371853
Title:
Logitech wireless mouse periodically loses correct
Darren reports experiencing the *same* issue and correlates a possible
cause which matches the setup of the original reporting. I think it's
rather premature to dismiss that as a separate bug. Bugs are anyway not
scoped to individual people). I will report back if the problem occurs
again with the
Hi Christopher. The BIOS I have is already an F8 version variant and I
would like to keep the variant. Further, I have not had this problem in
the 6 years of owning the hardware until 14.04. So further to Darren's
comment it seems very likely that this is a recent software issue. I
noticed the
Sounds similar to Bug #993655 - as I said there, try Ctrl-Alt-F1 then
Ctrl-Alt-F7 to switch to a terminal and back.
--
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/1337586
Title:
Mouse loses
*** This bug is a duplicate of bug 1006156 ***
https://bugs.launchpad.net/bugs/1006156
I have a very similar-sounding issue with Logitech wireless mouse (no
headset). Periodically loses click handlers or something with very
closely related symptoms. Try switching to console and back (Ctrl-
Public bug reported:
This problem began with the 14.04 upgrade. The mouse has always worked
normally until then.
Approximately every 10 minutes - and possibly triggered by Alt-Tab
window switches/opening new windows - the mouse behaviour becomes rather
strange. Primarly, left-clicks are not
Christopher, I've added you to the ticket as you suggested in the linked
tickets. I did not see any further comments from the reporters in those.
Let me know if I can provide further information.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
*** This bug is a duplicate of bug 1006156 ***
https://bugs.launchpad.net/bugs/1006156
Christopher, I created bug 1371853 and added you there.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Interestingly enough after purging everything and reinstalling a few
times (I even tried bumblebee again) it stated to work miraculously.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
I cannot perform the fix suggested. One moment prime was working fine
and the next it wasn't an option any more.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1301490
Title:
PRIME
This was because i386-linux-gnu_gl_conf alternative was not set to auto.
Didn't change this manual.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1359960
Title:
i386 apps
Public bug reported:
I'm having issues with the propertary ATI drivers and i386 apps. FI
steam and the ubuntu-emulator. I get no HWA.
It seems to be a problem with the existance of both
/usr/lib32/fglrx/libGL.so.1.2 and /usr/lib/i386-linux-
gnu/mesa/libGL.so.1.2.0 the first is from
Purging the closed-source drivers and using the open source ones solved
it (after resetting Compiz and Unity settings)
--
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/1335626
Title:
Xorg
My bug report
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1335626 was marked
as duplicate to this one.
With me, it only happend since less than a week on Utopic with the ATI drivers.
I also get artifacts in QtCreator
--
You received this bug notification because you are a member
Had you read my accompanying comments on the bug about me only having
used Ubuntu for 2[TWO] weeks, and that I am NEW to this OPERATING
SYSTEM, you wouldn't have sent me the reply that you did.
Never mind, I will return to WINDOWS OPERATING SYSTEM, even though it is
buggy, but at least they do
Public bug reported:
I've only been using Ubuntu 14.04 for 2 weeks!!! Have no knowledge of
Unix or variants.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
The original reporter seems to have dissapeared and I have exactly the
same laptop and problem!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1028617
Title:
Cursor
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DistUpgraded: Fresh install
DistroCodename: saucy
DistroRelease: Ubuntu 13.10
DistroVariant: ubuntu
InstallationDate: Installed on 2014-01-20 (50 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018747/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018748/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018749/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018751/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018750/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018745/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018746/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018762/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018768/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018766/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018760/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018761/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018752/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018753/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018765/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018764/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: xinput.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018767/+files/xinput.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018754/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018763/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018756/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1028617/+attachment/4018755/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Public bug reported:
sudo nvidia-detector
none
sudo nvidia-xconfig
sudo: nvidia-xconfig: command not found
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
No longer an issue for me.
Thanks for the heads up.
--
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/1019500
Title:
gnome-session: Gdk-WARNING: gnome-session: Fatal IO error 11 (resource
** Changed in: compiz
Milestone: 0.9.10.0 = 0.9.10.2
--
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/1194004
Title:
[regression] Compiz wakes up 200Hz while the screen is
** Changed in: compiz
Milestone: 0.9.10.0 = 0.9.10.2
--
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/1037732
Title:
compiz crashed with SIGSEGV in xcb_glx_gen_textures_data_length() from
Public bug reported:
followed the instructions here
http://askubuntu.com/questions/160605/what-packages-how-do-i-uninstall-propriety-amd-catalyst-driver
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-experimental-12 (not installed)
ProcVersionSignature: Ubuntu
Public bug reported:
To replicate:
1. Enable multiple desktops. I assume that you will also have the keyboard
shortcuts enabled. Ctrl+Alt+Shift+ Arrow Key will move a window to a desktop
in that direction; Ctrl+Alt+Arrow Key will move your current display to a
desktop in that direction.
2.
** Description changed:
Installed Ubuntu 9.04 on a friends Amilo L7320GW.
LCD not recognised, so I ended up with just the top left 1280x800 of a
1600x1200 virtual screen.
It thought it was displaying the full 1600x1200.
However, when I tried to set 1280x800 resolution it still seemed
Thanks!
--
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/1130974
Title:
mesa_8.0.4-0ubuntu0.3 fails to build on 12.04.2
To manage notifications about this bug go to:
01_libdrm_nouveau1.patch is the patch you want to review.
** Patch removed: Patch to use libdrm_nouveau1
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1130974/+attachment/3539251/+files/01_libdrm_nouveau1.patch
--
You received this bug notification because you are a member of
Public bug reported:
It looks like the libdrm_nouveau library has split into version 1 and
version 2, but the mesa package shipped with Ubuntu precise hasn't been
updated to build with the updated packages.
apt-get source mesa
pbuilder-dist precise build mesa_8.0.4-0ubuntu0.3.dsc
This fails
Here's a patch which partially fixes it, but not entirely. Anybody want
to dig in and see what I've missed?
** Patch added: Patch to use libdrm_nouveau1
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1130974/+attachment/3539251/+files/01_libdrm_nouveau1.patch
--
You received this bug
Okay, here is another revision of the patch which looks like it works.
Cheers!
** Patch added: 01_libdrm_nouveau1.patch
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1130974/+attachment/3539292/+files/01_libdrm_nouveau1.patch
--
You received this bug notification because you are a
I have a similar issue, the output from dmesg gives a similar
appearance.
[ 1828.730779] [drm:i915_hotplug_work_func], running encoder hotplug functions
[ 1828.738627] [drm:intel_dp_check_link_status], TMDS-22: channel EQ not ok,
retraining
[ 1828.739133] [drm:intel_dp_start_link_train],
Turn off texture compression in the opengl plugin.
--
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/1100068
Title:
./bin/compiz (opengl) - Error: FBO is incomplete:
Public bug reported:
Unusual text rendering and glitchy grpahics. Specifically intermittant
freezing of graphics and lag with little or no load. This does not occur
all the time and sometimes occures on, or after boot.
I have two apple thunderbolt displays connected which seems to be the
issue,
Thanks Nick
This had been driving me mad, tried Ubuntu 12.04 12.10, Mint 13 14,
lmde, fedora 17 and 18 the intel driver always caused a segmentation
fault. Could not get fglrx drivers to work with 7700M until installing
xserver-xorg-video-intel_2.20.9-0ubuntu2+andrik2_amd64.deb
--
You
I think we could be providing an invalid image to the driver. Not sure.
** Summary changed:
- compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() from __memmove_sse2()
from ? /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
+ compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() from
Hmm, nope. I've removed UnityMTGrabHandles::glDraw from the description
as we're just painting a regular old tfp texture from xcomposite. This
sounds like some kind of weird problem in the driver.
Can the reporters run nvidia-bug-report.sh ? It should be in your PATH
by default.
** Summary
I can blank the screen using the command xset dpms force off, and it
doesn't turn back on. Can't it just run that when the lid is closed?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in Ubuntu.
Ah, sorry, done a little more testing. It stays off indefinitely
(without input) if the lid is open. But, if I run it after closing the
lid, it still wakes randomly. This means that it must be receiving some
imaginary input when the lid is closed to wake it.
My biggest problem is that some
sorry, leaking the pixmap.
--
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/927168
Title:
compiz crashed with SIGSEGV in memmove() from
drisw_update_tex_buffer() from dri_set_tex_buffer2() from
Yes, that will work, however we'll need to be careful about not leaking
in the decorator in that case. That will probably involve compiz
creating a session window as well for the decorator, which isn't a
difficult task
--
You received this bug notification because you are a member of Ubuntu-X,
** Changed in: compiz
Milestone: 0.9.8.2 = 0.9.8.4
--
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/1037732
Title:
compiz crashed with SIGSEGV in xcb_glx_gen_textures_data_length() from
1 - 100 of 293 matches
Mail list logo
