*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Error activating XKB configuration on startup
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Error activating XKB configuration: Japanese keyboard with US layout
This bug is very, very widespread so bumping up the priority another
notch.
** Description changed:
After upgrading to Edgy Eft, the Polish symbols disapeared when I write.
However, they are properly displayed at the menus, web pages, etc.. During
logging in, the system showed an error
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug is no longer a duplicate of bug 217627
Japanese keyboard layout is incorrct in the case of upgrading 7.10 to 8.04
** This bug has been marked a duplicate of bug 67188
Error activating XKB
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Japanese keyboard layout is incorrct in the case of upgrading 7.10 to 8.04
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Error activating XKB configuration. It can happen under various
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Default keyboard settings are seemingly incompatible with GNOME
*** This bug is a duplicate of bug 67188 ***
https://bugs.launchpad.net/bugs/67188
** This bug has been marked a duplicate of bug 67188
Error activating XKB configuration. - Requires manual xorg.conf editing
--
Numeric keypad layout selection - Error activating XKB configuration
I can confirm this issue is occurring, however this mapping is not done
by xkeyboard-config
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: xkeyboard-config = gnome-control-center
Importance: Undecided = Medium
Status: Incomplete = Confirmed
--
sysrq and screenshot use
** Changed in: gtk2-engines (Ubuntu)
Sourcepackagename: xorg = gtk2-engines
Status: Incomplete = New
--
Menu selection causes program crash
https://bugs.launchpad.net/bugs/294167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
[This is an automated message]
Hi frankgroeneveld,
Thanks for including an image to demonstrate the issue. Could you also please
attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file
from after reproducing this issue. If you've made any customizations to your
** Changed in: totem (Ubuntu)
Sourcepackagename: xserver-xorg-video-ati = totem
--
totem-xine crashes with x error
https://bugs.launchpad.net/bugs/297135
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
desktop-bugs
Keyboard Layout Options provides dozens of different options besides
ctrl+shift for keyboard switching, and ctrl+shift is not the default
anyway. So this is not a priority for us to change in Ubuntu, but you
should feel free to raise the issue with upstream. Here's a link for
your convenience:
synaptic is not using an explicit suffix:
[EMAIL PROTECTED]:~/src/Sponsor/synaptic/synaptic-0.62.2ubuntu2$ grep -sr
'Icon=' . | grep -v .spec
./data/synaptic-kde.desktop.in:Icon=synaptic
./data/synaptic.desktop.in:Icon=synaptic
./debian/patches/02_ubuntu_desktop_file.dpatch: Icon=synaptic
**
Patched tsclient with fix.
** Changed in: tsclient (Ubuntu)
Status: Confirmed = Fix Committed
--
Use of explicit suffix in 'Icon' field of application launcher
https://bugs.launchpad.net/bugs/190688
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Sounds like just the vte patch needs sponsored, so closing the screen
task. Feel free to reopen if something else needs investigated there
(or maybe better to file a new bug).
** Changed in: screen (Ubuntu)
Status: New = Invalid
--
Backspace key in GNU Screen not detected correctly
** Changed in: vte (Ubuntu)
Status: Triaged = Fix Committed
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/29787
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Btw, I've also added a depends on hal to xserver-xorg, which should also
help reduce occurrences of this. (lool found a situation where in kvm
xorg can be launched without hal having been installed, leading to a
similar issue as this.)
--
mouse and keyboard unresponsive when gdm first runs
[This is an automated message]
Hi mjhildum,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
file from after reproducing this issue. If you've made any customizations to
your /etc/X11/xorg.conf please attach that as well.
** Changed in: xorg-server (Ubuntu)
** Changed in: xserver-xorg-input-keyboard (Ubuntu)
Status: New = Confirmed
--
Numeric keypad no longer works after upgrade
https://bugs.launchpad.net/bugs/197589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
[This is an automated message]
Hi nikratio,
Thanks for including the attached files. Could you also include your
/var/log/Xorg.0.log?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
Connection to ICE-unix/.. socket times out so programs take minutes to start
Public bug reported:
Binary package hint: gnome-terminal
ctrl-alt-q has a confirmation dialog, but ctrl-alt-w does not and can be
easily triggered for example if you aim badly when doing ctrl-a (a
common key combo in bash and console programs) and also depress the keys
above ctrl and a,
On Fri, Nov 14, 2008 at 02:23:24AM -, weboide wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I think you mean ctrl-shift- instead of ctrl-alt-.
At least to reproduce the steps, I had to use ctrl-shift-a/q/w on Intrepid
(gnome-terminal
Don't forget to correct the title as well.
On Thu, Nov 13, 2008 at 05:06:13PM -, Chris Coulson wrote:
Right, I will assign to xorg for now then
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: displayconfig-gtk = xorg-server
Status: Won't Fix = New
--
display-config
** Changed in: xkeyboard-config (Ubuntu)
Importance: Low = Wishlist
Status: Incomplete = Confirmed
--
No text editor marks text with ctr-shift-cursor
https://bugs.launchpad.net/bugs/54888
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Hi singalen,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
file from after reproducing this issue. If you've made any customizations to
your /etc/X11/xorg.conf please attach that as well.
** Changed in: xkeyboard-config (Ubuntu)
Status: New =
This isn't a bug in xkeyboard-config so closing out this task.
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xkeyboard-config (Ubuntu)
Status: New = Invalid
--
The key repeat delay for the down-arrow, left-arrow, and End keys is
longer than the
Sounds like the original issue (and many of the issues by subsequent
commenters) are fixed by the gdm priority change, so closing out the
xorg task - if I'm wrong please feel free to reopen the task with an
explanation.
** Changed in: xorg (Ubuntu)
Status: Confirmed = Fix Released
**
** Changed in: gdm (Ubuntu Intrepid)
Target: None = intrepid-updates
--
mouse and keyboard unresponsive when gdm first runs
https://bugs.launchpad.net/bugs/271138
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Confirmed
--
Virtual screen size too small when using dual head
https://bugs.launchpad.net/bugs/277948
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
** Changed in: synaptic (Ubuntu)
Importance: Undecided = Low
Status: New = Confirmed
** Changed in: thunderbird (Ubuntu)
Importance: Undecided = Low
** Changed in: tsclient (Ubuntu)
Importance: Undecided = Low
Status: New = Confirmed
--
Use of explicit suffix in 'Icon'
** Changed in: screen (Ubuntu)
Importance: Undecided = Low
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/29787
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: powernowd (Ubuntu)
Importance: Undecided = High
Status: Confirmed = Triaged
--
[hardy] Regression: powernowd no longer works with some chipsets
https://bugs.launchpad.net/bugs/223812
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Changed in: gnome-control-center (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
Target: ubuntu-8.04 = None
--
gnome-display-properties should revert change automatically if not acknowledged
https://bugs.launchpad.net/bugs/197673
You received this bug
** Changed in: xkeyboard-config (Ubuntu)
Status: Confirmed = Fix Released
--
GNOME's keyboard layout is incorrect for French canadian
https://bugs.launchpad.net/bugs/33318
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
May as well retain Jame's patch from bug #210383 until there is
documentation, no?
--
Help button in gnome-display-properties does nothing
https://bugs.launchpad.net/bugs/259942
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
tseliot, could you take a look at this?
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
--
Screen resolution capplet unnecesarily tries to set virtual resolution
https://bugs.launchpad.net/bugs/287062
You received this bug notification
Public bug reported:
Binary package hint: gnome-control-center
The Screen Resolution settings dialog is 558 pixels in vertical height.
Since the purpose of this tool is to change resolution settings, it
ought to be usable on as wide a range of resolutions as possible.
As a minimum, it should
Yep, looks good to me as a quick and safe fix.
** Attachment added: debdiff
http://launchpadlibrarian.net/19084657/32_31.diff
--
Screen resolution capplet unnecesarily tries to set virtual resolution
https://bugs.launchpad.net/bugs/287062
You received this bug notification because you are a
** Description changed:
Binary package hint: gnome-control-center
I have observed the problem when using my laptop (Compaq NC6220) with an
external monitor or projector. It can be reproduced as follows:
1. Start with both screens in mirrored (clone) mode, and with no virtual
[This is an automated message]
As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
fglrx bugs, which now includes a process for upstreaming bugs to AMD.
http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
To transition your bug into the new fglrx-package, we need
[This is an automated message]
As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
fglrx bugs, which now includes a process for upstreaming bugs to AMD.
http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
To transition your bug into the new fglrx-package, we need
[This is an automated message]
As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for
fglrx bugs, which now includes a process for upstreaming bugs to AMD.
http://bugs.launchpad.net/ubuntu/+source/fglrx-installer
To transition your bug into the new fglrx-package, we need
*** This bug is a duplicate of bug 269357 ***
https://bugs.launchpad.net/bugs/269357
** This bug is no longer a duplicate of bug 264368
[Needs EXA] totem crashes when compiz is enabled unless EXA is enabled
** This bug has been marked a duplicate of bug 269357
[Needs EXA] Video
*** This bug is a duplicate of bug 269357 ***
https://bugs.launchpad.net/bugs/269357
Since seb128 closed the totem task, no reason to keep this bug open
since it's otherwise just a dupe of 269357 anyway, and the latter has
better analysis and comments from oyvinst.
** Summary changed:
-
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this
Gdk-ERROR **: The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 91 error_code 11 request_code 140 minor_code 19)
(Note to programmers: normally, X errors are
Like the error message in comment #1's attachment points out, this is
probably a bug in the program moreso than in the video driver, however
it would be nice if the Xserver auto-reconfigured things to give the app
more memory when it needs it.
** Changed in: xorg-server (Ubuntu Intrepid)
For those using the -ati driver, also see 269357 - like I mentioned
above, if you're using XAA and experiencing this problem, switching to
EXA solves it. However we don't default to EXA yet due to various other
issues present with it. Maybe we will in Jaunty.
--
totem crashes when compiz is
Unfortunately I'm just the X guy, I'm not really intimately
knowledgeable about what's going on inside gnome-power-manager so can't
give much advice here on out.
It sort of feels like something is stealing the keyboard/mouse devices
away from X, and then the vt-switch remaps things back together
Mario suggested that this bug may be related to #261721, and that
testing against an earlier 2.6.24 kernel with the same version of gnome-
power-manager may be of use to identify if g-p-m is not bugged.
--
Losing keyboard and mouse control when changing screen brightness with fn +
arrow under
I found one of my systems reproduces the issue consistently. Of
interest, booted to root with no X, showkey does not show any output
when hitting the brightness keys, however the brightness does change
correctly.
--
Losing keyboard and mouse control when changing screen brightness with fn +
On further analysis, it's only the key release event that doesn't
produce output. Key down generates a keycode press.
And I see what's going on in X - it's not that the device itself is
stolen, just the focus. The mouse still works (you can click on the
firefox icon and launch it, interactic
Since it's narrowed to be a kernel and g-p-m issue, we can eliminate
-evdev at this point.
** Changed in: xserver-xorg-input-evdev (Ubuntu Intrepid)
Status: Incomplete = Invalid
** Changed in: gnome-power-manager (Ubuntu Intrepid)
Assignee: (unassigned) = Ted Gould (ted-gould)
--
Hi mark-mazan,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of Ubuntu?
Still seeing the mnemonics issue with 2.24.1-0ubuntu1. Reopening.
** Changed in: gnome-terminal (Ubuntu)
Status: Fix Released = Confirmed
--
[Interpid] Duplicated mnemonics in the menu
https://bugs.launchpad.net/bugs/279046
You received this bug notification because you are a member of
Given the above, and that it starts behaving once gnome-power-manager is
turned off, it's starting to sound like a bug in gnome-power-manager.
I'm adding a task for that package.
Given that your hotkeys work but the rest of the keyboard doesn't, and
that lshal output hasn't changed, it sort of
Public bug reported:
Binary package hint: gnome-terminal
man gnome-terminal lists 15 options, not counting aliases.
gnome-terminal --help lists 24 options, not counting aliases or help
options.
So the man page needs to be updated to include the missing 9 option:
--window, --tab, --use-factory,
Hi frasu,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of Ubuntu?
Hi mltruscott,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of Ubuntu?
Hi rubys,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of Ubuntu?
Hi rastaxe-gmail,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of
Hi phantom007,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest development release of Ubuntu?
Hi Elias, generally what you should do when triaging bugs like this, is
to go ahead and upstream it for the reporter, and link the bug report
here (via Also affects project - rhythmbox), and then request the
reporter subscribe to the upstream bug report.
Since this sounds like missing
Committed to git change to make xserver-xorg package depend directly on
-evdev.
** Changed in: xorg (Ubuntu Intrepid)
Status: Confirmed = Fix Committed
--
mouse and keyboard unresponsive when gdm first runs
https://bugs.launchpad.net/bugs/271138
You received this bug notification because
We had been anticipating a fix for this issue in time for intrepid from
libxcb upstream, but none was forthcoming. We did not have time during
intrepid to explore the option of de-enabling xcb in libx11 (it would
require changes to compiz and other things that now require it).
This bug has
Closing out the pygtk tasks; there was never evidence presented that it
has any relation to this bug. If you feel there's an xcb issue in
pygtk, please file a new bug.
** Changed in: pygtk (Ubuntu Hardy)
Status: New = Invalid
--
hardy, locking assertion failure, xorg/libsdl
I reviewed the change timo posted at http://users.tkk.fi/~tjaalton/dpkg
/xserver-prop.diff
It's quite a bit of code to change this late in the release. The
benefit it brings is to synchronize us with the released API. Given
that there's only a few packages that are likely to need this
Thanks for including the attached files. Could you also include your
/var/log/Xorg.0.log?
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New = Incomplete
--
Virtual screen size too small when using dual head
https://bugs.launchpad.net/bugs/277948
You received this bug
This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: New = Won't Fix
--
Switch User freezes at blank screen
https://bugs.launchpad.net/bugs/112518
You received
1. The problem with g-p-m not handling the brightness key when numlock
is set is in fact an issue local to gnome-power-manager. It's simply
neglects to grab the modifiers for the keys.
The first line of the attached patch makes the issue go away (the rest
of the patch is just instrumentation).
Public bug reported:
Binary package hint: gnome-panel
Steps to reproduce on Intrepid:
* Start firefox and open 3 new windows on different URLs
* Do File - Quit. When asked about saving tabs and windows, say yes
* Launch firefox again. When asked about restoring previous state, say yes
Hi Bruce,
In general the patch looks okay, but I notice it touches a lot of other
files unnecessarily. It appears you constructed the diff between two
different versions of g-c-c. Would you mind redoing the patch more
cleanly, so it doesn't touch so many files?
** Changed in:
Btw, the g-c-c patch needs to have its Build-Deps upped to the gnome-
desktop version, since it FTBS without the patched version now.
--
Setting the Virtual resolution should be easier
https://bugs.launchpad.net/bugs/275977
You received this bug notification because you are a member of Ubuntu
In general, X is less involved in hotkey management than before. It's
not completely out of the picture quite yet, so there's still some
chance of X interfering.
However, from what I can tell, when X is involved in handling the sleep
key, you should see something like XF86Standby listed in the
I'll plan to do some testing of this in coming days. I've reviewed the
changes in detail and think they look good. seb128 has also had a
chance to look and gave an ok for upload.
I agree this is a bug fix rather than a new feature. Note that an
earlier upload provided a preliminary fix, such
Re-closing. Muelli, you seem to have a different problem than everyone
else, please file a new bug. You can try doing so via running `ubuntu-
bug xserver-xorg-input-evdev`, which should attach the necessary files
for troubleshooting.
--
Up arrow key mapped to Print [screen]
Both screens are there, just uncheck the clone checkbox and drag the
screen to one side or another.
Feel free to reopen the bug and clarify if you think something isn't
working properly.
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: xorg = gnome-control-center
Status:
Patch has been in the upstream tracker for some time. I don't see
anything wrong with the patch, nor any comments against it here or
upstream, and it seems like a good idea, so I've gone ahead and
sponsored it for Intrepid.
** Changed in: alacarte (Ubuntu)
Status: Triaged = Fix Committed
** Attachment added: gnome-power-bugreport output
http://launchpadlibrarian.net/17568866/inspiron.txt
--
[Hardy] laptop function key + brightness keys combo activates twice if pressed
once.
https://bugs.launchpad.net/bugs/215217
You received this bug notification because you are a member of
I can reproduce this on my Inspiron 1420 with Intrepid. (I've seen this
issue since Hardy at least.)
I'm making a wild guess at filing this against gnome-power-manager, but
please refile elsewhere as appropriate.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: None =
*** This bug is a duplicate of bug 215217 ***
https://bugs.launchpad.net/bugs/215217
** This bug has been marked a duplicate of bug 215217
[Hardy] laptop function key + brightness keys combo activates twice if
pressed once.
--
fn buttons dim and brighten screen to fast
I think this might be specific to Inspirons - I was able to find another
dupe report about this bug, and the reporter also had an Inspiron 1420.
Fwiw, mine is a 1420N specifically.
--
[Hardy] laptop function key + brightness keys combo activates twice if pressed
once.
*** This bug is a duplicate of bug 245383 ***
https://bugs.launchpad.net/bugs/245383
In any case, it probably is fixed now; if you can reproduce it on
current Intrepid, feel free to undupe (or file a new bug). make sure to
include your /var/log/Xorg.0.log.
--
simply running xrandr with
Thanks
On Tue, Sep 09, 2008 at 07:54:56PM -, Pedro Fragoso wrote:
Thanks for your bug report, but this bug is already on upstream check
http://bugzilla.gnome.org/show_bug.cgi?id=548388
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
** Also affects:
Agreed a blueprint is probably more appropriate. Also, if it were done,
gdm and kdm would be sufficient; no need for xdm as well probably.
** Changed in: xdm (Ubuntu)
Status: New = Won't Fix
--
Secure attention key
https://bugs.launchpad.net/bugs/237721
You received this bug
Public bug reported:
Binary package hint: gnome-terminal
Terminal Set Title presents a dialog for entering the new title. It
should set focus on the Ok button so the dialog is dismissed when you
hit Enter.
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
--
Hi Jonathan, have you had a chance to update this with Martin's
recommendations?
--
missing man page for update-desktop-database
https://bugs.launchpad.net/bugs/160414
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in
The last several comments is doing nothing at all to help the case of
those wishing to revert libx11. Still no data about *specific* apps
with *specific* problems (backtraces or at least stderr msgs) are NOT
being posted to this bug report. If problems are so pervasive, then I
would expect it to
Btw, this bug is about XCB not XCD.
--
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 to pygtk in ubuntu.
--
desktop-bugs mailing list
fixed in g-c-c
** Changed in: xorg (Ubuntu)
Status: Triaged = Invalid
Target: ubuntu-8.04.1 = None
--
Useful dual-head configuration requires manual editing of xorg.conf to set
Virtual
https://bugs.launchpad.net/bugs/220563
You received this bug notification because you are a
I spoke with Bart Massey about this the other day, and unfortunately he
says the re-architecture work to eliminate the locking issues is delayed
and doesn't have an ETA.
However, I've word that the recent java fixes in Intrepid pretty much
resolve this issue now. I'd love hearing any
These patches look appropriate to me.
@Juan, thanks for testing them.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = Triaged
--
gnome-control-center and gnome-settings-daemon hardcode
Anyway, as per comment #5, resolution switching from the command line
seems to be working ok, so that suggests it's a bug in the Screen
Resolution applet, but without a backtrace it's hard to begin
troubleshooting on this one. The network failure makes me suspect a
kernel issue, but more
Displaying the EDID is pretty trivial, but probably wouldn't be very
meaningful to most users. It can also be obtained via xrandr --verbose,
or via the /var/log/Xorg.0.log, or via read-edid. I'm not convinced
there's much value to also having it available via the GUI, but wouldn't
turn aside a
** Changed in: xserver-xorg-driver-ati
Status: New = Invalid
--
system freezes after using Screen Resolution to set to 1440 x 900 with DVI
output (works from command line or with VGA)
https://bugs.launchpad.net/bugs/234811
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 245383 ***
https://bugs.launchpad.net/bugs/245383
** This bug has been marked a duplicate of bug 245383
Screen flickers when loading applications
--
simply running xrandr with radeon drivers makes screen flicker (also, it's slow)
According to the upstream bug, this is a problem in gtk, not in X.
Reassigning package.
If I'm not mistaken, EDID transfers are done in-band and thus will cause the
monitor to lose sync. There's really no way around it. From the recent thread
on the mailing list, it sounds like the solution is to
Seems like a kernel issue. Feel free to reopen against xorg if there's
proof it's X and not the kernel at fault.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Status: Incomplete = Invalid
--
feisty logout crash
901 - 1000 of 1256 matches
Mail list logo
