I confirm this bug. I have a workaround instead of sudo killall tsclient
from another tty. If you press the windows key you can being up the
start menu on the remote computer and log off. This releases the screen
back to you. You can then reconnect by pressing OK instead of using the
enter key.
--
I experienced the same Ubiquity crash when the installer unmounted a
partition to make it available for the installer. The partition was on a
SATA disk.
I also completely agree with danielhollocher above on the wording of the
buttons - they should read 'unmount volume and continue' and 'continue
w
This problem still exists in Lucid Beta 2. I replicated this exactly on
my Acer Aspire Revo R3600 - X crashes and causes a total system hang. I
can boot from the Lucid live cd but only by using the "nomodeset
xforcevesa" options...
Chewit: can you advise the workaround you used to get Lucid bootin
I would like to request that Ubuntu goes in its own direction regarding
this bug - seems like an obvious paper cut to me. If a new Ubuntu user
has accidentlly removed both panels, it is extremely difficult to get
them back and I could easily see it leading to a reinstall. If there is
only one panel
Version 2.31.90 here, bug still exists. The dialog box has dimensions
larger than my screen resolution and there is no scroll bar and no
visible add button. I notice I can tab to things on the dialog that are
invisible. But pressing the space bar on the hidden elements doesn't do
anything.
It woul
I experienced the same problem on a Samsung NC210 netbook. The screen
where you can select a profile photo or take one with the webcam has
buttons which are completely off-screen on a 1024z600 resolution
monitor. You can tab to an 'invisible' button and press enter to
proceed, blindly guessing that
This bug can be closed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878797
Title:
Internal error installing a .deb is not verbose enough
To manage notifications about this bug go to:
http
Public bug reported:
Downloaded a .deb file from www.google.com/chrome. Double clicked it,
and Software Centre opened. An error appears which says "Internal Error.
The file "/path/to/chrome.deb" could not be opened."
The message is not verbose and doesn't explain what can be done to fix
it.
When
** Description changed:
Downloaded a .deb file from www.google.com/chrome. Double clicked it,
and Software Centre opened. An error appears which says "Internal Error.
The file "/path/to/chrome.deb" could not be opened."
+
+ The message is not verbose and doesn't explain what can be done to
This can be closed as it's no longer an issue for me on 11.04. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645546
Title:
stereo bluetooth devices not working properly
To manage notifications
Here's a crappy workaround for people on 'classic mode' that have the
problem.
Launch skype
Open applications - terminal, and type: killall gnome-panel
This fixes the problem for Skype and Shutter, not sure about other apps
that use the notification area.
--
You received this bug notification b
Public bug reported:
Binary package hint: pulseaudio
Hi,
I don't know whether this is a pulseaudio thing, I suspect it's a
problem in the bluetooth stack or could be a laptop hardware
compatibility issue.
I have a couple of bluetooth devices, both stereo headphones: Nokia
BH503 and Nokia BH905,
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/645546/+attachment/1624291/+files/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/645546/+attachment/1624292/+files/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
Hi, not sure if that is related to this bug. I'm not experiencing
skipping - it just plays in low quality, kind of sounds like the
speakers are underwater.
--
stereo bluetooth devices not working properly
https://bugs.launchpad.net/bugs/645546
You received this bug notification because you are a
14 matches
Mail list logo
