[Bug 330400] Re: Mouse Accessibility with secondary click corrupts pointer

I cannot get Ubuntu to autocreate another xorg.conf file. I did recreate the problem though. So it still exists with no xorg.conf file. -- Mouse Accessibility with secondary click corrupts pointer https://bugs.launchpad.net/bugs/330400 You received this bug notification because you are a member o

[Bug 330400] Re: Mouse Accessibility with secondary click corrupts pointer

** Attachment added: "xorg.conf" http://launchpadlibrarian.net/22934242/xorg.conf -- Mouse Accessibility with secondary click corrupts pointer https://bugs.launchpad.net/bugs/330400 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 330400] Re: Mouse Accessibility with secondary click corrupts pointer

Here are the manually configured files. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/22934239/Xorg.0.log -- Mouse Accessibility with secondary click corrupts pointer https://bugs.launchpad.net/bugs/330400 You received this bug notification because you are a member of Ubuntu

[Bug 330400] [NEW] Mouse Accessibility with secondary click corrupts pointer

Public bug reported: I'm using Ubuntu 8.10 AMD64. When I go to System > Preferences > Mouse > Accessibility and select "Trigger secondary click by holding down the primary button" the pointer becomes corrupted (partially rendered by blocks and gaps). I wanted to show you what it looked like, but

[Bug 200447] Re: qemulator.py crashed with IndexError in on_comboboxMachinetype_changed()

*** This bug is a duplicate of bug 132720 *** https://bugs.launchpad.net/bugs/132720 ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/12535713/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/12535714/ProcMaps.txt ** Attachment ad

[Bug 200447] [NEW] qemulator.py crashed with IndexError in on_comboboxMachinetype_changed()

*** This bug is a duplicate of bug 132720 *** https://bugs.launchpad.net/bugs/132720 Public bug reported: Binary package hint: qemulator 1) Ubuntu 8.04 alpha 6 2) Qemulator 3) 0.5-3 4) Expected to launch Win XP in qemu 5) Qemulator successfully launched. When I pressed play to start the virt

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

This time the install succeeded (as expected). Here are the same logs as above, just for good measure. ** Attachment added: "/var/log/syslog" http://launchpadlibrarian.net/8783929/syslog -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/126029 You

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

As expected the above install failed. I just installed tribe 4 with the HDDs unplugged. Here are the same logs. ** Attachment added: "/var/log/syslog" http://launchpadlibrarian.net/8783904/syslog -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/12

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

** Attachment added: "/var/log/installer/debug" http://launchpadlibrarian.net/8783909/debug -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/126029 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contac

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

** Attachment added: "/var/log/partman" http://launchpadlibrarian.net/8783906/partman -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/126029 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

** Attachment added: "/var/log/partman" http://launchpadlibrarian.net/8783799/partman -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/126029 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

** Attachment added: "/var/log/installer/debug" http://launchpadlibrarian.net/8783801/debug -- Gutsy on AMD64 does not properly install with multiple HDDs https://bugs.launchpad.net/bugs/126029 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contac

[Bug 126029] Re: Gutsy on AMD64 does not properly install with multiple HDDs

Sorry it took me so long to post more info. In the mean time, I have reinstalled using Gutsy tribe3 both amd64 and x86. Both times it failed when the extra HDDs were plugged in. Once I tried installing with the HDDs, then unplugging them, then restarting. That didn't work either. Here are the logs

[Bug 126029] Gutsy on AMD64 does not properly install with multiple HDDs

Public bug reported: Hardware config: AMD64, sda (primary), hda, hdb, hdc All HDDs have ext3 The Gutsy AMD64 Tribe2 LiveCD recognized and mounted all my HDDs. Three Gutsy install options exist, % of disk, guided, and manual. I installed Gutsy using % and guided. I tried to use manual too, but it

[Bug 105350] [apport] Tomboy.exe crashed with SIGSEGV in _Unwind_ForcedUnwind()

Public bug reported: Binary package hint: tomboy crashes when booting up. ProblemType: Crash Architecture: amd64 Date: Tue Apr 10 00:09:40 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/tomboy/Tomboy.exe InterpreterPath: /usr/bin/mono Package: tomboy 0.6.1-0ubuntu1 PackageArchitecture:

[Bug 105350] Re: [apport] Tomboy.exe crashed with SIGSEGV in _Unwind_ForcedUnwind()

** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7258984/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7258985/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/7258986/Disassembly.txt ** Attachm

[Bug 74206] crashes on launch

Public bug reported: Hardware: Athlon64 3700+, A8N5X (MoBo), nForce 4, Mem - 2 GB Software: 6.10 (Edgy) AMD64 1. open freecraft through terminal 2. Terminal displays > FreeCraft default config file loading ... > 640 > 480 > 800 > 600 > 1024 > 768 > 1280 > 960 > 1600 > 1200 > ... ready! > FreeCra