When I run Kubuntu Jaunty from the LiveCD, I just cannot connect to my
wireless network (which uses a WEP key)--not even if I start the KDE
Wallet first.
After installation, I *can* connect, but it doesn't work as flawlessly
as it should: It will ask for my (hex) WEP key twice--but, since that's
j
Update:
Currently (running Ubuntu 8.10, fully updated as per 2009-02-14), I can no
longer reproduce the problem.
USB works perfectly now.
I guess this solves the problem for me.
Note:
Under 8.04, USB still won't work (cfr.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/254589), but since
** Attachment added: "calltrace.txt"
http://launchpadlibrarian.net/29772738/calltrace.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
https://bugs.launchpad.net/bugs/407660
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
I installed UbuntuStudio 9.04 from the "ubuntustudio-9.04-alternate-
amd64.iso" DVD.
The installation went OK, but as soon as I boot up the computer, it
displays a Call Trace and locks up. The only way out is a hard reset.
I subsequently installed the real-time kernel 2.6.28
I'm attaching the output from the "cpuid" command.
(The command was run under Ubuntu 8.10 on one of the machines on which I
attempted to run UbuntuStudio 9.04).
** Attachment added: "cpuid.txt"
http://launchpadlibrarian.net/29772755/cpuid.txt
--
Real-Time Kernel won't boot on my AMD Athlon 6
I'm also attaching the output of the "lshw" command (run on the same computer).
The motherboard is a Gigabyte GA-MA78G-DS3H.
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/29772777/lshw.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
h
> I can actually get it to fully boot if I pass the nolapic option and
disable the lan in the bios.
Hmmm... That doesn't work for me. I simply get a message stating that
the local APIC cannot be found, after which my system still locks up.
Enabling or disabling the LAN in BIOS doesn't change a thi
> with the nolapic option does the system still lock up with the same
tick_handle_periodic() trace?
Nope... No trace. The only output that appears on screen, is the
following two lines:
[0.212982] BIOS bug, local APIC #0 not detected!...
[0.213018] ... forcing use of dummy APIC emulation.
> with the nolapic option does the system still lock up with the same
tick_handle_periodic() trace?
Nope... No trace. The only output that appears on screen, is the
following two lines:
[0.212982] BIOS bug, local APIC #0 not detected!...
[0.213018] ... forcing use of dummy APIC emulation.
I have been testing Fedora 10 (the KDE version) for a few days now, and
I cannot reproduce this problem there.
So, it's a problem with either Ubuntu 8.10, or GNOME. To know for sure,
I would have to test it under Kubuntu 8.10 as well; if I can get around
to doing so, I'll report my findings here.
I'm having this very same problem, on two computers with nearly
identical hardware: Same brand and type of motherboard, same (AMD64)
CPU, same types and capacities of harddisks, same brand and type of DVD
drive.
They both have three USB hubs connected to them:
- A four-port external STLab USB 2.0
For reference: This attachment ("lshw_silverstone_cd.txt") is the
complete output from the "lshw" command, after I booted from the Ubuntu
8.04 Live CD, and connected a USB stick to the Silverstone hub.
** Attachment added: "lshw_silverstone_cd.txt"
http://launchpadlibrarian.net/19943844/lshw_si
For reference: This attachment ("lshw_silverstone_hd.txt") is the
complete output from the "lshw" command, after I booted Ubuntu 8.04
(fully updated) from harddisk, and connected a USB stick to the
Silverstone hub.
I didn't have to run the "lsusb" command, since the Silverstone hub
functions norm
> change your preferences in your video player to output via "x11".
An earlier comment here explained how to do that in various video players:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/179042/comments/25
This is really just a work-around, not a real fix, though.
Basically, t
Public bug reported:
In an attempt to solve the stability issues with Firefox and the Flash
plugin, and to allow simultaneous access to the sound hardware by
multiple applications, I followed parts A and B of the Ubuntu Forum post
at http://ubuntuforums.org/showthread.php?p=4928900. Actually, I ra
** Attachment added: "pulse-audio-fixes"
http://launchpadlibrarian.net/16133117/pulse-audio-fixes
--
flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
https://bugs.launchpad.net/bugs/249553
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: openoffice.org (Ubuntu)
Status: New => Invalid
--
Open Office breaks Plasma
https://bugs.launchpad.net/bugs/226833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
For me, numlockx *does* correctly handle the keyboard led, at least
under Ubuntu.
Under *Xubuntu* however, the led will NOT get lit. This has the rather strange
effect that:
- If I use numlockx to turn NumLock on, then the numeric keypad will become
functional, but the led will remain off;
- If
The suggestion made by Cipher_no1 above, does work: Turning on NumLock from
"/etc/gdm/Init/Default" *will* turn on the keyboard LED.
Once the xfce environment is loaded, however, the "numlockx" utility will no
longer touch the LED.
For me, this is an acceptable work-around for this issue--NumLoc
Martin-Éric Racine wrote:
> Hence why I am veering towards blaming XFCE for skipping the X startup
script.
I don't think that XFCE is skipping the startup script: After I
installed numlockx on Xubuntu, the numeric keypad did become functional
upon login--but the keyboard LED did not get lit.
It
Note: The same issue happens under Kubuntu (the KDE3 generation; haven't
tested with Kubuntu Remix yet).
Thus:
- Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine;
- Under Xubuntu (xfce), numlockx will not control the LED; however, you can run
"numlockx on" from the "/etc/gdm/Init
Public bug reported:
Running Kubuntu-kde4 8.04, with OpenOffice.org 2.4.0 (everything is installed
from the repositories).
When OpenOffice.org is open and is the foreground application, the systembar
and menu get corrupted (cfr. attached screenshot, where the menu is terribly
mangled).
Display
** Attachment added: "Screenshot.png"
http://launchpadlibrarian.net/14347139/Screenshot.png
--
Systembar and menu get corrupted if OpenOffice.org is the foreground application
https://bugs.launchpad.net/bugs/227924
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Still present in Ubuntu 8.10 with gdm package version 2.20.8-0ubuntu3 as well.
The workaround, as described by Nils-Anders Nøttseter above, still works.
--
Cannot change option "Use 24 Hour Clock" for login screen
https://bugs.launchpad.net/bugs/256283
You received this bug notification because y
Public bug reported:
Binary package hint: udev
Ubuntu Release: Ubuntu 8.10 (Intrepid Ibex), fully updated as per
2008-11-16.
When the system performs many I/O operations on a USB disk in quick succession,
I/O errors tend to get reported, and the device will get "not cleanly
unmounted."
The "su
** Attachment added: "dmesg"
http://launchpadlibrarian.net/19700118/dmesg
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
After I ran into the problem, I booted into Slackware, connected the USB disk,
and ran "fsck" on it.
The output from "fsck" reported that the device "was not cleanly unmounted,
check forced."
(Cfr. the "fsck" file attached.)
(Note that Slackware identifies the disk as "/dev/sdd," while Ubuntu
ca
** Attachment added: "fsck"
http://launchpadlibrarian.net/19700208/fsck
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "Input/Output errors as reported by unison."
http://launchpadlibrarian.net/19700243/unison-errors
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bug
Looks to me like GRUB doesn't want to be installed onto the Boot Block
of a partition; it wants to be installed onto the Master Boot Block of a
disk.
Now, when you manually install GRUB onto the Boot Block of a partition
(using the GRUB "setup" command), it displays a warning about being
unable to
My suspicion that GRUB won't install onto the Boot Block of a partition,
doesn't turn out to hold water.
I did a reinstall with GRUB on the Boot Block of the root partition, and this
time it worked fine.
The difference: This time I installed everything into one single partition; I
did not config
In my case, it cannot be a question of "the existing grub multiboot
partition being back-level," because I install GRUB into the root
partition that I'm creating. I even install the GRUB boot loader
("stage1") into the Boot Block of the root partition (NOT in the Master
Boot Block--I use a custom-c
I agree with Jonathan Thomas that this must be an nVIDIA driver problem.
It doesn't happen on a (newly assembled) AMD64 system with an ATI graphics
adapter.
--
MASTER - nvidia drivers + OO.o trigger plasma drawing artifacts
https://bugs.launchpad.net/bugs/226833
You received this bug notificatio
Forget about this bug... I have just upgraded my PC hardware to an AMD64
CPU with an onboard ATI video chip, and the problem is gone: After I ran
my pulse-audio-fixes script, the http://www.metacafe.com site works
flawlessly.
I'm not sure what could have caused the problems in the first place--the
** Changed in: openoffice.org (Ubuntu)
Status: New => Invalid
--
Open Office breaks Plasma
https://bugs.launchpad.net/bugs/226833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Public bug reported:
In an attempt to solve the stability issues with Firefox and the Flash
plugin, and to allow simultaneous access to the sound hardware by
multiple applications, I followed parts A and B of the Ubuntu Forum post
at http://ubuntuforums.org/showthread.php?p=4928900. Actually, I ra
** Attachment added: "pulse-audio-fixes"
http://launchpadlibrarian.net/16133117/pulse-audio-fixes
--
flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
https://bugs.launchpad.net/bugs/249553
You received this bug notification because you are a member of Ubuntu
Bugs, which
For me, numlockx *does* correctly handle the keyboard led, at least
under Ubuntu.
Under *Xubuntu* however, the led will NOT get lit. This has the rather strange
effect that:
- If I use numlockx to turn NumLock on, then the numeric keypad will become
functional, but the led will remain off;
- If
The suggestion made by Cipher_no1 above, does work: Turning on NumLock from
"/etc/gdm/Init/Default" *will* turn on the keyboard LED.
Once the xfce environment is loaded, however, the "numlockx" utility will no
longer touch the LED.
For me, this is an acceptable work-around for this issue--NumLoc
Martin-Éric Racine wrote:
> Hence why I am veering towards blaming XFCE for skipping the X startup
script.
I don't think that XFCE is skipping the startup script: After I
installed numlockx on Xubuntu, the numeric keypad did become functional
upon login--but the keyboard LED did not get lit.
It
Note: The same issue happens under Kubuntu (the KDE3 generation; haven't
tested with Kubuntu Remix yet).
Thus:
- Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine;
- Under Xubuntu (xfce), numlockx will not control the LED; however, you can run
"numlockx on" from the "/etc/gdm/Init
I agree with Jonathan Thomas that this must be an nVIDIA driver problem.
It doesn't happen on a (newly assembled) AMD64 system with an ATI graphics
adapter.
--
MASTER - nvidia drivers + OO.o trigger plasma drawing artifacts
https://bugs.launchpad.net/bugs/226833
You received this bug notificatio
Forget about this bug... I have just upgraded my PC hardware to an AMD64
CPU with an onboard ATI video chip, and the problem is gone: After I ran
my pulse-audio-fixes script, the http://www.metacafe.com site works
flawlessly.
I'm not sure what could have caused the problems in the first place--the
Still present in Ubuntu 8.10 with gdm package version 2.20.8-0ubuntu3 as well.
The workaround, as described by Nils-Anders Nøttseter above, still works.
--
Cannot change option "Use 24 Hour Clock" for login screen
https://bugs.launchpad.net/bugs/256283
You received this bug notification because y
I have been testing Fedora 10 (the KDE version) for a few days now, and
I cannot reproduce this problem there.
So, it's a problem with either Ubuntu 8.10, or GNOME. To know for sure,
I would have to test it under Kubuntu 8.10 as well; if I can get around
to doing so, I'll report my findings here.
Looks to me like GRUB doesn't want to be installed onto the Boot Block
of a partition; it wants to be installed onto the Master Boot Block of a
disk.
Now, when you manually install GRUB onto the Boot Block of a partition
(using the GRUB "setup" command), it displays a warning about being
unable to
My suspicion that GRUB won't install onto the Boot Block of a partition,
doesn't turn out to hold water.
I did a reinstall with GRUB on the Boot Block of the root partition, and this
time it worked fine.
The difference: This time I installed everything into one single partition; I
did not config
I'm having this very same problem, on two computers with nearly
identical hardware: Same brand and type of motherboard, same (AMD64)
CPU, same types and capacities of harddisks, same brand and type of DVD
drive.
They both have three USB hubs connected to them:
- A four-port external STLab USB 2.0
For reference: This attachment ("lshw_silverstone_cd.txt") is the
complete output from the "lshw" command, after I booted from the Ubuntu
8.04 Live CD, and connected a USB stick to the Silverstone hub.
** Attachment added: "lshw_silverstone_cd.txt"
http://launchpadlibrarian.net/19943844/lshw_si
For reference: This attachment ("lshw_silverstone_hd.txt") is the
complete output from the "lshw" command, after I booted Ubuntu 8.04
(fully updated) from harddisk, and connected a USB stick to the
Silverstone hub.
I didn't have to run the "lsusb" command, since the Silverstone hub
functions norm
In my case, it cannot be a question of "the existing grub multiboot
partition being back-level," because I install GRUB into the root
partition that I'm creating. I even install the GRUB boot loader
("stage1") into the Boot Block of the root partition (NOT in the Master
Boot Block--I use a custom-c
Public bug reported:
Binary package hint: udev
Ubuntu Release: Ubuntu 8.10 (Intrepid Ibex), fully updated as per
2008-11-16.
When the system performs many I/O operations on a USB disk in quick succession,
I/O errors tend to get reported, and the device will get "not cleanly
unmounted."
The "su
** Attachment added: "dmesg"
http://launchpadlibrarian.net/19700118/dmesg
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
After I ran into the problem, I booted into Slackware, connected the USB disk,
and ran "fsck" on it.
The output from "fsck" reported that the device "was not cleanly unmounted,
check forced."
(Cfr. the "fsck" file attached.)
(Note that Slackware identifies the disk as "/dev/sdd," while Ubuntu
ca
** Attachment added: "fsck"
http://launchpadlibrarian.net/19700208/fsck
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "Input/Output errors as reported by unison."
http://launchpadlibrarian.net/19700243/unison-errors
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
Running Kubuntu-kde4 8.04, with OpenOffice.org 2.4.0 (everything is installed
from the repositories).
When OpenOffice.org is open and is the foreground application, the systembar
and menu get corrupted (cfr. attached screenshot, where the menu is terribly
mangled).
Display
** Attachment added: "Screenshot.png"
http://launchpadlibrarian.net/14347139/Screenshot.png
--
Systembar and menu get corrupted if OpenOffice.org is the foreground application
https://bugs.launchpad.net/bugs/227924
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Update:
Currently (running Ubuntu 8.10, fully updated as per 2009-02-14), I can no
longer reproduce the problem.
USB works perfectly now.
I guess this solves the problem for me.
Note:
Under 8.04, USB still won't work (cfr.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/254589), but since
> change your preferences in your video player to output via "x11".
An earlier comment here explained how to do that in various video players:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/179042/comments/25
This is really just a work-around, not a real fix, though.
Basically, t
I have been testing Fedora 10 (the KDE version) for a few days now, and
I cannot reproduce this problem there.
So, it's a problem with either Ubuntu 8.10, or GNOME. To know for sure,
I would have to test it under Kubuntu 8.10 as well; if I can get around
to doing so, I'll report my findings here.
When I run Kubuntu Jaunty from the LiveCD, I just cannot connect to my
wireless network (which uses a WEP key)--not even if I start the KDE
Wallet first.
After installation, I *can* connect, but it doesn't work as flawlessly
as it should: It will ask for my (hex) WEP key twice--but, since that's
j
Update:
Currently (running Ubuntu 8.10, fully updated as per 2009-02-14), I can no
longer reproduce the problem.
USB works perfectly now.
I guess this solves the problem for me.
Note:
Under 8.04, USB still won't work (cfr.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/254589), but since
When I run Kubuntu Jaunty from the LiveCD, I just cannot connect to my
wireless network (which uses a WEP key)--not even if I start the KDE
Wallet first.
After installation, I *can* connect, but it doesn't work as flawlessly
as it should: It will ask for my (hex) WEP key twice--but, since that's
j
** Attachment added: "calltrace.txt"
http://launchpadlibrarian.net/29772738/calltrace.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
https://bugs.launchpad.net/bugs/407660
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
I installed UbuntuStudio 9.04 from the "ubuntustudio-9.04-alternate-
amd64.iso" DVD.
The installation went OK, but as soon as I boot up the computer, it
displays a Call Trace and locks up. The only way out is a hard reset.
I subsequently installed the real-time kernel 2.6.28
I'm attaching the output from the "cpuid" command.
(The command was run under Ubuntu 8.10 on one of the machines on which I
attempted to run UbuntuStudio 9.04).
** Attachment added: "cpuid.txt"
http://launchpadlibrarian.net/29772755/cpuid.txt
--
Real-Time Kernel won't boot on my AMD Athlon 6
I'm also attaching the output of the "lshw" command (run on the same computer).
The motherboard is a Gigabyte GA-MA78G-DS3H.
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/29772777/lshw.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
h
> I can actually get it to fully boot if I pass the nolapic option and
disable the lan in the bios.
Hmmm... That doesn't work for me. I simply get a message stating that
the local APIC cannot be found, after which my system still locks up.
Enabling or disabling the LAN in BIOS doesn't change a thi
> with the nolapic option does the system still lock up with the same
tick_handle_periodic() trace?
Nope... No trace. The only output that appears on screen, is the
following two lines:
[0.212982] BIOS bug, local APIC #0 not detected!...
[0.213018] ... forcing use of dummy APIC emulation.
> with the nolapic option does the system still lock up with the same
tick_handle_periodic() trace?
Nope... No trace. The only output that appears on screen, is the
following two lines:
[0.212982] BIOS bug, local APIC #0 not detected!...
[0.213018] ... forcing use of dummy APIC emulation.
Public bug reported:
In an attempt to solve the stability issues with Firefox and the Flash
plugin, and to allow simultaneous access to the sound hardware by
multiple applications, I followed parts A and B of the Ubuntu Forum post
at http://ubuntuforums.org/showthread.php?p=4928900. Actually, I ra
** Attachment added: "pulse-audio-fixes"
http://launchpadlibrarian.net/16133117/pulse-audio-fixes
--
flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
https://bugs.launchpad.net/bugs/249553
You received this bug notification because you are a member of Ubuntu
Bugs, which
I agree with Jonathan Thomas that this must be an nVIDIA driver problem.
It doesn't happen on a (newly assembled) AMD64 system with an ATI graphics
adapter.
--
MASTER - nvidia drivers + OO.o trigger plasma drawing artifacts
https://bugs.launchpad.net/bugs/226833
You received this bug notificatio
Forget about this bug... I have just upgraded my PC hardware to an AMD64
CPU with an onboard ATI video chip, and the problem is gone: After I ran
my pulse-audio-fixes script, the http://www.metacafe.com site works
flawlessly.
I'm not sure what could have caused the problems in the first place--the
** Changed in: openoffice.org (Ubuntu)
Status: New => Invalid
--
Open Office breaks Plasma
https://bugs.launchpad.net/bugs/226833
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
For me, numlockx *does* correctly handle the keyboard led, at least
under Ubuntu.
Under *Xubuntu* however, the led will NOT get lit. This has the rather strange
effect that:
- If I use numlockx to turn NumLock on, then the numeric keypad will become
functional, but the led will remain off;
- If
The suggestion made by Cipher_no1 above, does work: Turning on NumLock from
"/etc/gdm/Init/Default" *will* turn on the keyboard LED.
Once the xfce environment is loaded, however, the "numlockx" utility will no
longer touch the LED.
For me, this is an acceptable work-around for this issue--NumLoc
Martin-Éric Racine wrote:
> Hence why I am veering towards blaming XFCE for skipping the X startup
script.
I don't think that XFCE is skipping the startup script: After I
installed numlockx on Xubuntu, the numeric keypad did become functional
upon login--but the keyboard LED did not get lit.
It
Note: The same issue happens under Kubuntu (the KDE3 generation; haven't
tested with Kubuntu Remix yet).
Thus:
- Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine;
- Under Xubuntu (xfce), numlockx will not control the LED; however, you can run
"numlockx on" from the "/etc/gdm/Init
Public bug reported:
Running Kubuntu-kde4 8.04, with OpenOffice.org 2.4.0 (everything is installed
from the repositories).
When OpenOffice.org is open and is the foreground application, the systembar
and menu get corrupted (cfr. attached screenshot, where the menu is terribly
mangled).
Display
** Attachment added: "Screenshot.png"
http://launchpadlibrarian.net/14347139/Screenshot.png
--
Systembar and menu get corrupted if OpenOffice.org is the foreground application
https://bugs.launchpad.net/bugs/227924
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Binary package hint: udev
Ubuntu Release: Ubuntu 8.10 (Intrepid Ibex), fully updated as per
2008-11-16.
When the system performs many I/O operations on a USB disk in quick succession,
I/O errors tend to get reported, and the device will get "not cleanly
unmounted."
The "su
** Attachment added: "dmesg"
http://launchpadlibrarian.net/19700118/dmesg
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
After I ran into the problem, I booted into Slackware, connected the USB disk,
and ran "fsck" on it.
The output from "fsck" reported that the device "was not cleanly unmounted,
check forced."
(Cfr. the "fsck" file attached.)
(Note that Slackware identifies the disk as "/dev/sdd," while Ubuntu
ca
** Attachment added: "fsck"
http://launchpadlibrarian.net/19700208/fsck
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "Input/Output errors as reported by unison."
http://launchpadlibrarian.net/19700243/unison-errors
--
I/O errors on USB device - device is not cleanly unmounted
https://bugs.launchpad.net/bugs/298797
You received this bug notification because you are a member of Ubuntu
Bug
Looks to me like GRUB doesn't want to be installed onto the Boot Block
of a partition; it wants to be installed onto the Master Boot Block of a
disk.
Now, when you manually install GRUB onto the Boot Block of a partition
(using the GRUB "setup" command), it displays a warning about being
unable to
My suspicion that GRUB won't install onto the Boot Block of a partition,
doesn't turn out to hold water.
I did a reinstall with GRUB on the Boot Block of the root partition, and this
time it worked fine.
The difference: This time I installed everything into one single partition; I
did not config
Still present in Ubuntu 8.10 with gdm package version 2.20.8-0ubuntu3 as well.
The workaround, as described by Nils-Anders Nøttseter above, still works.
--
Cannot change option "Use 24 Hour Clock" for login screen
https://bugs.launchpad.net/bugs/256283
You received this bug notification because y
I'm having this very same problem, on two computers with nearly
identical hardware: Same brand and type of motherboard, same (AMD64)
CPU, same types and capacities of harddisks, same brand and type of DVD
drive.
They both have three USB hubs connected to them:
- A four-port external STLab USB 2.0
For reference: This attachment ("lshw_silverstone_cd.txt") is the
complete output from the "lshw" command, after I booted from the Ubuntu
8.04 Live CD, and connected a USB stick to the Silverstone hub.
** Attachment added: "lshw_silverstone_cd.txt"
http://launchpadlibrarian.net/19943844/lshw_si
For reference: This attachment ("lshw_silverstone_hd.txt") is the
complete output from the "lshw" command, after I booted Ubuntu 8.04
(fully updated) from harddisk, and connected a USB stick to the
Silverstone hub.
I didn't have to run the "lsusb" command, since the Silverstone hub
functions norm
In my case, it cannot be a question of "the existing grub multiboot
partition being back-level," because I install GRUB into the root
partition that I'm creating. I even install the GRUB boot loader
("stage1") into the Boot Block of the root partition (NOT in the Master
Boot Block--I use a custom-c
Public bug reported:
In an attempt to solve the stability issues with Firefox and the Flash
plugin, and to allow simultaneous access to the sound hardware by
multiple applications, I followed parts A and B of the Ubuntu Forum post
at http://ubuntuforums.org/showthread.php?p=4928900. Actually, I ra
** Attachment added: "pulse-audio-fixes"
http://launchpadlibrarian.net/16133117/pulse-audio-fixes
--
flashplugin-nonfree Version 10 beta won't properly play ".swf" contents
https://bugs.launchpad.net/bugs/249553
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "calltrace.txt"
http://launchpadlibrarian.net/29772738/calltrace.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
https://bugs.launchpad.net/bugs/407660
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
I installed UbuntuStudio 9.04 from the "ubuntustudio-9.04-alternate-
amd64.iso" DVD.
The installation went OK, but as soon as I boot up the computer, it
displays a Call Trace and locks up. The only way out is a hard reset.
I subsequently installed the real-time kernel 2.6.28
I'm attaching the output from the "cpuid" command.
(The command was run under Ubuntu 8.10 on one of the machines on which I
attempted to run UbuntuStudio 9.04).
** Attachment added: "cpuid.txt"
http://launchpadlibrarian.net/29772755/cpuid.txt
--
Real-Time Kernel won't boot on my AMD Athlon 6
I'm also attaching the output of the "lshw" command (run on the same computer).
The motherboard is a Gigabyte GA-MA78G-DS3H.
** Attachment added: "lshw.txt"
http://launchpadlibrarian.net/29772777/lshw.txt
--
Real-Time Kernel won't boot on my AMD Athlon 64 X2 Dual Core - Displays Call
Trace
h
1 - 100 of 204 matches
Mail list logo
