OK, thanks. Maybe I am thick here, but just a last question: is there
confirmation (Guido?) that reverting to 2.4 will fix the suspend/resume
locks? If yes, I can upgrade and maybe help with the UXA testing.
Thanks!
--
[i945] (Needs UXA) X freezes a few minutes after resuming
https://bugs.launch
Public bug reported:
After switching to the low-power GPU, several applications that use
OpenCL will refuse to start and crashes: for example GIMP do the follow:
(0)samsung-romano:~% gimp
Setting of real/effective user Id to 0/0 failed
ERROR: could not insert 'fglrx': Operation not permitted
Erro
Strange --- this bug is marked as fixed but I can reproduce it all the
time on my LVD. xserver-xorg 1:7.7+1ubuntu6 (apt-get update tell me
it's recent). Am I doing something wrong?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in U
I can confirm that the bug (both the badly rendered fill areas and the
crash) still happens in my laptop with 13.04 (intel drivers) and still
does not happen in one of my desktop with 13.04 (radeon open source
drivers).
I am now downloading the test image of trusty to see if I am able to
check for
Short: fixed on Trusty Thar beta.
Long:
Tested on Trusty image as of today (2014-01-7), with versions:
xfig 1:3.2.5.c-1ubuntu1
unity 7.1.2+14.04.20131106.1-0ubuntu1
xserver-xorg-video-intel 2:2.99.907-0ubuntu1
in this configuration I was *not* able to trigger the bug (neither the c
PS: in Trusty xfig will core dump on exiting, though. But it seems
unrelated.
--
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/1184085
Title:
Xorg server crashes when drawing dashed circles
Christopher M. Penalver, it seems fit to mark the bug closed (it is
fixed).
About the SRU procedure, the problem is that I have no idea which patch
/ package release / update to which software caused the fix, so I am
quite swamped by the SRU procedure posted.
The impact of this bug could be high
Hmm. Using Ubuntu Gnome 16.04 here, intel graphics, no bug. On another
laptop, with Xubuntu, it happens.
I think is more screen-locker related that desktop-flavor related.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
I can reproduce in natty too, with an eee-pc.
The good news is that the patch in the ppa: https://launchpad.net/~aapo-
rantalainen/+archive/ppa-aaporantalainen works very well. So this
problem has, at least for the user of a synapctics touchpad, a solution.
See also the page at http://cc.oulu.fi/~
The (this morning) update of fglrx-updates &co (Now at version
2:8.881-0ubuntu6.1) seems to have fixed the worst of it.
Nevertheless, there is still some (minor, but not nice) problem. See the
attached shot --- easier than explain.
(5 minutes...)
well, I stand back, it seems that it's impossi
Some more info: had a lot of tearing when activating the "notification"
(mouse in the lower right corner) area. Unbearable with "anti tearing"
off, simply annoying with "anti tearing on".
Still unable to obtain a screenshot. Can anyone confirm this?
--
You received this bug notification because
Yes, I have similar (albeit normally smaller) corrupted drop down and
scroll-bars.
--
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/838577
Title:
GNOME Shell display problems with FGLR
Another data point: the lock-screen simply makes the screen a mess
(complete lack of sync, it seems, like the not-so-good-old-times when
you got ModeLine frequency wrong in x11.conf files).
Uf. Need to go back to Unity to be able to work, I hope it will be fixed
soon.
--
You received this bug no
I think that the upstream bug is not correct here. The problem is not
with panning; the problem is with scaling and the mouse behavior.
I have xserver-xorg 1:7.7+1ubuntu6 (X.Org X Server 1.14.5), and if I
issue
xrandr --output LVDS1 --scale 2x2
the screen scales correctly, but then the mouse
So basically, the "Fix released" status is incorrect. The bug referred
to the title is still here (at least in Saucy, will test Trusty). Maybe
the other problem (panning, mentioned in the upstream bug, not related
with this bug title) is fixed, but not this one.
--
You received this bug notificat
Probably this bug has been marked invalid because there is a mix of two
bugs here: one is related to panning (which I do not know if it's fixed
or no), and the other one to mouse constraints when scaling.
I have X.Org X Server 1.14.5 , and if I issue
xrandr --output LVDS1 --scale 2x2
the screen
Probably this bug has been marked invalid because there is a mix of two
bugs here: one is related to panning (which I do not know if it's fixed
or no), and the other one to mouse constraints when scaling.
I have X.Org X Server 1.14.5 , and if I issue
xrandr --output LVDS1 --scale 2x2
the screen
...checked in 14.04 trusty, still here.
A real PITA because the scaling is really useful with all the
applications (*-tweak-tools, are you listening me?) which are expecting
1600x1200 pixel every time...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
Can a bug supervisor mark this for Trusty and removing the (wrong) Fix
Released status?
--
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/883319
Title:
xrandr --scale restricts area in which
Yes --- I understand. But why the bug is marked "Invalid"? It is quite
easy to reproduce, and difficult to miss (if you ever needed to use the
--scale option).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.la
I can confirm that the bug is fixed in Trusty Thar 14.04.
--
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/1184085
Title:
Xorg server crashes when drawing dashed circles
To manage notifica
Public bug reported:
To reproduce:
install xfig (sudo apt-get install xfig)
open xfig --- then try to draw a circle with dashed line (choose the
circle, select the dash line in the row below the main screen, click in
the canvas to draw). The Xorg ser4ver crashes and You are back to login.
The f
I have too this problem again. Opened a new bug:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184085
--
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/553647
Title:
xserver cr
** Description changed:
To reproduce:
install xfig (sudo apt-get install xfig)
open xfig --- then try to draw a circle with dashed line (choose the
circle, select the dash line in the row below the main screen, click in
the canvas to draw). The Xorg ser4ver crashes and You are back
apport information
** Tags added: apport-collected raring ubuntu
** Description changed:
To reproduce:
install xfig (sudo apt-get install xfig)
open xfig --- then try to draw a circle with dashed line (choose the
circle, select the dash line in the row below the main screen, click
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687307/+files/BootLog.txt
--
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/11840
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687309/+files/DpkgLog.txt
--
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/11840
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687310/+files/GconfCompiz.txt
--
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/bu
apport information
** Attachment added: "HookError_cloud_archive.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687311/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687312/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687313/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687314/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bug
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687315/+files/LightdmLog.txt
--
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
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687316/+files/Lspci.txt
--
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/1184085
T
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687317/+files/Lsusb.txt
--
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/1184085
T
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687318/+files/ProcCpuinfo.txt
--
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/bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687319/+files/ProcEnviron.txt
--
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/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687320/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687321/+files/ProcModules.txt
--
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/bu
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687327/+files/Xrandr.txt
--
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/1184085
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687328/+files/xdpyinfo.txt
--
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/118
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687329/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687323/+files/UdevLog.txt
--
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/11840
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687324/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687325/+files/XorgLog.txt
--
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/11840
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687326/+files/XorgLogOld.txt
--
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
@Dave:
I managed to have a working apport-collect. It wasn't working because for
whichever reason python-launchpadlib and python-launchpadlib-toolkit were not
installed. It reported the bug of the last error, but spat out this:
(process:13190): GLib-CRITICAL **: g_slice_set_config: assertion `
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687330/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687308/+files/CurrentDmesg.txt
--
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/
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1184085/+attachment/3687322/+files/UdevDb.txt
--
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/1184085
I can confirm that the bug *does NOT* occur in another machine with ATI
card which uses the open-source radeon modules. In that machine, xfig
works ok (no crashes and the solid color fill are ok). So it seems a
intel-driver bug.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Un
@Chris Wilson:
Sorry, didn't know. I supposed an -intel problem because my other PC (ATI
radeon based) works ok.
Any hint on a possible fix/workaround? I know I am in a minority, but I use
xfig quite a lot... :-(
--
You received this bug notification because you are a member of Ubuntu-X,
whi
Thanks --- although I suspect it will be tough on performance. Now the
problem I have... it was in 2003 the last time I had to edit an
xorg.conf file, and now I discovered it's not there anymore. I have seen
a group of files in /ust/share/X11/xorg.conf.d/, but no idea on how and
where to add that o
@Chris: is there an upstream bug to link?
I hoped that the last update to X that entered this morning could have fixed
it, but no, still here.
--
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.laun
Possible a duplicate of https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/+bug/1568604.
Check if switching to a VC (Ctrl-Alt-F1) and back (Alt-F7) fixes the
thing.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Changed the title accordingly. If in tweak tools you deselect "file
manager handle desktop", you than have the background black all the
time (not only in overview).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https
Same problem, open source intel drivers.
So not fixed (or reintroduced).
** Summary changed:
- Gnome-Shell activities shows black background with fglrx in raring
+ Gnome-Shell activities shows black background
--
You received this bug notification because you are a member of Ubuntu-X,
which i
A comment: I could manage the full resolution of my Samsung laptop only
with the solution here:
http://askubuntu.com/questions/205112/how-do-i-get-amd-intel-hybrid-
graphics-drivers-to-work
(one million thanks). But my main problem was that the open-source
driver was not giving me the correct scr
@Marco: you're right --- wrong place. But if anyone would arrive here on
trying to solve a problem similar to mine: I can use the free drivers
simply removing the nomodesetting flag from the boot command line (which
was necessary to boot the installation USB). Thanks.
--
You received this bug not
I have hand-installed fglrx-updates, and now it's almost ok for me - I
just have the glitches on pop-up tips and ayatana scroll bars, but it's
usable and quite fast. Using that now, let's see.
Jockey (additional hardware) continue to think that no additional driver
is installed. Trying to "activat
Correcting myself. Crashing like a crazy when viewing/editing videos.
Back to unity. Sigh.
--
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/838577
Title:
GNOME Shell display problems wi
** Attachment added: "Full Xorg log from crashing session."
https://bugs.launchpad.net/bugs/1032573/+attachment/3246641/+files/Xorg.0.log.old
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Has anyone any hints on this? It is really obnoxious.
I *think* it happens when using nautilus, but I cannot be sure.
Some hints on how to debug?
--
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/
Yes, five minutes was an approximate thing. It crashed on me today few seconds
after resume, mad yesterday after more than one hour work.
If only apport would work. I have seen something about a crash in
XInspectProperty or something similar...
--
You received this bug notification because you
@Kevin: which cache are you referring to? Thanks!
Can someone tell me how can I use apport manually? I have this sensation
that the apport-gtk is to blame for the apport crash, and having another
way to obtain a text-only trace could help to nail it down.
--
You received this bug notification be
The method for triggering the bug explained in #81 does not work for me.
Is still useful to test the package from -proposed?
--
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/9
Well, I could not trigger the bug, but had crashes every few hours.
Since when updating to the proposed package, I had no more crashes -
can't be 100% sure it's fixed, given the random nature of the thing, but
it seems ok, and it's for sure much better than before.
--
You received this bug notifi
Great. Is there any instruction on how to undo the - proposal activation
? I used the method described in the wiki to add only this package (the
trick with priorities), is deselecting the proposed repository
sufficient? Thanks!
--
You received this bug notification because you are a member of Ubu
Well, I am quite confused now.
The bug name was changed "needs UXA". But AFAIK that's not true. In my
notebook, booting with a Jaunty live cd, the X freezes after a resume
form S2R with *standard* configuration, no UXA needed at all.
I suspect there are two bugs mixed here:
1) the first one is t
OK. great news. What about a recipe to fix it in Jaunty? Thanks!
--
[i945] (Needs UXA) X freezes a few minutes after resuming
https://bugs.launchpad.net/bugs/339091
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
*** This bug is a duplicate of bug 201330 ***
https://bugs.launchpad.net/bugs/201330
Hmmm. Not so sure if it's a correct duplicate. Just to put my 2 cents
in, I had the same exact problem, and solved it thanks to this post:
http://www.rebelzero.com/hardware/ubuntu-810-atiamd-fglrx-driver-
upd
Just to throw in my 2 cents, this report is the one that is stopping me to
update to Maverick my Asus Eee PC 1005PE netbook. UNR in Lucid is pleasant to
use.
Now, I think that it would be nice if someone of the affected people could try
to log in with a normal Gnome session, and tell here if in
@Kevin:
when you are in the login screen, there is a drop-up menu (in 10.04 is on the
bottom of the screen, slightly at the right) where you can choose session.
Choose "gnome session" and voilá. The setting is remembered for further logins.
--
[Intel GMA 945/950] Unity Interface Is Extremely Sl
I think this (not backporting) is most unfortunate; basically because it
will not expose the future solution to a very big testing bed which
would be very useful in order to not repeat the failure we're seeing
now.
On the other hand, which is the suggested path for 10.04 users with this
problem?
I finally upgraded, telling the update process to substitute old conf
files. On my hardware, Unity is working --- I can't say it is snappy,
but it works at an acceptable speed. More data:
Asus eeePC 1005PE with 1Gbyte RAM, video:
00:02.0 VGA compatible controller: Intel Corporation N10 Family Int
Just to specify a bit more about the comment #62: for me, the only thing
that is really painfully slow is the "Application" launcher (from 10 to
30 seconds to show). By the way, is it possible to configure it so that
it stays put after launching the application? This could reduce the pain
(launch i
76 matches
Mail list logo
