[Bug 71425] Edgy Live CD installer forces minimum host name length of 3 characters
Public bug reported: Hi, During an attempt to install Edgy via the Live CD, I found that I was not able to assign a 2-character host name to the machine; the installer enforced a minimum length of 3 characters. As far as I am aware, this minimum length is not enforced elsewhere (specifically the Alternate installer and the GNOME Networking Administration applet). To me it doesn't make sense to do this anyway because I have happily used a 2-character host name on this machine for years. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Edgy Live CD installer forces minimum host name length of 3 characters https://launchpad.net/bugs/71425 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71615] Keyboard applet's Layout window does not display layouts
Public bug reported: Hello, If I open the Keyboard applet (gnome-keyboard-properties) from the System > Preferences menu, move to the Layouts tab and click 'Add...' I arrive at the 'Choose a Layout' box. Within this box a graphic of the selected layout should be shown. This no longer seems to be the case, with left-over screen artifacts appearing instead. Screen shots are available at this Ubuntu Forums thread: http://ubuntuforums.org/showthread.php?p=1748738 and I will post one of the screen shots here when I determine how this is done. I am running Ubuntu Edgy Desktop with GNOME v2.16.1, built on 02/10/06. Please let me know if I can provide any further useful information and thanks for your attention. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- Keyboard applet's Layout window does not display layouts https://launchpad.net/bugs/71615 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71615] Re: Keyboard applet's Layout window does not display layouts
Attached is a picture of the 'Choose a Layout' applet as it appears on my system. ** Attachment added: "A screen shot of the 'Choose a Layout' window displaying button artifacts where a graphic of the currently selected layout should appear. This picture was taken after the window was enlarged in both directions." http://librarian.launchpad.net/5062169/Screenshot-Choose%20a%20Layout-2.png -- Keyboard applet's Layout window does not display layouts https://launchpad.net/bugs/71615 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71615] Re: Keyboard applet's Layout window does not display layouts
I wonder if bug #46343 is somehow related to this? It seems to discuss similar issues with xkeyboard-config. -- Keyboard applet's Layout window does not display layouts https://launchpad.net/bugs/71615 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71619] Locked session becomes temporarily visible during user switch
Public bug reported: Binary package hint: gnome-screensaver Hello, If I select System > Quit > Switch User, my session locks and I am presented with the login screen. When I select Quit from the login screen, my monitor briefly goes black, my desktop is fully redrawn (this takes one full second on my PC) and then my screen saver is displayed. This behaviour can also be exhibited by locking the session, switching to another TTY (regardless of its content) and then switching back. As my session is locked, I would expect my desktop not to be displayed under any circumstance besides correct entry of my password. I have marked this as a security vulnerability since a user's desktop may be displaying sensitive information at the time that it is locked, and it is possible to glance at that information without unlocking the desktop. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: Unconfirmed ** Visibility changed to: Public -- Locked session becomes temporarily visible during user switch https://launchpad.net/bugs/71619 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71620] System > Quit does not respond to assigned keyboard shortcut/hotkey
Public bug reported: Hello, I attempt to attach the Ctrl+Alt+Delete keyboard shortcut to the 'Log Out' window by opening the Keyboard Shortcuts applet and assigning Delete to the 'Log out' entry. I then close the Keyboard Shortcuts window to ensure that this new hot key is activated (although this should not be necessary). If I then press Ctrl+Alt+Delete (ensuring that I use the left Alt key), no Log Out window appears. I tried assigning Shift+4 to this action with no success. I can replicate this behaviour on two different machines. If I minimise all windows, select an icon on the desktop and then press the designated hot key, the selected icon flashes; this suggests that at least something is happening. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- System > Quit does not respond to assigned keyboard shortcut/hotkey https://launchpad.net/bugs/71620 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446534] [NEW] aptdaemon kills all my processes 10 minutes after starting an upgrade
Public bug reported: Binary package hint: aptdaemon $ lsb_release -rd Description:Ubuntu karmic (development branch) Release:9.10 $ apt-cache policy aptdaemon aptdaemon: Installiert: 0.10+bzr258-0ubuntu1 Kandidat: 0.10+bzr258-0ubuntu1 Versions-Tabelle: *** 0.10+bzr258-0ubuntu1 0 500 http://de.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status I started the upgrade process through update-manager. When the upgrade takes longer than 10 minutes, aptdaemon kills all processes of the current user exactly 10 minutes after the upgrade was started. Furthermore I found the following messages in /var/log/syslog: Oct 8 18:45:56 r00t-desktop AptDaemon.Worker: CRITICAL: Killing child since timeout of 600 s Oct 8 18:45:56 r00t-desktop modem-manager: Caught signal 15, shutting down... Oct 8 18:45:56 r00t-desktop avahi-daemon[968]: Disconnected from D-Bus, exiting. Oct 8 18:45:56 r00t-desktop avahi-daemon[968]: Got SIGQUIT, quitting. Oct 8 18:45:56 r00t-desktop avahi-daemon[968]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.10.226. Oct 8 18:45:56 r00t-desktop NetworkManager: disconnected by the system bus. Oct 8 18:45:56 r00t-desktop console-kit-daemon[1086]: WARNING: no sender#012 Oct 8 18:45:56 r00t-desktop NetworkManager: no sender Oct 8 18:45:56 r00t-desktop init: Disconnected from system bus Oct 8 18:45:56 r00t-desktop init: dbus main process ended, respawning Oct 8 18:45:56 r00t-desktop init: avahi-daemon main process (968) terminated with status 255 Oct 8 18:45:56 r00t-desktop init: avahi-daemon main process ended, respawning Oct 8 18:45:56 r00t-desktop init: network-manager main process (1236) terminated with status 1 Oct 8 18:45:58 r00t-desktop dbus-daemon: Reloaded configuration Oct 8 18:46:01 r00t-desktop gdm-simple-slave[23101]: WARNING: Unable to load file '/etc/gdm/custom.conf': No such file or directory Oct 8 18:46:01 r00t-desktop acpid: client 1337[108:115] has disconnected Oct 8 18:46:01 r00t-desktop acpid: client 1299[0:0] has disconnected Oct 8 18:46:01 r00t-desktop acpid: client connected from 23102[0:0] Oct 8 18:46:01 r00t-desktop bonobo-activation-server (r00t-23123): could not associate with desktop session: Failed to connect to socket /tmp/dbus-CDDVovhxzn: Connection refused [...] /var/log/apt/term.log says: Log started: 2009-10-08 18:35:55 [...] (Lese Datenbank ... 226965 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereiten zum Ersetzen von linux-image-2.6.31-12-generic 2.6.31-12.40 (durch .../linux-image-2.6.31-12-generic_2.6.31-12.41_amd64.deb) ... Done. Entpacke Ersatz für linux-image-2.6.31-12-generic ... Running postrm hook script /usr/sbin/update-grub. [...] Richte mesa-utils ein (7.6.0-1ubuntu1) ... Verarbeite Trigger für libc-bin ... ldconfig deferred processing now taking place Log ended: 2009-10-08 18:46:23 Now some guesses: I think that the bug must be in the class DaemonInstallProgress in progress.py and that child_pid has to be set correctly since it is only initialised with 0. Furthermore last_activity should be updated properly as it is only updated on start, when start_time is also updated. ProblemType: Bug Architecture: amd64 Date: Thu Oct 8 19:33:31 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: aptdaemon 0.10+bzr258-0ubuntu1 PackageArchitecture: all ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: aptdaemon Uname: Linux 2.6.31-12-generic x86_64 XsessionErrors: (gnome-settings-daemon:2593): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2593): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:2678): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:2743): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed ** Affects: aptdaemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- aptdaemon kills all my processes 10 minutes after starting an upgrade https://bugs.launchpad.net/bugs/446534 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446534] Re: aptdaemon kills all my processes 10 minutes after starting an upgrade
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33314606/Dependencies.txt -- aptdaemon kills all my processes 10 minutes after starting an upgrade https://bugs.launchpad.net/bugs/446534 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446534] Re: aptdaemon kills all my processes 10 minutes after starting an upgrade
Problem also applies to 0.10+bzr259-0ubuntu1 $ apt-cache policy aptdaemon aptdaemon: Installiert: 0.10+bzr259-0ubuntu1 Kandidat: 0.10+bzr259-0ubuntu1 Versions-Tabelle: *** 0.10+bzr259-0ubuntu1 0 500 http://de.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status -- aptdaemon kills all my processes 10 minutes after starting an upgrade https://bugs.launchpad.net/bugs/446534 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355232] Re: acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
+1 from me too I have a AMD Phenom II Black Edition and want to optimize my system through custom Cool'n'Quiet. I undervolt my processor on lower power states and overclock a little bit with default voltage on highest power state. This allows me to lower power consumption in idle and also get higher performance if I need it. -- acpi-cpufreq/powernow-k8 should not be built-in into the kernel image https://bugs.launchpad.net/bugs/355232 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447853] Re: screen stays in a stale state between usplash and xsplash
The same also appears on my system. I think the broken blue line should be text. e.g. If booting is interrupted because of a filesystem error the blue lines stay there, no X gets started and if I press ENTER I get an additional dotted green line going over the screen some pixel below the blue broken line. With further ENTERs the green line partly changes the colour to blue. If I boot without the kernel parameter splash I can see the emergency shell (as expected on a filesystem error). -- screen stays in a stale state between usplash and xsplash https://bugs.launchpad.net/bugs/447853 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447853] Re: screen stays in a stale state between usplash and xsplash
Usplash 0.5.44 solves the problem on my system. Instead of the lines my system now displays a clean black screen between usplash and xsplash. I rechecked this by installing the older versions 0.5.42 and 0.5.43. As expected by me the lines show up again with these versions. After installing 0.5.44 again also the lines disappeared again. Although I must note that on filesystem errors the black screen stays black until I press a key, then the emergency shell is displayed correctly. Moreover I want to note that on usplash start something similar happens. On the black screen just while usplash is starting, I can see some broken green lines for some milliseconds. After that the usplash theme (ubuntu logo) is displayed correctly. But as these lines only appear for some milliseconds they aren't really annoying. -- screen stays in a stale state between usplash and xsplash https://bugs.launchpad.net/bugs/447853 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
