I still get many people asking me how to fix this behavior in Linux.
Since this bug is now nine years old and there seems to be no interest
in providing a "proper" fix, I've created a small shell script that
should configure your system to generate a cedilla c on '+c:
https://github.com/marcopagan
This problem hit me hard today. Problems like this definitely diminish
the user trust in the Ubuntu upgrade process.
The solution was a painful manual rollback, using the output of "dpkg
--get-selections" from before the upgrade (this old habit has saved me
in more than one occasion). Getting my s
It is an annoying problem indeed. The issue is that a lot of people in
Brazil, for example, use the ABNT-2 layout, where a separate cedilla C key
exists. Everyone else was dropped in the middle of the road with this
change.
I have a quick workaround to fix it. Just cut and past the lines below and
This seems to be resolved in Lucid. My Thinkpad X40 running Lucid can
connect with no problem to my headless server running Hardy. I didn't
test it that extensively, but it's been running for over 10 minutes
without a crash, and I ran an IRC program and a server update.
** Changed in: xorg-server
Hi Vikram,
I thought I'd made it clear in my description and forum thread, but I
guess not.
This behavior applies to an upgrade install from Intrepid to Karmic. The
only way to check if it exists in Lucid is to do an upgrade from Karmic
to Lucid, which I plan to do when Lucid is released, but not
Naturally I reported it against Karmic; Karmic is the current release
version, which is installed on my machines. When Lucid is released, I
will upgrade to it. Whether or not it works in Lucid, until then, the
Karmic package needs attention.
I realize this sounds testy, but I'm really tired of see
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => New
--
Invisible Pointer at boot - fixed by locking / unlocking screen
https://bugs.launchpad.net/bugs/475665
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-
The sad part of all this is that a lot of people are used to US-intl
generating a cedilla when accent+C is used. Curiously, there's a "New
US Intl" layout that does the same as the "regular" US-Intl. I think
the cleanest solution would be to have an "Old US Intl" or "Legacy
US-Intl" that would gene
I've started a forum thread about this; hopefully we will be able to
find more information.
http://ubuntuforums.org/showthread.php?p=8323616
** Description changed:
Binary package hint: xserver-xorg-video-intel
After updating from Jaunty to Karmic, and also when using the xserver-
xorg-
Hi Tormod,
I updgraded to Karmic yesterday, so this will be more difficult for me
to test. I will have more resources when I get home next week, so I will
look into it then.
Just a side note, Karmic has the same issue with the mouse pointer that
the x-updates package did in Jaunty - it's invisibl
The invisible pointer issue seems to be setting related. Some setting
associated with my account doesn't like the new driver configuration. I
created a new account for testing and the mouse pointer works fine
there. Anyone have an idea what setting might be messing things up?
--
[x-updates] X fai
And here's dmesg output from the boot with the working (but invisible
pointer) X
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/34285701/dmesg.txt
--
[x-updates] X fails to start with "i810 module not found" error
https://bugs.launchpad.net/bugs/458588
You received this bug no
And here's Xorg.0.log from the same boot
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/34285747/Xorg.0.log
--
[x-updates] X fails to start with "i810 module not found" error
https://bugs.launchpad.net/bugs/458588
You received this bug notification because you are a member of
I merged my minimal xorg.conf with my previous xorg.conf. Everything
appears to be working smoothly now, although I still get unwatchably
slow framerates in .MKV video. (Trying to watch .MKVs is the reason
started using the x-swat drivers in the first place.)
The weird thing is, my mouse pointer
With a minimal xorg.conf specifying the intel driver X *does* in fact
start (woohoo!) - unfortunatetly, my mouse pointer is invisible (darn!).
** Attachment added: "Xorg.0.log.minimal"
http://launchpadlibrarian.net/34284929/Xorg.0.log.minimal
--
[x-updates] X fails to start with "i810 module
Here is my dmesg output
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/34284880/dmesg.txt
--
[x-updates] X fails to start with "i810 module not found" error
https://bugs.launchpad.net/bugs/458588
You received this bug notification because you are a member of Ubuntu-X,
which is
Also note that the files that ubuntu-bug automatically attached may have
misleading information - in order to get X to start so I could file the
bug I had to revert to the xserver-xorg-video-intel package found in the
main Jaunty repositories.
Xorg.0.log.borked is the log from the failed attempt,
** Attachment added: "Xorg.0.log.borked"
http://launchpadlibrarian.net/34178331/Xorg.0.log.borked
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34178332/Dependencies.txt
** Attachment added: "LsHal.txt"
http://launchpadlibrarian.net/34178333/LsHal.txt
** Attachm
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After updating to the most recent xserver-xorg-video-intel found in the
x-swat PPA (uploaded on the 19th of October I think) X fails to start
with this error:
(EE) Failed to load module "i810" (module does not exist, 0)
This may
19 matches
Mail list logo
