It seems this was fixed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=70348
http://lists.freedesktop.org/archives/pixman/2013-October/003077.html
** Bug watch added: freedesktop.org Bugzilla #70348
https://bugs.freedesktop.org/show_bug.cgi?id=70348
--
You received this bug notificati
This modification wasn't really asked for. XFree86/Xorg (xkb?) have always
worked the way this report asks, until a couple of years.
You don't need a Brazilian Windows. You just need a US keyboard and make '
(apostrophe) followed by C output a Ç.
--
Please add Microsoft compatible keyboard layo
Ok, thanks. Actually I just filed this bug because at the time "radeon"
wasn't working for me either. "radeon" is working much better now, and I
had actually forgotten completely about this bug entry :-$
--
glxinfo crashed with SIGSEGV in glXMakeCurrentReadSGI()
https://bugs.launchpad.net/bugs/51
I confirm. After all those kernel, firmware, drm and xorg updates, X is finally
working with modeset & dri & glx :-)
The only issue I have is that the first login attempt always falls back to
login screen. Also I've experienced two hard freezes since the last relevant
update (about a week or so,
Eduardo Ceretos' approach (if I understand it) is the correct one: to create a
different layout for 'Brazil' model and let US model alone. There several
completely different (and completely irrelevant) layouts for Brazil model like
all "Nativo" variants (I can't speak for Dvorak and Esperanto, t
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38851088/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/38851089/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38851090/Dependencies.txt
** Attachment
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38850843/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/38850844/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38850845/Dependencies.txt
** Attachment
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38834691/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/38834692/CoreDump.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38834693/CurrentDmesg.txt
** Attachment
/usr/lib/failsafe-x? ;)
--
Failsafe X stuff shouldn't be stored in /etc/gdm
https://bugs.launchpad.net/bugs/480744
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: https:/
If it was always overwritten, what would be use for its existence?
BTW, failsafe X works without it, right? I vaguely remember trying it, but...
--
Failsafe X doesn't always overwrite /etc/X11/xorg.conf.failsafe
https://bugs.launchpad.net/bugs/480747
You received this bug notification because you
Public bug reported:
Binary package hint: xorg
failsafeX doesn't have an option to restart X after editing the
configuration. Also it doesn't have an option to restart the system, so
the user is thrown back to the console.
Offtopic, but I guess obvious enough for someone who'd reply to this repo
To the OP: do you happen to have a rtl8187 wireless "card"?
--
Suspend broken
https://bugs.launchpad.net/bugs/164342
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
__
12 matches
Mail list logo