Although I am using a fresh installation of Ubuntu 8.10 on Toshiba
Portege M200, I can confirm that I experienced identical symptoms as a
consequence of installing "irda-utils". The "/etc/init.d/irda-setup"
script in my case runs "modprobe smsc-ircc2" what somehow breaks
"/dev/ttyS0" (does this als
For Toshiba Portege M200: Isn't the root problem located in the fact
that acpid doesn't trigger an event when you rotate? I can't see
anything on the acpi_listen output, but if I check the contents of
/proc/acpi/button/lid/LID/state the state changes from "open" to
"closed". It seems that acpid doe
I haven't written a patch. In my specific situation I am trying to use
an encrypted swap (it would be the same for any other partition type)
*without* LUKS (and without UUIDs - it doesn't really matter). And
current code just freezes the boot process and waits for the timeout
(because vol_id can't
I think that this fix is not good in all circumstances. The problem lies
in the fact that the "waiting loop" for encrypted devices is NOT the
same as for unencrypted devices. In case you are using LUKS everything
is OK, because there is a container vol_id can detect, but if you are
encrypting with
The alternative workaround does not seem to work anymore in Ubuntu 8.10.
Switch to vt1 makes usplash go away, but there is no way to get the
cryptsetup prompt and also blindly typing the password in any of the vts
doesn't work...
--
boot-time encryption password prompt can be lost
https://bugs.la
Public bug reported:
Binary package hint: usplash-theme-ubuntu
Visually the text gets corrupted if you enter a long input text when a
script wants it. I noticed this when using cryptroot that asks me (via
askpass) for a password that in my case is quite long and doesn't fit in
the line (gets wrap
In /etc/fstab you must use /dev/mapper/ entries, because this is
what you mount. Afaik the UUID= entries placed in /etc/crypttab should
work, as should LABEL= entries and also direct /dev/XdaY.
Did you misunderstand how it all works or is it still a bug? If so, then
include all configuration files
Public bug reported:
Binary package hint: cryptsetup
I would like to suggest a modification that would allow someone to have
multiple keyscript entries in crypttab. In addition there should also be an
added keystdout filed and also multiple key fields (for each keyscript one).
All the keyscrip
Public bug reported:
Binary package hint: policykit-gnome
I would suggest that in case of only one authorized user for a specific
task he should be automatically selected. And not that you need to first
click on the "Select user..." to set it - what is annoying.
Reproduce:
- Probably not essenti
Public bug reported:
Binary package hint: gdm-guest-session
I noticed that the guest-session user gets assigned UID/GID values that
are usually used by daemons (above 100) and because the user entry gets
removed after the session closes any leftover files (eg. in /tmp) would
just confuse the admi
This is an annoying bug. To me it seems that after right-clicking the
popup context menu doesn't unregister itself, instead it just hides but
stays at that position.
I am having around 20 open tabs and I can *always reproduce* this bug and even
control what it "randomly" opens!!! I was testing al
Public bug reported:
Binary package hint: eagle
I installed on Ubuntu 9.04 (Jaunty) that uses Gnome 2.26.1 the packages
eagle (5.4.0-4ubuntu1) and eagle-data from Karmic. Most of the program
works, but it seems that there is a missing installation dependency,
because every time I click on an opti
Packages eagle (4.16r2-4ubuntu2) and corresponding eagle-data open the
file selection dialogs without any problems.
Even recompiling the eagle (5.4.0-4ubuntu1) from the sources (deb-src)
did not solve the problem.
--
Segmentation fault on file dialog in 5.4.0-4ubuntu1 on Jaunty
https://bugs.laun
Well, I see two better options than physically doing something to the
speakers:
1. Use another display/login manager. There are plenty of other ones out
there, gdm is just happens to be the default for Gnome... Actually
that's exactly what GNU/Linux is all about - choice - because no one
forces yo
** Attachment added: "My dual-screen Display settings."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873796/+attachment/5357132/+files/TwoScreenDisplaySettings.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
I am using the pre-release Ubuntu 20.04 (updated on 2020-04-20) with
Gnome and XWayland. I have a dual-screen setup with an additional
monitor above the main one. The exactly same setup used to work on
Ubuntu 19.10.
When the top monitor is connected, the results of the "Show
** Attachment added: "Screenshot with two screens where the "Show
applications"/"Search" menu does not work."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873796/+attachment/5357131/+files/TwoScreensProblem.png
--
You received this bug notification because you are a member of
17 matches
Mail list logo
