See http://wiki.ubuntu.com/X/Backtracing for directions on obtaining
backtraces.
If you cannot ssh into the box, then that indicates it might be a kernel
issue - check for kernel Oopses and so on (see debugging instructions
for the kernel if this is the case.)
--
feisty logout crash
This issue should be fixed in -openchrome, not the long obsolete -via
driver.
** Changed in: xserver-xorg-video-via (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: xserver-xorg-video-openchrome (Ubuntu)
Status: Confirmed = Triaged
--
[feisty/gutsy/hardy] f-spot and system
-unichrome is being dropped in Intrepid since it no longer builds with
Intrepid's xserver. -openchrome should be used instead, and will be the
only VIA driver supported going forward.
** Changed in: xserver-xorg-video-unichrome (Ubuntu)
Status: Confirmed = Won't Fix
--
To follow up to the above comments, as I mentioned, the specific issue
characterized on this bug - OpenOffice crashing - was resolved (it
turned out to be a xrandr heap corruption rather than a libxcb issue).
However, regarding the libxcb locking issue, I checked with upstream
about it the other
** Changed in: libxcb (Ubuntu Intrepid)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I'm marking the libxcb bug won't fix for hardy because a) the only
libxcb fix we can deploy at this point would be to disable libxcb
entirely - with the side effect of disabling compiz for everyone (c.f.
comment #137), and b) a viable workaround exists (c.f. comment #144).
See bug #236676 for
Thanks osteenbeergen for testing that, although your comments are
ambiguous - does it function better, worse, the same as, or just
differently than before?
Since we're seeing a few issues with traces involving libxcb, I've
prepared a non-xcb-enabled libx11 here:
Oh sorry, I did this one already earlier.
** Changed in: gimp (Ubuntu)
Status: New = Fix Released
--
Please merge gimp 2.4.6-1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/241285
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks, uploaded.
Checking Signature on .changes
gpg: Signature made Thu Jun 19 21:15:53 2008 PDT using DSA key ID E0E67611
gpg: Good signature from Bryce Harrington [EMAIL PROTECTED]
gpg: aka Bryce Harrington [EMAIL PROTECTED]
gpg: aka Bryce Harrington [EMAIL
Fwiw, Inkscape built fine with the patch locally, but it looks like all
of the buildd's failed.
** Changed in: poppler (Ubuntu)
Importance: Undecided = High
Status: New = Confirmed
--
libpoppler-glib-dev: Depends: libpoppler-glib3 (= 0.8.2-2) but it is not
installable
Public bug reported:
I got this error when trying to upload a minor patch to inkscape, which
has a build-dep on libpoppler-glib-dev:
http://launchpadlibrarian.net/14979320/buildlog_ubuntu-intrepid-
amd64.inkscape_0.46-0ubuntu4_FAILEDTOBUILD.txt.gz
Reading state information...
Some packages
I'm refiling this against evince since it sounds like from the comments
that this is where the bug really is.
If the X server crash can be reproduced reliably with the evince crash,
please feel free to open a task against xorg-server, however make sure
to include your /var/log/Xorg.0.log and a
** Changed in: gdm (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
Status: Confirmed = Triaged
--
Accessible GDM broken if non-existent input devices present
https://bugs.launchpad.net/bugs/83860
You received this bug notification because you are a member
Thanks Miguel, Martin, and ethanay for identifying and confirming the
problem is with the slow keys accessibility feature; I've updated the
title. @Juri, if you're still tracking this bug it would be helpful if
you concur with this analysis.
Could someone propose what the next step should be for
*** This bug is a duplicate of bug 220563 ***
https://bugs.launchpad.net/bugs/220563
** This bug has been marked a duplicate of bug 220563
Useful dual-head configuration requires manual editing of xorg.conf to set
Virtual
--
Can't configure extended desktop
*** This bug is a duplicate of bug 173837 ***
https://bugs.launchpad.net/bugs/173837
** This bug has been marked a duplicate of bug 173837
'new login in a window' should use Xephyr rather than Xnest
--
xephyr should have a menu entry
https://bugs.launchpad.net/bugs/189579
You received
** Changed in: gdm (Ubuntu)
Sourcepackagename: xorg-server = gdm
--
xephyr should have a menu entry
https://bugs.launchpad.net/bugs/189579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
This will be fairly important to have working for input-hotplug support
** Changed in: gnome-control-center (Ubuntu)
Target: None = intrepid-alpha-6
--
Integrate extra buttons in mouse properties
https://bugs.launchpad.net/bugs/198313
You received this bug notification because you are a
** Changed in: nautilus (Ubuntu)
Sourcepackagename: xorg = nautilus
--
Nautilus-share - keyboard letter keys un-responsive
https://bugs.launchpad.net/bugs/232235
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
seb128, please explain what the xorg issue is, not just it's an xorg
issue - we need some additional clues in what needs
changed/reverted/fixed...
Also, can someone who is experiencing this problem please post their
/var/log/Xorg.0.log (to get version #'s etc.)
** Changed in: xorg-server
By 'menu' I assume it's meant an entry in the gdm startup stuff... in
any case, not really an xorg-server bug so bumping package to gdm.
** Changed in: gdm (Ubuntu)
Sourcepackagename: xorg-server = gdm
--
xephyr should have a menu entry
https://bugs.launchpad.net/bugs/189579
You received this
** Summary changed:
- gdmflexiserver or 'new login in a window' doesn't refresh screen
+ 'new login in a window' should use Xephyr rather than Xnest
** Changed in: gdm (Ubuntu)
Sourcepackagename: xorg-server = gdm
--
'new login in a window' should use Xephyr rather than Xnest
** Changed in: totem (Ubuntu)
Sourcepackagename: xorg-server = totem
--
The program 'totem' received an X Window System error.
https://bugs.launchpad.net/bugs/224565
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
*** This bug is a duplicate of bug 173837 ***
https://bugs.launchpad.net/bugs/173837
** This bug has been marked a duplicate of bug 173837
'new login in a window' should use Xephyr rather than Xnest
--
xephyr should have a menu entry
https://bugs.launchpad.net/bugs/189579
You received
*** This bug is a duplicate of bug 32457 ***
https://bugs.launchpad.net/bugs/32457
** This bug has been marked a duplicate of bug 32457
[Gutsy] [Regression] gnome-screensaver activates while playing SDL games
--
something steals focus of fullscreen 3d apps
*** This bug is a duplicate of bug 32457 ***
https://bugs.launchpad.net/bugs/32457
** This bug is no longer a duplicate of bug 163865
something steals focus of fullscreen 3d apps
** This bug has been marked a duplicate of bug 32457
[Gutsy] [Regression] gnome-screensaver activates while
Closing as per comment #26
** Changed in: gnome-session (Ubuntu)
Status: Confirmed = Fix Released
--
Connection to ICE-unix/.. socket times out so programs take minutes to start
https://bugs.launchpad.net/bugs/58171
You received this bug notification because you are a member of Ubuntu
-server (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.24 = xorg-server
Status: Triaged = Fix Released
** Changed in: xorg-server (Ubuntu Hardy)
Importance: Undecided = High
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
Status: New = In Progress
** Changed in: cairo (Ubuntu)
Target: later = intrepid-alpha-1
--
web page background render errors
https://bugs.launchpad.net/bugs/186186
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Hmm, actually patch 42 is already in the Hardy xserver. Are there
actually any Xorg tasks to do here? Sounds like the only thing needed
is to revert that compiz patch, which should be cleared by mvo.
--
[nvidia] compiz displays white screen when locked
https://bugs.launchpad.net/bugs/160264
No changes to g-c-c are needed.
** Changed in: gnome-control-center (Ubuntu Hardy)
Status: New = Fix Released
** Changed in: xserver-xgl (Ubuntu Hardy)
Importance: Undecided = Medium
Target: None = ubuntu-8.04.1
--
gnome-display-properties crashed with SIGSEGV in _start()
I've uploaded this to Intrepid.
If you'd like to see it included for Hardy, please follow the SRU
process as outlined at https://wiki.ubuntu.com/StableReleaseUpdates. I
think this patch would qualify if you're interested.
--
gnome-display-properties crashed with SIGSEGV in _start() [when
*** This bug is a duplicate of bug 224179 ***
https://bugs.launchpad.net/bugs/224179
** This bug has been marked a duplicate of bug 224179
gnome-display-properties font size is too large
--
screen resolution pictures are connected
https://bugs.launchpad.net/bugs/219014
You received this
* Move the Detect Displays button to the top right of the window, right of the
Clone Screens checkbox.
* Look for and remove excess padding
* Shrink the vertical height of the graphical layout section
That should be sufficient.
Note that it would also be possible for the applet to compare the
** Changed in: xterm (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
** Changed in: ubuntu
Sourcepackagename: cruft = None
--
font in terminal does not resemble font in preview
https://bugs.launchpad.net/bugs/190848
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
*** This bug is a duplicate of bug 93847 ***
https://bugs.launchpad.net/bugs/93847
** Changed in: gnome-system-monitor (Ubuntu)
Sourcepackagename: xorg = gnome-system-monitor
** This bug has been marked a duplicate of bug 93847
Excessive CPU usage by Gnome System Monitor
--
Xorg
Not sure why xft was subbed to this; there is no explanation in comments
for changed needed to xft, so am unsubscribing it.
** Changed in: xft (Ubuntu)
Status: New = Invalid
--
font in terminal does not resemble font in preview
https://bugs.launchpad.net/bugs/190848
You received this bug
** Changed in: cruft (Ubuntu)
Sourcepackagename: xft = cruft
--
font in terminal does not resemble font in preview
https://bugs.launchpad.net/bugs/190848
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
See wiki.ubuntu.com/X/Config for an example of how to configure it
statically. Or you can use Screen Resolution to set it. Or put your
xrandr command line in your ~/.xsession file.
** Changed in: gtk+2.0 (Ubuntu)
Sourcepackagename: None = gtk+2.0
Status: New = Confirmed
** Summary
** Changed in: totem (Ubuntu)
Sourcepackagename: xserver-xorg-video-ati = totem
--
Totem quits on startup due to X Window System error
https://bugs.launchpad.net/bugs/194987
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in
Dual head configuration was enabled in gnome-control-center
(1:2.22.1-0ubuntu2).
There is still an issue where Virtual size must be specified in
xorg.conf, but that's an xorg bug, not gnome-control-center.
Marius, regarding your need to explicitly turn on the external monitor,
I've not
Thanks, looks good. I'll take it from here.
** Changed in: xserver-xgl (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
gnome-display-properties crashed with SIGSEGV in _start() [when running xgl]
https://bugs.launchpad.net/bugs/215396
You received this bug
Closing as out of date. If the problem still occurs with released
Hardy, please feel free to reopen with the requested information.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Invalid
--
visual bug in gnome terminal
https://bugs.launchpad.net/bugs/128329
You
Hi John,
Thanks for investigating this. It lines up with what I suspected as
well.
jcristau suggested alternatively something more like what the xserver does:
http://cgit.freedesktop.org/xorg/xserver/diff/randr/rrdispatch.c?id=3b71b0f89f1db837da91650baa0ef4bb7ef2e98f
except with
I believe this is fixed with the new gnome-display-properties tool. If
not, please feel free to reopen with additional detail.
** Changed in: xorg (Ubuntu)
Status: Confirmed = Fix Released
--
[Hardy] Ubuntu does not remember the screen resolution
https://bugs.launchpad.net/bugs/189599
Has anyone had a chance to test this? Is the problem even still an
issue? It's gotten to be too late to push this for Hardy but if it
still occurs I'll queue it to go in for Intrepid.
If no one responds with test results within a couple months, I'll assume
the problem has resolved itself and we
it often just made performance worse, and sometimes created
visualization bugs. People wishing to gain added performance should be
experimenting with EXA anyway, not this setting. (closes LP: #182038)
-- Bryce Harrington [EMAIL PROTECTED] Mon, 14 Apr 2008 12:34:54 -0700
** Changed
Toltech, 'Unknown' is for upstream bug status, and just means the bug
updater scripts couldn't figure out the upstream priority. It is
'invalid' for firefox-3.0 since the core issue was identified to be an X
issue rather than firefox itself.
For X issue importance, Critical is reserved for bugs
Patch to switch to turn off offscreen pixmaps when using XAA. This is
the exact patch used by Fedora.
The XAAOffscreenPixmaps feature seems to be an early optimization trick
that never really worked right; often it resulted in *worse* performance
than having no optimization at all. So most
The patch is uploaded, just waiting on release managers.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Fix Committed
--
Black rectangle instead of image in FF3 [Hardy]
https://bugs.launchpad.net/bugs/182038
You received this bug notification because you are a member of Ubuntu
Hi John,
Attaching the patch to a bug report (maybe this one?) would be a good
start. I don't review xserver-xgl bugs too frequently, so you might
want to find me or tjaalton on #ubuntu-x or the ubuntu-x@ mailing list
once it's ready for upload.
--
gnome-display-properties crashed with SIGSEGV
Issue seems to no longer be present in hardy.
** Changed in: xchat-gnome (Ubuntu)
Status: New = Fix Released
--
xchat-gnome performance lags with over 12 channels
https://bugs.launchpad.net/bugs/06
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: xkeyboard-config (Ubuntu)
Sourcepackagename: xorg = xkeyboard-config
--
infinite loop with PrintScreen
https://bugs.launchpad.net/bugs/84278
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Released
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = James Westby (james-w)
--
error starting GNOME Settings Daemon
https://bugs.launchpad.net/bugs/199960
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
the failure
back up to the caller. If there are still crashes, this lets us
handle them at a higher level.
-- Bryce Harrington [EMAIL PROTECTED] Wed, 09 Apr 2008 14:46:48 -0700
--
gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
https://bugs.launchpad.net/bugs
I've uploaded a patch with some better error checking in it. Please re-
test against current Hardy and reopen if it is still crashing. (It is
possible I merely shifted the crash to another spot, but I'll be
optimistic...)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed =
@Pavel, how did you arrive at that patch as a fix for this bug? (Not
arguing against the patch, just curious). I note that the patch affects
the EXA code in the -ati driver, where I understood this particular
render bug only occurs in XAA, and goes away when using EXA.
(Are multiple bugs being
This appears to no longer be an issue (at least, I can't reproduce it).
Please reopen with additional details if it still occurs on Hardy.
** Changed in: xkeyboard-config (Ubuntu)
Status: Confirmed = Fix Released
--
several keyboard layouts are listed several times
: Undecided = Wishlist
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
Status: New = Triaged
--
gnome-display-properties shows incorrect monitor size
https://bugs.launchpad.net/bugs/211409
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Florent, yeah I think you're right, it looks cleaner that way and gets
rid of the need for freeing things.
http://people.ubuntu.com/~bryce/Uploads/gnome-
desktop_2.22.0-0ubuntu5.dsc
seb128, if it looks good to you now, go ahead and upload it.
--
gnome-display-properties should revert change
Look in your Xorg.0.log for a line like:
(II) RADEON(0): Max H-Image Size [cm]: horiz.: X vert.: Y
That line is what your monitor is reporting of its true capabilities,
and is provided directly from the monitor manufacturer.
Now simply take X and Y, and then calculate the diagonal: D =
I can confirm that adding Option XAANoOffscreenPixmaps true resolves
the black image problem.
I still have unease about setting this as a default for everyone,
though. Typically when setting these sorts of options on for everyone,
a lot of corner cases turn up within 1-2 weeks after about random
I've been testing this dialog on my own system and it works for the most
part, but there's a few situations where it may fail, such as if the
user did not have an existing ~/.gnome2/monitors.xml. I would
appreciate it if others could test this out with care and report any
corner cases that aren't
I'm getting this as well on a dell inspiron 1420. Video playback worked
properly a month or two ago, so it's been updates since then that broke
it.
I suspect the commenters on this bug are seeing at least two separate
bugs. One where shifting to a different sound system makes it work
(although
Looks like your monitor is reporting its dimensions as:
(II) intel(0): Max H-Image Size [cm]: horiz.: 31 vert.: 23
...
(II) intel(0): clock: 25.2 MHz Image Size: 306 x 230 mm
which is 12 x 9, which calculates out to a 15 diagonal.
I confirmed this via your monitor's manual
You're awesome Gabor!
In fact this was one case I was experimenting with the revert dialog I'm
working on, to ensure it reacts appropriately. But I agree your patch
to prevent the situation in the first place via UI sugar is even
superior. I will include your patch in my next upload, thanks!
Ah, okay; postponing xorg milestone as well.
** Changed in: xorg-server (Ubuntu)
Target: ubuntu-8.04 = None
--
web page background render errors
https://bugs.launchpad.net/bugs/186186
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Florent, cool, I'll take a look at your patch tomorrow.
Meanwhile, I've continued work on my end, and have a new update
available for testing:
http://people.ubuntu.com/~bryce/Uploads/gnome-desktop_2.22.0-0ubuntu4.dsc
I've been looking into all of the fglrx issues today. Many I suspect
are due to AIGLX, but I'm awaiting confirmation of that. Applying help
towards confirming and providing extra info on any of those bugs (which
are in linux-restricted-modules-2.6.24) would help in moving things
forward.
I've reviewed the changes up to Mar 19th, and I see the Mar 28 changes
for clone mode, but haven't reviewed those yet. In any case I do plan
on updating our code to newer upstream stuff once this revert dialog is
done.
I look forward to seeing your xevent test code. Sounds like it still
Kyle, let's please try to keep the discourse civil. Like many of the
other commenters have reported in this thread, you should be using xorg-
server and AIGLX or NVIDIA's implementation of accelerated indirect
rendering. If there exist bugs in it, those should be reported. If Xgl
works better
108 caused FTBS. My bad.)
-- Bryce Harrington [EMAIL PROTECTED] Tue, 25 Mar 2008 02:11:52 -0700
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed = Fix Released
--
Display capplet's border is too big
https://bugs.launchpad.net/bugs/204447
You received this bug
108 caused FTBS. My bad.)
-- Bryce Harrington [EMAIL PROTECTED] Tue, 25 Mar 2008 02:11:52 -0700
** Changed in: control-center (Ubuntu)
Status: Fix Committed = Fix Released
--
monitor resolution panel won't fit on 640x480 screen
https://bugs.launchpad.net/bugs/203897
You received
If anyone is still using Xgl, please test with the latest updates.
We've put in some checks which we think should handle the crash more
gracefully.
If it's still crashing under Xgl, please reopen this bug, and I can look
into adding a check specifically for Xgl. Don't think it's necessary
One hackish coming right up...
** Attachment added: gd_randr12_revert_support.patch
http://launchpadlibrarian.net/12935259/gd_randr12_revert_support.patch
--
gnome-display-properties should revert change automatically if not acknowledged
https://bugs.launchpad.net/bugs/197673
You received
untested; for review only
** Attachment added: cc_randr12_revert_dialog.patch
http://launchpadlibrarian.net/12935270/cc_randr12_revert_dialog.patch
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed = In Progress
--
gnome-display-properties should revert change
gnome-desktop (1:2.22.0-0ubuntu3) hardy; urgency=low
* debian/patches/103_gd-xrandr-xerror-check.patch:
- Catch X error thrown and exit function gracefully (LP: #199960)
- Don't try to apply store config to undefined screens (LP: #197645)
** Changed in: gnome-settings-daemon (Ubuntu)
Attached is a patch which fixes the lack of icon and also fills in the
window application name in the kicker panel.
This patch is included in the following package, which is ready for
upload:
http://people.ubuntu.com/~bryce/Testing/XrandrGui/gnome-control-center_2.22.0-0ubuntu2_i386.deb
the border size I'll look at as well (also c.f. bug 203897)
** Changed in: gnome-control-center (Ubuntu)
Status: New = In Progress
--
Display capplet's border is too big
https://bugs.launchpad.net/bugs/204447
You received this bug notification because you are a member of Ubuntu
Desktop
Hmm, as currently set on my system, the panel fits into 540x437 (see
attached), which fits 640x480 with ample margin.
** Attachment added: xrandr-gui-540x437.png
http://launchpadlibrarian.net/12852208/xrandr-gui-540x437.png
--
monitor resolution panel won't fit on 640x480 screen
By changing the border width from 18 to 5, we can shrink it to 514x411
(again, on my system).
** Attachment added: xrandr-gui-514x411.png
http://launchpadlibrarian.net/12852224/xrandr-gui-514x411.png
--
monitor resolution panel won't fit on 640x480 screen
A few more glade tweaks gets us down to 472x387. I think this should
give us ample margin. :-)
--
monitor resolution panel won't fit on 640x480 screen
https://bugs.launchpad.net/bugs/203897
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Attachment added: xrandr-gui-472-387.png
http://launchpadlibrarian.net/12852302/xrandr-gui-472-387.png
--
monitor resolution panel won't fit on 640x480 screen
https://bugs.launchpad.net/bugs/203897
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Here is the glade file that implements the shrinkages. To test, place
in /usr/share/gnome-control-center/glade/ and restart gnome-display-
properties.
Like I said, this won't fix underlying font size issues (a separate bug)
but should now give a lot more margin for fitting into 640x480.
**
This nukes the border size down to something more reasonable.
** Attachment added: 109_cc-randr12-gui-shrinkage.patch
http://launchpadlibrarian.net/12852327/109_cc-randr12-gui-shrinkage.patch
--
Display capplet's border is too big
https://bugs.launchpad.net/bugs/204447
You received this bug
Ready for upload:
http://people.ubuntu.com/~bryce/Uploads/gnome-control-center_2.22.0-0ubuntu3.dsc
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress = Fix Committed
--
Display capplet's border is too big
https://bugs.launchpad.net/bugs/204447
You received this bug
Ready for upload:
http://people.ubuntu.com/~bryce/Uploads/gnome-control-center_2.22.0-0ubuntu3.dsc
** Changed in: control-center (Ubuntu)
Importance: Undecided = Medium
Status: Confirmed = Fix Committed
--
monitor resolution panel won't fit on 640x480 screen
@seb128, part of a patch that I sent you earlier included a test for Xgl
which I knew would break in this case - you rejected the patch because
part of it was parsing Xorg.0.log. However the portion that tests for
Xgl is independent and seems still valid. While I agree that xgl is not
supported
Unfortunately, many cases where xrandr fails, it locks the system up, so
we'd have no way to ensure that the restoration logic would always get
called reliably.
But something similar could be done by e.g. moving the previous
configuration to monitors.xml.old, and then have gnome-settings-daemon
@Egon, thanks. For Hardy it's probably too intrusive to force all -ati
users over to EXA but perhaps I can do it case by case. For this I'll
need your card's exact pci id. Can you please attach the output of
`lspci -vvnn`?
@kripkenstein, can you doublecheck /var/log/Xorg.0.log that EXA is on,
Alexander, I see that this has a component filed against xorg-server;
could you explain what is needed to be done at the xorg-server level?
If it is just the question about the XAA code, I'm not sure I follow the
question, could you ask the question again in more detail?
In general, XAA is in
Miso, are you using the -intel driver? If so, greedy should be on by
default now when EXA is used (which I believe should now be all the
time, unless configured differently in xorg.conf).
For users of -ati or -nv, I'd be interested in hearing if setting Option
AccelMethod EXA makes the issue go
Hmm, not sure what's going on. It might help to run xterm with its
TRACE messages flipped on. Here's a package with this done:
http://people.ubuntu.com/~bryce/Testing/ICE-unix/
I also encourage everyone experiencing this issue to install debug
packages of gnome-session, libice, libgnomeui,
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress = Fix Committed
--
gnome-settings-daemon crashed with SIGSEGV in rw_screen_list_outputs()
https://bugs.launchpad.net/bugs/197645
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
@William Woelke: did you also have this issue in gutsy, like John?
@John: Did this start happening when you shifted to gutsy, or did it
occur before that?
--
mouse keys turns on randomly
https://bugs.launchpad.net/bugs/192508
You received this bug notification because you are a member of Ubuntu
It's pretty simple to change the colors in the code. Do you know of a
place where theme colors can be queried from? I'd like to avoid a plain
gray.
--
Screens Resolution tool shows text labels not centered, overlapping monitor
area
https://bugs.launchpad.net/bugs/201589
You received this bug
Unfortunately these backtraces are still incomplete (they show debug
symbols for Xorg calls but not for gnome-settings-daemon or gnome-
desktop), so it is hard to tell where the crash is starting. Please add
deb http://ddebs.ubuntu.com gutsy main universe to your sources and
install the packages
The previous code (in main.c) worked by applying the changes via xrandr,
then prompting the user about if they're okay, and then writing to
gconf. So if there was a catastrophic failure preventing the prompt, no
config would be written.
In redhat's new code, it writes the changes to monitors.xml
The issue where gnome-settings-daemon was not working is solved by bug 198951.
For the issue where upgraders must restart before Apply becomes functional, I
suspect this is now being prompted for in general, and is a transitory issue in
any case.
For the requirement of xrandr 1.2 rather than
1001 - 1100 of 1256 matches
Mail list logo
