[Bug 89923] Re: [apport] mono crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6634492/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6634493/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/6634494/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6634495/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6634496/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6634497/Registers.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6634498/ThreadStacktrace.txt -- [apport] mono crashed with SIGSEGV https://launchpad.net/bugs/89923 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 18845] Re: [breezy] network-manager doesn't work with static wired IP
This was closed for Breezy, but I think it resurfaced as bug #5364 and it's still active on Feisty (with a few related issues, too). Shouldn't it be reopened and marked as a duplicate of one of them? -- [breezy] network-manager doesn't work with static wired IP https://launchpad.net/bugs/18845 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 5364] Re: Can't use static ip address with network-manager
I agree with James. Also, if I understand correctly the upstream bug linked at the top, this actually is implemented, but Ubuntu doesn't use it right. So I'd say it's really an Ubuntu bug. -- Can't use static ip address with network-manager https://launchpad.net/bugs/5364 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90409] metacity forgets "(on Hostname)" annotantion on remote apps sometimes
Public bug reported: Binary package hint: metacity Hi! This report is about the latest Metacity on Feisty. Metacity usually tries to add an "(on Hostname)" annotation to applications that run on remote hosts but use the local machine's X server. For instance, I run Amarok on another computer using "ssh -fnX Hostname.local amarok", and the hostname is normally displayed in the window's titlebar. I'm not sure what causes the problem, but often the annotation disappears. In Amarok's case, it always disappears if I reduce it to a Notification Area icon. When I restore the window, it looks just like a local window. When Amarok changes its title (for example, when the track changes) the annotation returns. It doesn't disappear if I minimize it, just if I iconize it. I'm almost sure I've seen this for other applications, too, but this is the one I can consistently reproduce the bug with. ** Affects: metacity (Ubuntu) Importance: Undecided Status: Unconfirmed -- metacity forgets "(on Hostname)" annotantion on remote apps sometimes https://launchpad.net/bugs/90409 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90599] [apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()
Public bug reported: Binary package hint: firefox I wasn't using FF at the moment, it was minimized. I had just did an update (using update manager), and I let the computer unsupervised for a while. When I returned I got the crash report. It's possible the update caused the crash. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Thu Mar 8 10:59:05 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/firefox/firefox-bin Package: firefox 2.0.0.2+1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/lib/firefox/firefox-bin ProcCwd: /home/bogdanb ProcEnviron: LANGUAGE=en_US:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: firefox StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libpthread.so.0 ?? () ?? () ?? () Uname: Linux cimer 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access pulse-rt scanner video ** Affects: firefox (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall() https://launchpad.net/bugs/90599 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90599] Re: [apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6674917/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6674918/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/6674919/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6674920/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6674921/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6674922/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/6674923/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6674924/ThreadStacktrace.txt -- [apport] firefox-bin crashed with SIGSEGV in __kernel_vsyscall() https://launchpad.net/bugs/90599 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127649] Re: [ipw3945] nm-applet doesn't work unless I start dhclient manually
I can confirm that it works correctly now, i.e. NM connects itself to the network after giving it the keyring password. -- [ipw3945] nm-applet doesn't work unless I start dhclient manually https://bugs.launchpad.net/bugs/127649 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90409] Re: metacity forgets "(on Hostname)" annotantion on remote apps sometimes
Yes, it seems to work now correctly. Thanks! -- metacity forgets "(on Hostname)" annotantion on remote apps sometimes https://bugs.launchpad.net/bugs/90409 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121796] Re: multiple non-working "Open With>Gimp" entries
I still have the "not working" issue even after the latest upgrades. (But I also have multiple entries, so that might contribute.) -- multiple non-working "Open With>Gimp" entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132054] can't create new keyring
Public bug reported: Binary package hint: gnome-keyring-manager This is about Ubuntu Gutsy, freshly updated. I can't create any new keyrings (including the default one, if there are none) with the gnome keyring manager. When I try to create a new keyring (menu Keyring>New Keyring) the new name is added to the keyrings list, but it's not accessible. I get a "Gnome-Keyring-Manager-WARNING **: Failed to get keyring info." error in the console. I've snooped around through the sources a bit, and as far as I can tell: (1) create_keyring_callback in gnome-keyring-manager-keyring-manager.c receives a (correct) GnomeKeyringResult of GNOME_KEYRING_RESULT_OK, which should indicate that adding the keyring was successful, but then (2) it runs gkm_keyring_manager_update_keyring_info on the new keyring, which (3) runs gnome_keyring_get_info on it, and (4) update_keyring_info_worker_callback receives a GNOME_KEYRING_RESULT_NO_SUCH_KEYRING status. Which doesn't seem right to me. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-keyring-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132054] Re: can't create new keyring
I added gnome-keyring to the "affects" list, as it seems there's the problem. -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133139] update-manager bug when loading Changes is slow
Public bug reported: Binary package hint: update-manager Hello. This is about the latest (and older) update-manager on Gutsy. I have the update-manager window opened with the "Changes" tab selected and expanded, so it shows the changes for every package to be updated. Imagine there are three packages in the updates list, A, B and C. If A is selected, its changes are displayed correctly below it. If I press down arrow on the keyboard, the B package is selected, its changes should be looked-up and displayed. The same for C. This works OK normally, but: (We're back with A selected.) I click down, B gets selected. The Changes tab briefly displays "Downloading the list of changes" or something similar. This is the trick: If I press down again _before_ the changes for B are displayed (this happens often for me, but it might depend on your connection), then the bug happens. Usually the changes for C are displayed (not sure why it's quicker than B), then I get a warning in the console, then the changes for B are displayed, although C is still selected. I can get the changes for C by going back to B and then returning to C. Here's an example for this happening three times in a row: /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875ece0' has no handler with id `362' button.disconnect(id); /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875ece0' has no handler with id `367' button.disconnect(id); /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875eb70' has no handler with id `377' button.disconnect(id); I suppose a callback waiting for the download of the changes forgets to check if it should still display them. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager bug when loading Changes is slow https://bugs.launchpad.net/bugs/133139 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58386] Re: ACPI: Looking for DSDT ... not found! (message during boot)
Re-opening (I think). Even if this is not a real "error" (ie, if not having a DSDT is a normal situation), this is still a user-interface bug: it should not be reported as a boot-time error. The message should be changed to something more descriptive, like "file /DSDT.aml not found, using defaults" or whatever is appropriate. I couldn't find any recent docs on this, what is it supposed to do, anyway? I'm always having issues with ACPI and I'm always on the look for hacks. Is there anything I can do (ie, compile a file) and perhaps include it in a package to help support my laptop type better (Dell Latitude D620). I'm attaching 2.6.22 too, as I still get this message on Gutsy with the newest kernel. ** Also affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-source-2.6.15 (Ubuntu) Status: Invalid => New -- ACPI: Looking for DSDT ... not found! (message during boot) https://bugs.launchpad.net/bugs/58386 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133146] ACPI Warning: Incorrect checksum in table
Public bug reported: Binary package hint: linux-image-2.6.22-9-generic During boot I get the following warning: [0.684000] ACPI: EC: Look up EC in DSDT [0.696000] ACPI Warning (tbutils-0158): Incorrect checksum in table [TCPA] - 00, should be 9A [20070126] [0.696000] ACPI: SSDT 3F681A10, 0043 (r1 LMPWR DELLLOM 1001 INTL 20050624) [0.696000] ACPI: Interpreter enabled [0.696000] ACPI: (supports S0 S3 S4 S5) [0.696000] ACPI: Using IOAPIC for interrupt routing [0.736000] ACPI: PCI Root Bridge [PCI0] (:00) (The second line has the warning, I included the rest for context.) Even if it's not indicative of a problem (though I always have issues with ACPI), I'd like to find the cause and perhaps a fix. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- ACPI Warning: Incorrect checksum in table https://bugs.launchpad.net/bugs/133146 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133150] ubuntu-desktop depends on serpentine
Public bug reported: Binary package hint: ubuntu-desktop In Gutsy, ubuntu-desktop (up-to-date) depends on serpentine. This is not a _necessary_ package---some desktop users might not even have a CD writer. It should be a recommends rather than depends. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- ubuntu-desktop depends on serpentine https://bugs.launchpad.net/bugs/133150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133150] Re: ubuntu-desktop depends on serpentine
*** This bug is a duplicate of bug 122039 *** https://bugs.launchpad.net/bugs/122039 The same is true for cd-paranoia, dvd+rw-tools, nautilus-cd-burner, wodim --- someone without a CD drive can be desktop user. Other unnecessary packages (should be recommends): fortune-mod, gnome- pilot-conduits (I don't have a PDA), and almost all printer-related packages (foomatic-*, pnm2ppa, cupsys-*) which are not critical for users without a printer. -- ubuntu-desktop depends on serpentine https://bugs.launchpad.net/bugs/133150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122039] Re: [Gutsy] unnecessary packages in ubuntu-desktop dependencies?
Other items for the list: cd-paranoia, dvd+rw-tools, nautilus-cd-burner, wodim --- someone without a CD drive can be desktop user. fortune-mod --- not really critical gnome-pilot-conduits --- I don't have a PDA almost all printer-related packages (foomatic-*, pnm2ppa, cupsys-*) which are not critical for users without a printer. -- [Gutsy] unnecessary packages in ubuntu-desktop dependencies? https://bugs.launchpad.net/bugs/122039 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133150] Re: ubuntu-desktop depends on serpentine
*** This bug is a duplicate of bug 122039 *** https://bugs.launchpad.net/bugs/122039 Thanks, I moved the list of packages there. -- ubuntu-desktop depends on serpentine https://bugs.launchpad.net/bugs/133150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79633] Re: Network-config doesn't start the network
Hi, thanks for reminding me of this. It's working now, you can close this safely. -- Network-config doesn't start the network https://bugs.launchpad.net/bugs/79633 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133167] Re: Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Forgot to mention: this is on an up-to-date Gutsy, running on a Dell Latitude D620 with ipw3945 wireless. The network works. -- Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported https://bugs.launchpad.net/bugs/133167 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133167] Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Public bug reported: Binary package hint: network-manager I see I keep getting this error in /var/log/daemon.log: Aug 17 18:10:33 cimer NetworkManager: Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported And I get _lots_ of it. I haven't been toying with the killswitch at the time (it doesn't work most of the time). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported https://bugs.launchpad.net/bugs/133167 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71510] Re: Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after 500ms
I can see this in up-to-date Gutsy every time I shut down. Strangely I can't find anything in the logs about it, with just one exception a few days ago: $ grep "Error sending" /var/log/* kern.log:Aug 12 14:35:32 cimer kernel: [75812.852000] ipw3945: Error sending LEDS_CMD: time out after 500ms. It seems similar, though it gives a name to the command. -- Error on shutdown --> ipw 3945: error sending cmd #07 to daemon: timeout after 500ms https://bugs.launchpad.net/bugs/71510 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98955] Re: logd not running
So right now there is zero possibility to find out what happened during boot? I see messages spewing all over the console, some of them errors (that I'm trying to work out), how can I get to them? -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94120] Re: bootlogd configuration files are misleading
Someone might want to apply this patch to the /etc/init.d/bootlogd file. As the old one, it checks if the daemon exists. However, if it doesn't, it warns the user (the old one failed silently) and points them to this bug report, which is informative enough. There's also a 2 sec delay there (it only occurs in the error situation) to let the user at least notice the message. (Due to these bugs, the logs are not available...) ** Attachment added: "Warns the user if the daemon doesn't exist" http://launchpadlibrarian.net/8881730/bootlogd.diff -- bootlogd configuration files are misleading https://bugs.launchpad.net/bugs/94120 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133183] segmentation fault during boot---udev to blame?
Public bug reported:
Binary package hint: udev
Hello! Not sure what to do with this. I'm running Gutsy on an intel
laptop.
I've noticed that during boot there are several "Segmentation fault"
messages appearing after the "running init-bottom" message. I think one
of the local-* scripts appears between the first and the second faults.
I've checked and I have only one init-bottom script, /usr/share
/initramfs-tools/scripts/init-bottom/udev. (There's nothing in /etc
/initramfs-tools/scripts/init-bottom.)
I've added echos before every line, and apparently the first segfault
appears on the line "mount -n -o bind ${rootmnt}/dev /dev/.static/dev".
(The echo before that line is displayed, then the segfault, then nothing
else from that file.)
Since apparently no kind of boot logging works, I'm not sure how to
investigate this further. I don't see anything not working though.
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
segmentation fault during boot---udev to blame?
https://bugs.launchpad.net/bugs/133183
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133206] Re: 915resolution spams the console at startup
The attached file is my replacement for /etc/init.d/915resolution It should do everything the current version does, but (1) it dumps any output of its binary in /var/log/915resolution and (2) it uses the init- functions to display messages, including success status, failures and warnings. The current file should be replaced by this version (after some review, I could only check on my system). ** Attachment added: "Replacement for /etc/init.d/915resolution" http://launchpadlibrarian.net/8882296/915resolution -- 915resolution spams the console at startup https://bugs.launchpad.net/bugs/133206 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133206] 915resolution spams the console at startup
Public bug reported: Binary package hint: 915resolution On Gutsy (and probably everything else) the startup script of 915resolution doesn't use the /lib/lsb/init-functions for display. It uses "echo"s and it also allows its binary to spew stuff in the console. At least on my system the result is about two screens of misaligned messages during the boot process. ** Affects: 915resolution (Ubuntu) Importance: Undecided Status: New -- 915resolution spams the console at startup https://bugs.launchpad.net/bugs/133206 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137247] libpam-keyring broken on autologins
Public bug reported: Binary package hint: libpam-keyring This is on up-to-date Gutsy: libpam-keyring doesn't work correctly when set-up together with gdm's autologin feature. As expected, GDM logins automatically the correct user. However libpam- keyring fails to retrieve the user's password (probably because it wasn't entered) and instead displays a dialog box asking for it, which defeats the purpose of the plugin. Instead, if the password isn't available it should just do nothing (perhaps log a message somewhere) and allow the normal keyring unlocking to work (eg, let Network Manager ask for the password when it needs it). Also, the dialog where libpam-keyring asks for the password does NOT mask the entered password (eg, with asterisks), making it visible on the screen. That's why I'm marking this as a (minor) security vulnerability. It's likely that libpam cannot actually retrieve the password on autologins (I assume GDM just "su -"s into the username, so it doesn't actually know the password), in which case this should be attached as a "wishlist" bug for GDM or gnome-keyring. For instance, gnome-keyring might allow itself to be unlocked by the "root" user as an optional, lower-security feature. Here's my config: $ cat /etc/pam.d/gdm-autologin #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequiredpam_env.so readenv=1 envfile=/etc/default/locale authrequiredpam_permit.so authoptionalpam_keyring.so try_first_pass @include common-account session requiredpam_limits.so session optionalpam_keyring.so @include common-session @include common-password ** Affects: pam-keyring (Ubuntu) Importance: Undecided Status: New ** Visibility changed to: Public ** Description changed: Binary package hint: libpam-keyring This is on up-to-date Gutsy: libpam-keyring doesn't work correctly when set-up together with gdm's autologin feature. As expected, GDM logins automatically the correct user. However libpam- keyring fails to retrieve the user's password (probably because it wasn't entered) and instead displays a dialog box asking for it, which defeats the purpose of the plugin. Instead, if the password isn't available it should just do nothing (perhaps log a message somewhere) and allow the normal keyring unlocking to work (eg, let Network Manager ask for the password when it needs it). Also, the dialog where libpam-keyring asks for the password does NOT mask the entered password (eg, with asterisks), making it visible on the screen. That's why I'm marking this as a (minor) security vulnerability. It's likely that libpam cannot actually retrieve the password on autologins (I assume GDM just "su -"s into the username, so it doesn't actually know the password), in which case this should be attached as a "wishlist" bug for GDM or gnome-keyring. For instance, gnome-keyring - might allow itself to be unlocked by the "root" user as an optional - feature. + might allow itself to be unlocked by the "root" user as an optional, + lower-security feature. Here's my config: $ cat /etc/pam.d/gdm-autologin #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequiredpam_env.so readenv=1 envfile=/etc/default/locale authrequiredpam_permit.so authoptionalpam_keyring.so try_first_pass @include common-account session requiredpam_limits.so session optionalpam_keyring.so @include common-session @include common-password -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137254] No boot-time logs exists at this time in Gutsy
Public bug reported: Binary package hint: ubuntu-minimal In the current build of Gutsy, there is no kind of boot log, ie a log of all the messages shown during boot. There are a couple of bugs in the (two, I think) packages that provide boot-log functionality that I'd like to link here (either would fix this) but I can't find right now. I hope someone in triage can help. However, this is a bug in the entire distribution, not a duplicate of those, because they are sufficient but not necessary; this one can be fixed by another temporary solution, for instance. I think even a makeshift solution would do for now, even if it's mildly inconvenient or buggy. A boot-time parameter could enable/disable it. I hesitate to mark this as a security vulnerability. It's not really a vulnerability in a package, but it's a (lacking) vital security tool: without a boot log it's very hard to notice error messages (and thus potential security issues) during the boot time. It's also pretty hard to debug any start-up issues---if any of the developers can help with a note of how they manage to find out what's wrong with, eg, initrd scrips, please leave a note here. I attached this to ubuntu-minimal, as I think this functionality is critical to a running system, but feel free to move it somewhere more appropriate. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- No boot-time logs exists at this time in Gutsy https://bugs.launchpad.net/bugs/137254 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137247] Re: libpam-keyring broken on autologins
** Description changed: Binary package hint: libpam-keyring This is on up-to-date Gutsy: libpam-keyring doesn't work correctly when set-up together with gdm's autologin feature. As expected, GDM logins automatically the correct user. However libpam- keyring fails to retrieve the user's password (probably because it wasn't entered) and instead displays a dialog box asking for it, which defeats the purpose of the plugin. Instead, if the password isn't available it should just do nothing (perhaps log a message somewhere) and allow the normal keyring unlocking to work (eg, let Network Manager - ask for the password when it needs it). + ask for the password when it needs it). This locks the loading process, + which is very annoying. Also, the dialog where libpam-keyring asks for the password does NOT mask the entered password (eg, with asterisks), making it visible on the screen. That's why I'm marking this as a (minor) security vulnerability. + + Note: of course this can be worked-around by simply disabling the plugin + in /etc/pam.d/gdm-autologin (and it doesn't put itself there), but it's + still buggy behavior. It's likely that libpam cannot actually retrieve the password on autologins (I assume GDM just "su -"s into the username, so it doesn't actually know the password), in which case this should be attached as a "wishlist" bug for GDM or gnome-keyring. For instance, gnome-keyring might allow itself to be unlocked by the "root" user as an optional, lower-security feature. Here's my config: $ cat /etc/pam.d/gdm-autologin #%PAM-1.0 authrequisite pam_nologin.so authrequiredpam_env.so readenv=1 authrequiredpam_env.so readenv=1 envfile=/etc/default/locale authrequiredpam_permit.so authoptionalpam_keyring.so try_first_pass @include common-account session requiredpam_limits.so session optionalpam_keyring.so @include common-session @include common-password -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137254] Re: No boot-time logs exists at this time in Gutsy
One of the bugs I mentioned above is https://bugs.launchpad.net/upstart/+bug/98955 There's also a question on this subject: https://answers.launchpad.net/ubuntu/+question/11985 -- No boot-time logs exists at this time in Gutsy https://bugs.launchpad.net/bugs/137254 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137510] better console setup
Public bug reported: Binary package hint: console-tools Hello! I'm using Ubuntu Gutsy, and for some times I've been hacking around parts of the boot process, and in particular the set-up of the text console. There are a few improvements I've been able to make, and some of them I think should be included as default in the Ubuntu packages. I'd like however the input of others familiar with the packages (console-tools and console-setup) about the changes, and for committing the patches. So here are a few ideas: (1) redundancy setting console font: as far as I can tell, the /etc/init.d/console-setup is setting up the console font quite late in the boot process. However, /usr/share/initramfs-tools/scripts/init- top/console_setup does (or can do) the same thing much earlier. I think only the later part should be used, since it provides the "good" font longer during the boot process. (It would be great if it were possible to setup the font before the kernel prints anything, but that seems difficult.) (2) redundancy setting keyboard layout: as far as I can tell, at least three of the scripts in /etc/init.d handle the keyboard layout. Ideally this should be set-up only once, very early in the boot process (ideally starting with grub, but init-top is OK too). I administrate my own system, and I'm used with dvorak; it's very annoying when something breaks and I have to use the layout on the keyboard, which isn't even normal qwerty since this is a French laptop. (This is an issue for anyone using a non-standard keyboard, like the localized variants, not only for dvorak.) (3) a better default font: I'm using the Uni3 console fonts because they enable lots of diacritics. (I also happen to think it looks nicer.) I know many people don't usually need diacritics (ie, English natives), but with Unicode being almost everywhere these days, it's not uncommon to encounter filenames with such characters, even if one doesn't use them all the time. (Ubuntu does use UTF8 as the default encoding after all, right?) Localized versions would certainly benefit from having a Unicode console font enabled by default. AFAIK, no-one would be hurt by defaulting to the Uni3 fonts, and people who need more (for Arabic or whatever isn't supported by Uni3) can just set-up their systems as before. (4) a better default layout: related to the previous item, since Unicode is more common I've often felt the need to generate accented characters. I'm not talking only about my native-language files; sometimes I've had to transfer, eg, music files through a ssh connection, and this always leads to issues with songs from international artists. Even though it won't cover everything (like Japanese), we could set-up by default the internationalized version of the US keyboard; it uses AltGr to generate some dead-keys; this doesn't annoy anyone who doesn't use them (altgr+tilde,a is not a common key combination), and it would help a lot some users. I think the console-setup package is intended to use the same keymaps with X. It might be worthwhile to get rid of the other kind(s) in the default install, to minimize redundancy. I'd like to also add the possibility to modify or create custom layouts, at least by providing a nice man page explaining how things work. ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Affects: console-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu) Importance: Undecided Status: New -- better console setup https://bugs.launchpad.net/bugs/137510 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137514] sshfs locks up randomly
Public bug reported: Binary package hint: sshfs Hello! I'm running Gutsy on a laptop, and I use sshfs to mount directories from various computers around the house. (AFAIK, it's the "safest" solution, but I'm open to suggestions.) It usually runs pretty well, although a bit slow (though I think it's because of the wireless more than the overhead). However, it randomly locks up. This means that any application that tries to access a mount point (say, nautilus or ls) just freezes. I can start a terminal and kill the sshfs process, unmount the "share", and the applications (usually) come back. Either that or I kill them and restart them from the terminal. I can remount immediately, and it works for a while until it happens again. I can't see any constant pattern with the freezes. I seems to happen more often when there's a big load on the share (eg, copy files and play media at the same time), but not always. Sometimes it seems to happen repeatedly when I try to access a certain directory on a share, but after a while it works. It doesn't seem to be linked to a certain application, either. Sometimes it happens a dozen times a day, sometimes I go for days without encountering this. I've checked for anything that seemed obvious: the network isn't to blame (everything else keeps working), it happens both on wireless and Ethernet, and I'm connecting to a Linux (Ubuntu Feisty) and a MacOS X machine and it happens the same way. I don't know what to search for next. ** Affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: sshfs Hello! I'm running Gutsy on a laptop, and I use sshfs to mount directories from various computers around the house. (AFAIK, it's the "safest" solution, but I'm open to suggestions.) It usually runs pretty well, although a bit slow (though I think it's because of the wireless more than the overhead). However, it randomly locks up. This means that any application that tries to access a mount point (say, nautilus or ls) just freezes. I can start a terminal and kill the sshfs process, unmount the "share", and the applications (usually) come back. Either that or I kill them and restart them from the terminal. I can remount immediately, and it works for a while until it happens again. I can't see any constant pattern with the freezes. I seems to happen more often when there's a big load on the share (eg, copy files and play media at the same time), but not always. Sometimes it seems to happen repeatedly when I try to access a certain directory on a share, but after a while it works. It doesn't seem to be linked to a certain - application, either. + application, either. Sometimes it happens a dozen times a day, sometimes + I go for days without encountering this. I've checked for anything that seemed obvious: the network isn't to blame (everything else keeps working), it happens both on wireless and Ethernet, and I'm connecting to a Linux (Ubuntu Feisty) and a MacOS X machine and it happens the same way. I don't know what to search for next. -- sshfs locks up randomly https://bugs.launchpad.net/bugs/137514 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137519] sshfs: please update to latest version (1.6 -> 1.8)
Public bug reported: Binary package hint: sshfs The SSHFS in the Gutsy repositories is currently version 1.6-1. In the Sourceforge repositories it already reached 1.8: http://sourceforge.net/project/showfiles.php?group_id=121684&package_id=140425 ** Affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: New -- sshfs: please update to latest version (1.6 -> 1.8) https://bugs.launchpad.net/bugs/137519 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 137247] Re: libpam-keyring broken on autologins
I am using libpam-keyring, not pam-keyring. I'll try to get a screenshot today. $ aptitude show ~npam-key Package: libpam-keyring New: yes State: installed Automatically installed: yes Version: 0.0.8-6 Priority: optional Section: universe/admin Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]> Uncompressed Size: 127k Depends: libc6 (>= 2.5-0ubuntu1), libglib2.0-0 (>= 2.12.9), libgnome-keyring0 (>= 0.8), libpam0g (>= 0.76) Recommends: gnome-session (>= 2.10) Description: PAM module that unlock gnome keyring This PAM module unlock your gnome keyring at login time. Useful when using network-manager or other tools that requires access to gnome keyring just after login. Homepage: http://www.hekanetworks.com/pam_keyring/ -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132054] Re: can't create new keyring
Yes, it seems to be working now. Thanks! ** Changed in: gnome-keyring (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-keyring-manager (Ubuntu) Status: New => Fix Released -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 118862] Re: update-manager -c -d DOESN'T work for going to Gutsy
Same here, with a "normal" Feisty (without xubuntu or kubuntu). -- update-manager -c -d DOESN'T work for going to Gutsy https://bugs.launchpad.net/bugs/118862 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 118862] Re: update-manager -c -d DOESN'T work for going to Gutsy
As the second error suggests, file "/usr/lib/python2.5/site- packages/UpdateManager/DistUpgradeFetcher.py" doesn't import the "os" object/package/whatever it's called. (Sorry, I only learned python by ear...) I added "import os" at the top of that file and the update started. (I still got the dbus problem, so I also added "import dbus" at the same file. Now I don't get either error.) I'm trying to do the update now and hoping this will work... -- update-manager -c -d DOESN'T work for going to Gutsy https://bugs.launchpad.net/bugs/118862 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119135] wrong "e; entity
Public bug reported: Binary package hint: gdm File /usr/share/gnome/help/gdm/es/gdm.xml contains a wrong ""e;" entity instead of the correct """ one. I noticed this during the update from Feisty to Gutsy. ** Affects: gdm (Ubuntu) Importance: Undecided Status: Unconfirmed -- wrong "e; entity https://bugs.launchpad.net/bugs/119135 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119137] memory warning in mono update
Public bug reported: Binary package hint: mono I have noticed some warnings during the update from Feisty to Gutsy. I've only managed to copy the snippet below (it happened at least once before). If there's a log you need just tell me where to get it from. ***MEMORY-WARNING***: /usr/share/mono/MonoGetAssemblyName.exe[16892]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... ***MEMORY-WARNING***: /usr/lib/mono/1.0/gacutil.exe[16896]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... * Installing 1 assembly from libndesk-dbus1.0-cil into Mono ***MEMORY-WARNING***: /usr/share/mono/MonoGetAssemblyName.exe[16906]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... ***MEMORY-WARNING***: /usr/lib/mono/1.0/gacutil.exe[16910]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono ***MEMORY-WARNING***: /usr/share/mono/MonoGetAssemblyName.exe[16920]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... ***MEMORY-WARNING***: /usr/lib/mono/1.0/gacutil.exe[16924]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... Setting up mono-runtime (1.2.4-3ubuntu1) ... Setting up libexif12 (0.6.15-1) ... Setting up libmono-system1.0-cil (1.2.4-3ubuntu1) ... Setting up libglib2.0-cil (2.10.0-2) ... Setting up libmono-cairo1.0-cil (1.2.4-3ubuntu1) ... Setting up libgtk2.0-cil (2.10.0-2) ... Setting up libglade2.0-cil (2.10.0-2) ... Setting up libgnomeprint2.2-data (2.18.0-2) ... Setting up libgnomeprint2.2-0 (2.18.0-2) ... Setting up libgnomeprintui2.2-common (2.18.0-2) ... Setting up libgnomeprintui2.2-0 (2.18.0-2) ... Setting up libart2.0-cil (2.16.0-6) ... Setting up librsvg2.0-cil (2.16.0-6) ... Setting up cli-common (0.4.8) ... Setting up libgmime-2.0-2 (2.2.8-1ubuntu1) ... Setting up libgmime2.2-cil (2.2.8-1ubuntu1) ... * Installing 1 assembly from libgmime2.2-cil into Mono ***MEMORY-WARNING***: /usr/share/mono/MonoGetAssemblyName.exe[16944]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... ***MEMORY-WARNING***: /usr/lib/mono/1.0/gacutil.exe[16948]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... Setting up binfmt-support (1.2.10) ... * Enabling additional executable binary formats binfmt-support [ OK ] Setting up binutils-static (2.17.20070426cvs-7ubuntu2) ... Setting up python-bittorrent (3.4.2-11ubuntu1) ... ** Affects: mono (Ubuntu) Importance: Undecided Status: Unconfirmed -- memory warning in mono update https://bugs.launchpad.net/bugs/119137 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 118862] Re: update-manager -c -d DOESN'T work for going to Gutsy
Update: OK, I've run the update. The good news: it worked (but see below). I'm happily running Gutsy right now. The bad news: it didn't work flawlessly. During the update there were several error messages. I did run a (probably unnecessary, perhaps harmful, and certainly lengthy) "dpkg-reconfigure -a -u", and a dist- update, and I had to pick the new kernel manually on boot. (Got me a bit of a scare the first time; I didn't notice the old kernel was running, and it had no network drivers...) The other good news: it will probably work better for others. My system is a bit special: I've updated continuously from Dapper through Gutsy, and I always mess with configs and things, so it's very likely my system was a bit hard to update. -- update-manager -c -d DOESN'T work for going to Gutsy https://bugs.launchpad.net/bugs/118862 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119196] gconftool-2 reports memory corruption
Public bug reported: Binary package hint: gconf2 Hello. I've just updated from Feisty to Gutsy (using the update manager) and during the update I've seen many warnings like the one below. ***MEMORY-WARNING***: gconftool-2[28570]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... I don't know which package exactly contains gconftool, but I suppose the gconf guys would know. I've seen the same error during a dpkg-reconfigure _after_ the update, so it's very likely still a problem in Gutsy. ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- gconftool-2 reports memory corruption https://bugs.launchpad.net/bugs/119196 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119198] non-package menu entry
Public bug reported: Binary package hint: gnome-app-install Hi. Not sure if this is a real bug, maybe just a UI bug. I've just done an update from Feisty to Gutsy, and I noticed these messages during the update: .. Setting up gnome-app-install (0.4.2) ... Caching application data... Got non-package menu entry kiso.desktop Got non-package menu entry xchm.desktop Got non-package menu entry k3dsurf.desktop Got non-package menu entry grdesktop.desktop Got non-package menu entry tsclient.desktop Got non-package menu entry kmyfirewall.desktop Generating mime/codec maps... .. Now, it doesn't say it's an error or not, but it looks weird. If it's not an error, why is it displaying those packages in particular? If it's an error, what does it mean? ** Affects: gnome-app-install (Ubuntu) Importance: Undecided Status: Unconfirmed -- non-package menu entry https://bugs.launchpad.net/bugs/119198 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119318] power manager insists batter is broken
Public bug reported: Hello! I've just updated from Feisty to Gutsy. I'm having a strange issue with the power manager. (I use Gnome for pretty much everything, btw.) Each time I start up the computer, the power manager claims the battery's total capacity is only 33%, which probably means a bad or old battery. I'm almost sure that isn't the case (I have about the same uptime on a battery as when I bought the laptop, AFAIK). After the start-up finishes the power applet correctly shows the battery almost full, though. I've also seen the manager at least once shutting down the computer with quite a lot of battery left (about a third), on a separate occasion. I've read somewhere the power manager switched to a new battery estimator (I can't find where, though); apparently it needs a few battery cycles to "learn" the battery's behavior. If that's true then it's still a bug: I think it should use the old heuristics until it has a reasonably good estimation (ie, it goes through a couple of full charge-discharge cycles with a better than, say, 5% estimate; restarts or time aren't good, as I often keep the computer plugged in for a few days). Otherwise, it can scare people with fake warnings, and can cause loss of work by shutting down with a full battery. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- power manager insists batter is broken https://bugs.launchpad.net/bugs/119318 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119315] udevd hogs the processor and spams /var/log/messages
Public bug reported: Binary package hint: udev Hello! I've updated from Feisty to Gutsy yesterday, and noticed a weird problem: Right after boot, a "udevd" process (there are several in the System Monitor) keeps hogging the processor. (This means 100% pretty much all the time. However this is a dual-core machine, it remains responsive.) I've looked in var/log, and at least "kern.log" and "messages" are spammed by ioctl errors (and I mean tens of megabytes). See below for snippets. If I do a /etc/init.d/udev restart I get an "Loading additional hardware drivers..." and the scripts remains there (I killed it after a minute or so; the errant process kept hogging). However, "udev stop && udev start" worked, ie. it stopped the processor-hog and restarted udev; I still got an "error receiving uevent message: No buffer space available", but I suppose that's something wrong with a script. After restarting udev, it doesn't hog the processor anymore nor does it spam the logs; everything seems to work OK until I reboot, when everything happens the same again. This is an up-to-date Gutsy running on a Latitude D620 laptop (Centrino Duo processor). $ uname -a Linux cimer 2.6.22-6-generic #1 SMP Fri Jun 1 19:24:12 GMT 2007 i686 GNU/Linux This is what /var/log/kern.log lists (megabytes of it): Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer kernel: [ 543.86] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Jun 8 14:19:47 cimer kernel: [ 543.86] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer kernel: [ 543.86] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed Jun 8 14:19:47 cimer kernel: [ 543.86] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer kernel: [ 543.86] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed And this is what /var/log/messages shows: Jun 8 14:19:47 cimer kernel: [ 543.844000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer kernel: [ 543.848000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer last message repeated 6 times Jun 8 14:19:47 cimer kernel: [ 543.852000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer last message repeated 7 times Jun 8 14:19:47 cimer kernel: [ 543.856000] device-mapper: ioctl: error adding target to table Jun 8 14:19:47 cimer last message repeated 8 times ** Affects: udev (Ubuntu) Importance: Undecided Status: Unconfirmed -- udevd hogs the processor and spams /var/log/messages https://bugs.launchpad.net/bugs/119315 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119424] [Gutsy] libflashsupport is not installable
Public bug reported: After updating from Feisty to Gutsy I got only intermittent sound with Flash (ie, only sometimes, not skippy). After a while it simply didn't work at all. I tried reinstalling libflashsupport and I got a "No candidate version found for libflashsupport". ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- [Gutsy] libflashsupport is not installable https://bugs.launchpad.net/bugs/119424 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115616] Re: Device-mapper errors: dm-linear, lookup failed
In case that's not obvious from the above, "aptitude remove evms" gets rid of the problem. I suppose if you don't know what evms is, then you're probably not using it (unless someone else configured your system; you should ask them then). -- Device-mapper errors: dm-linear, lookup failed https://bugs.launchpad.net/bugs/115616 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81876] Re: Dependency on java2-runtime removed
Indeed, it seems to have gone back to the old dependency set. -- Dependency on java2-runtime removed https://bugs.launchpad.net/bugs/81876 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82307] Re: Can't copy VCD ".dat" files from CD to Hard Drive
I have a similar issue on Gutsy, but the errors are a bit different (see below). The disc plays with no glitches in a hardware player, but the .dat files can't be copied. I can't find a cdfs package, only a cdfs-src but that doesn't build (under Gutsy, at least), I think it's made for a different kernel. $ sudo dmesg [68555.788000] end_request: I/O error, dev sr0, sector 5040 [68555.788000] printk: 22 messages suppressed. [68555.788000] Buffer I/O error on device sr0, logical block 1260 [68555.788000] Buffer I/O error on device sr0, logical block 1261 [68555.788000] Buffer I/O error on device sr0, logical block 1262 [68555.788000] Buffer I/O error on device sr0, logical block 1263 [68555.788000] Buffer I/O error on device sr0, logical block 1264 [68555.788000] Buffer I/O error on device sr0, logical block 1265 [68555.788000] Buffer I/O error on device sr0, logical block 1266 [68555.788000] Buffer I/O error on device sr0, logical block 1267 [68556.704000] end_request: I/O error, dev sr0, sector 5040 [68556.704000] Buffer I/O error on device sr0, logical block 1260 [68556.704000] Buffer I/O error on device sr0, logical block 1261 ** Also affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Can't copy VCD ".dat" files from CD to Hard Drive https://bugs.launchpad.net/bugs/82307 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 140643] Re: [evince] cairo context error: NULL pointer
Any idea when it will be accessible here? BTW, not sure if that's related or interesting, but I can't print the document given above. (Evince usually prints PDFs.) -- [evince] cairo context error: NULL pointer https://bugs.launchpad.net/bugs/140643 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12153] Re: Cannot use Windows key in keyboard shortcuts
The funny thing is that using compiz's settings manager (ccsm) this works without any problem. -- Cannot use Windows key in keyboard shortcuts https://bugs.launchpad.net/bugs/12153 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153676] weird behavior with full-screen windows
Public bug reported: Hello! I've just done a fresh install of Ubuntu Gutsy, and I'm currently quite pleased with how Compiz works. (I had Gutsy before (re-installed after some hardware problems), but Compiz didn't work very well, probably because of cruft accumulated through upgrades all the way from Dapper.) Now Compiz works great, and after a bit of configuring I'm actually more pleased with it than I ever was with Metacity. However, there are still a few kinks related to full-screen windows that I can't get around. I use full-screen windows a lot, so this is rather annoying. (Note that I have disabled "unredirect fullscreen windows" because of other issues, so every window should be treated the same way now. Compiz runs on the "intel" driver, if that affects anything. Also, when I say full-screen, I mean it, not just maximize.) 1) New windows appear below the fullscreen windows. How to reproduce: a) open Firefox (or a terminal or anything else) b) put the window in fullscreen mode (F11 works by default with Firefox and the terminal, but I have set Compiz to do that for every window). c) open a new window (I have the terminal on Start-T, but with Firefox you can use Ctrl-N, and with terminal Ctrl-Shift-T.) Results: a new window is (correctly) opened, it is given focus (correctly), but it's behind the full-screen window. Expected: the new window should be on top of the stack. I have to press Alt-Tab twice (first to return to the full-screen window, second to get to the newly-opened window) to get it to display. EDIT: Note that this happens for _every_ kind of new window that should appear on top, including dialogs opened by the full-screen window, which is the most annoying thing (think of save-to dialogs, exit confirmations, etc). 2) Windows disappear when dragged over a full-screen window. How to reproduce: a) open a small window (a terminal) b) open Firefox (or another terminal or anything else) c) put the second window in fullscreen mode d) alt-tab to the first window (non-fullscreen) You should have now the full-screen window on the whole screen, and exactly one window above it. e) drag the small window by left-clicking on its title-bar. Results: the window fades out (only the full-screen window is displayed). However, the move _does_ work (the moved window changes position), and the window doesn't loose focus (alt-tab returns to the full-screen window, and another alt-tab to the moved window). Strangely, if I use Alt+drag to move the window (that's a Compiz feature, I think it's enabled by default), the window doesn't disappear. Any ideas? ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello! I've just done a fresh install of Ubuntu Gutsy, and I'm currently quite pleased with how Compiz works. (I had Gutsy before (re-installed after some hardware problems), but Compiz didn't work very well, probably because of cruft accumulated through upgrades all the way from Dapper.) Now Compiz works great, and after a bit of configuring I'm actually more pleased with it than I ever was with Metacity. However, there are still a few kinks related to full-screen windows that I can't get around. I use full-screen windows a lot, so this is rather annoying. (Note that I have disabled "unredirect fullscreen windows" because of other issues, so every window should be treated the same way now. Compiz runs on the "intel" driver, if that affects anything. Also, when I say full-screen, I mean it, not just maximize.) 1) New windows appear below the fullscreen windows. How to reproduce: a) open Firefox (or a terminal or anything else) b) put the window in fullscreen mode (F11 works by default with Firefox and the terminal, but I have set Compiz to do that for every window). c) open a new window (I have the terminal on Start-T, but with Firefox you can use Ctrl-N, and with terminal Ctrl-Shift-T.) Results: a new window is (correctly) opened, it is given focus (correctly), but it's behind the full-screen window. Expected: the new window should be on top of the stack. I have to press Alt-Tab twice (first to return to the full-screen window, second to get to the newly-opened window) to get it to display. + EDIT: Note that this happens for _every_ kind of new window that should + appear on top, including dialogs opened by the full-screen window, which + is the most annoying thing (think of save-to dialogs, exit + confirmations, etc). + 2) Windows disappear when dragged over a full-screen window. How to reproduce: a) open a small window (a terminal) b) open Firefox (or another terminal or anything else) c) put the second window in fullscreen mode d) alt-tab to the first window (non-fullscreen) You should have now the full-screen window on the whole screen, and exactly one window above it. e) drag the small window by left-clicking on its title-bar. Results: th
[Bug 153969] avahi-autoipd takes over when the router fails, breaks DHCP
Public bug reported: I'm having a bit of an issue with avahi-daemon on Ubuntu Gutsy. My home network consists of an ADSL modem that includes a WiFi & ethernet router, into which I have plugged: 1) one laptop, running Gutsy, connected via ethernet; let's call it gutsy-eth. 2) one laptop, running Gutsy, connected via WiFi; let's call it gutsy-wifi. 3) some other computers I don't own, among which a Macbook running MacOS X. The router/modem has a DHCP server, which I normally use for configuring the network. (For practical reasons the router is not configurable, thus I have to just deal with how it works right now.) So normally every laptop connects to the network (via Network Manager for Linux, and whatever MacOS uses), asks for an address from the router's DHCP server, and stuff (almost) just works. Here come the problem: The router occasionally resets itself. I don't know why, and it's not really relevant. The important thing is that when this happens, it takes a couple minutes, sometimes longer, before each of its services come back up (ie, ethernet, wifi, internet, not necessarily in that order). The trouble is that when this happens, the network interfaces get disconnected (the ethernet laptop is plugged directly into the router, so it probably sees the cable disconnect during the reboot, and the wifi laptop just notices the wifi isn't working). At this point, the Network Manager starts trying to reconnect, which of course it can't because the router is still rebooting. At some point the networks are both working (ie, the interfaces come up), but for some reason the DHCP server isn't running yet on the router. So what happens is that dhclient tries for a bit, then gives up, and avahi-autoipd comes up and sets a link-local address (169.blah.blah). Then the DHCP server comes up, and the Macbook and other computers (not Gutsy on any of them) notice this, get an address, and just work. The issue is that the link-local address doesn't work for accessing the other computers. The two Gutsy machines can talk to each other, but (1) internet doesn't work, presumably because the gateway on the router is in the 192.168.1.* domain, (2) the other machines can't see the Gutsy computers, presumably because they're on the same 192.* domain where the DHCP server puts them, and (3) the Gutsy computers can't see the other machines, despite what /etc/network/if-up.d/avahi-autoipd claims to do (ie, add a default route to allow accessing non-link-local-addressed machines). When this happens (randomly, say at night) the two laptops essentially are removed from the network, which is annoying because (a) one of them serves files to the other machines and (b) I have to actually walk to each machine to reset its network. Now, I can't turn the entire network to link-local addresses (since I don't control all machines, including the router), and I don't really want to remove avahi-autoipd completely (since I do move the machines to other networks, occasionally; also, autoipd is cool). I was wondering if there's a way to (in order of preference): 1) Have the laptops to somehow notice when a DHCP server comes up, and switch from link-local addresses (if they have them) to a DHCP address; 2) Increase the timeout before dhclient gives up in favour of avahi-autoipd, to give enough time to the router to come up. 3) Disable avahi-autoipd without uninstalling it and without disturbing avahi-daemon services (eg, mDNS publishing/discovery on whatever connection method succeeded). ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- avahi-autoipd takes over when the router fails, breaks DHCP https://bugs.launchpad.net/bugs/153969 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124008] libcurl4-openssl no longer exists
Public bug reported: Binary package hint: curl Somewhere between https://launchpad.net/ubuntu/+source/curl/7.16.2-4ubuntu1 and https://launchpad.net/ubuntu/+source/curl/7.16.2-6ubuntu4 the libcurl4-openssl package disappeared. I don't know if that's intentional (libcurl4-openssl-dev still exists, apparently), but it's wreaking havoc with the package dependencies: $ sudo aptitude dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done Building tag database... Done The following packages are BROKEN: libcurl3-gnutls libcurl4-gnutls The following packages are unused and will be REMOVED: libcurl4-openssl The following packages will be upgraded: apport apport-gtk base-files compiz-fusion-plugins-main curl gnome-applets gnome-applets-data human-icon-theme initramfs-tools iptables kdelibs-data kdelibs4c2a libboost-date-time1.34.0 libboost-filesystem1.34.0 libboost-regex1.34.0 libboost-serialization1.34.0 libboost-thread1.34.0 libcurl3 libcurl4-openssl-dev libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglibmm-2.4-1c2a libglu1-mesa libglu1-mesa-dev libgtkmm-2.4-1c2a libmms0 libtotem-plparser7 libvlc0 libvolume-id0 mesa-common-dev mesa-utils mozilla-plugin-vlc python-apport python-celementtree python-launchpad-bugs python-problem-report sqlite3 tangerine-icon-theme totem totem-gstreamer totem-mozilla ubuntu-docs udev vim vim-common vim-runtime vim-tiny vlc vlc-nox volumeid 53 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 60.9MB of archives. After unpacking 26.9MB will be freed. The following packages have unmet dependencies: libcurl3-gnutls: Conflicts: libcurl4-gnutls but 7.16.2-6ubuntu3 is to be installed. libcurl4-gnutls: Depends: libcurl3-gnutls (= 7.16.2-6ubuntu3) but 7.16.2-6ubuntu4 is to be installed. Resolving dependencies... The following actions will resolve these dependencies: Remove the following packages: amarok amarok-engines amarok-xine language-support-fr libcurl4-gnutls libtunepimp5 libtunepimp5-mp3 openoffice.org openoffice.org-base openoffice.org-calc openoffice.org-common openoffice.org-core openoffice.org-draw openoffice.org-evolution openoffice.org-filter-binfilter openoffice.org-filter-mobiledev openoffice.org-gnome openoffice.org-gtk openoffice.org-help-en-us openoffice.org-help-fr openoffice.org-impress openoffice.org-java-common openoffice.org-l10n-en-us openoffice.org-l10n-fr openoffice.org-math openoffice.org-style-andromeda openoffice.org-style-crystal openoffice.org-style-human openoffice.org-style-industrial openoffice.org-thesaurus-en-us openoffice.org-writer python-pycurl python-uno thunderbird-locale-fr ubuntu-desktop xine-ui Leave the following dependencies unresolved: bzr recommends python-pycurl language-pack-fr-base recommends language-support-fr Score is -10824 ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- libcurl4-openssl no longer exists https://bugs.launchpad.net/bugs/124008 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124008] Re: libcurl4-openssl no longer exists
OK. I'll check it out in a few days. I didn't see any comments on that around the net. Is there any way of installing something in the meantime without breaking the installed packages? (Ignoring the mess with openssl?) -- libcurl4-openssl no longer exists https://bugs.launchpad.net/bugs/124008 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124008] Re: libcurl4-openssl no longer exists
I've been thinking: Shouldn't this bug be left "open" (or "in progress") until the migration is deemed complete? (It's still a bug even though it's "intentional" because it's not wanted behavior, it's a temporary side-effect of a change, like a (known) regression... right?) Since there are so many packages, there should be a way to know when things "should" be complete. That way I can tell if I get update errors because it's still being worked on or if I actually have something broken. -- libcurl4-openssl no longer exists https://bugs.launchpad.net/bugs/124008 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 116829] Re: White boxes where there should be shadows
Should this work correctly by now? I still get white bars around the panels and the menus, though shadows work correctly around "normal" windows. -- White boxes where there should be shadows https://bugs.launchpad.net/bugs/116829 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122941] Re: compiz.real crashed with SIGSEGV in exit()
It happens to me too, on an Intel video card. It happened when I tried to "restart" compiz with "compiz --replace" (it was working OK, just wanted to reload some settings), then when I tried the same thing using the "Desktop Effects" applet. -- compiz.real crashed with SIGSEGV in exit() https://bugs.launchpad.net/bugs/122941 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125642] compiz messes panels' auto-show
Public bug reported: Binary package hint: compiz I started compiz recently (to try it out), and noticed an annoying effect: Panels don't unhide normally. I have all panels (top and bottom) set to auto-hide. They normally unhide when I move the mouse to the top or the bottom. With compiz active they only seem to pop-up on the left top/bottom corners. (I don't have anything set-up on the top and bottom edges in compiz's settings.) ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- compiz messes panels' auto-show https://bugs.launchpad.net/bugs/125642 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80520] Re: azureus crashes when the network connection fails
I've just realized I didn't mention the work-around I found in this thread: I've noticed that the reason for the crashes, all crashes (at least on my computer) is not actually the network failure but the error dialog. I have checked the "Disable sliding animation/on top style for alert messages" option (Options>Interface>Display, almost at the bottom), and I didn't have _any_ crash since (it used to be very often). You need to use one of the other workarounds to get Azureus to start before doing that, of course. (You _might_ be able to rename the ~/.azureus folder, check the option, than re-name the folder back.) -- azureus crashes when the network connection fails https://bugs.launchpad.net/bugs/80520 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121415] Re: [gutsy] wireless doesn't work after booting with wireless switch off
I'm still getting this at least sometimes. I don't use the killswitch very often because of that, but it seems that the behavior changes from time to time. Before Gutsy, nm-applet would display the "disconnected" status when I killed the wireless, and automatically re-connected when I reset the switch. Right now, it can't tell the wireless is off, it just shows the "no signal" icon. After I reset the switch it doesn't do anything, and when I try to manually reconnect it can't (it tries for a while then stops with the "No network connection"). I just noticed that iwconfig says "eth1 no wireless extensions." after on/offing the killswitch --- but eth1 is my wireless card. So it might not be nm-applet's fault. -- [gutsy] wireless doesn't work after booting with wireless switch off https://bugs.launchpad.net/bugs/121415 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121415] Re: [gutsy] wireless doesn't work after booting with wireless switch off
Just to clarify: when I filed this bug, the killswitch worked as long as wireless was enabled at boot. Now it just permanently disables wireless. -- [gutsy] wireless doesn't work after booting with wireless switch off https://bugs.launchpad.net/bugs/121415 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121415] Re: [gutsy] wireless doesn't work after booting with wireless switch off
That would be very helpful if only suspend worked :) Time for another bug report... -- [gutsy] wireless doesn't work after booting with wireless switch off https://bugs.launchpad.net/bugs/121415 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44002] Re: Trivial actions are not appearing immediately
I'm sure something can be done about this. I've just done an strace on the menu opening, it tries to do ~1500 file opens (most of which are for non-existent files). First of all, most of those should be preloaded (actually, they should be cached once, then the cache should be preloaded in one step). The argument that it takes up memory doesn't hold, because the memory is still taken up the first time I open the menu. Second of all, any refresh can be done incrementally. There's no reason to flush the entire menu and re-open 1500 files, when one or two might be new. And especially you don't need to do it on every boot. Third, even a refresh could be done in parallel, with a "nice -n 10" to make sure things don't get unpleasant. Last, I don't even get it why it has to read the entire menu. If I'm going for the package manager I have no reason to wait for th 1500 file accesses, when it fact I'm only going to see about 20 icons on the way. -- Trivial actions are not appearing immediately https://bugs.launchpad.net/bugs/44002 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121415] Re: [gutsy] wireless doesn't work after booting with wireless switch off
I noticed something weird: the failure, whatever may be causing it, appears to be intermittent. Yesterday I accidentally booted up with the wireless disabled via the switch, and when I flicked the switch back the wireless turned on. It's totally weird, this never happened before _and_ I'm sure I haven't done upgrades since the last post. -- [gutsy] wireless doesn't work after booting with wireless switch off https://bugs.launchpad.net/bugs/121415 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127168] vesafb sets the refresh rate too high for some LCDs
Public bug reported: Binary package hint: linux-image-2.6-386 Hello! I'm running Ubuntu Gutsy on a Dell Latitude D620 laptop with Intel integrated video. See ddcprobe below. X runs very well with the intel driver, although I'm using 915resolution to get the native display resolution programmed into the video board (1280x1024). I've been trying for a week to get the same results in the console (or at least more than VGA), with no success. I can't get intelfb to work (I suspect vesafb is disabling it somehow, but I can't check until I compile a new kernel, maybe later). So I tried using the vesafb to get larger resolutions (1024x768), adding this line (or similar) to the kernel parameters: "video=vesafb:mtrr,ywrap,maxvf=60,[EMAIL PROTECTED] vga=0x317 hsync=60" I've tried any combinations of the parameters, different resolutions, bitdepths and refresh rates. It seems to work, according to the messages, but all I get is a blank, black screen. X comes up normally when the boot is over. I can switch back and forth between X and the consoles, but the consoles are always blank. $ fbset mode "1024x768-76" # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz geometry 1024 768 1024 768 16 timings 12714 128 32 16 4 128 4 rgba 5/11,6/5,5/0,0/0 endmode According to fbset the refresh rate is always set at 76 Hz, and I'm sure the screen allows only 60 (or 70, maybe, but I don't think so). This is not a problem, since it's an LCD. I know people have been asking for higher refresh rates at boot for a long time (for CRTs), so maybe this is what caused the change (it worked in Dapper or Feisty, not sure which). Is there any way to get a lower refresh rate (preferably without recompiling the kernel)? And is there any way to detect laptops with such problems and fix it automatically? $ sudo ddcprobe vbe: VESA 3.0 detected. oem: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS vendor: Intel Corporation product: Intel(r) 82945GM Chipset Family Graphics Controller Hardware Version 0.0 memory: 12288kb mode: 1280x1024x256 mode: 1280x1024x64k mode: 1280x1024x16m mode: 1024x768x256 mode: 1024x768x64k mode: 1024x768x16m mode: 640x480x16m mode: 800x600x64k mode: 800x600x16m mode: 640x480x256 mode: 800x600x256 mode: 640x480x64k edid: edid: 1 3 id: 3157 eisa: SEC3157 serial: manufacture: 0 2005 input: analog signal. screensize: 30 19 gamma: 2.20 dpms: RGB, no active off, no suspend, no standby dtiming: [EMAIL PROTECTED] monitorid: UD490141W1 monitorid: '7?Og��� $ lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 03:01.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller (rev 40) 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02) 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- vesafb sets the refresh rate too high for some LCDs https://bugs.launchpad.net/bugs/127168 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127243] update-manager (and others) should lower their priority when working
Public bug reported: Binary package hint: update-manager This is more a feature request rather than a bug (though it could be seen as a usability bug). It concerns mainly Gutsy as it's the development branch, but it applies to the other versions too. Except for viewing and picking updates, everything the Update Manager does (installing and removing packages) is intrinsically slow and not at all urgent. The Update Manager should do all the "real work" --- updating and removing packages, loading the package list and building the dependency tree, etc --- in a low-priority (not idle, just lower than interactive), with only the interface running interactively. Especially the updates should be very easy to do with lower priority, because they're run by dpkg (or apt-get, I'm not sure), but even reading the package list should be done the same way (with care to keep the interface interactive). The current behavior can turn even a dual-core machine unresponsive for some time. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager (and others) should lower their priority when working https://bugs.launchpad.net/bugs/127243 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127376] ccache should add a group of alternatives for cc, c++ and gcc
Public bug reported: Binary package hint: ccache Ubuntu uses update-alternatives to manage and decide which of several alternatives can be used for a certain function. CCache should use this system to allow the user to automatically configure their system to use ccache on compilation. ** Affects: ccache (Ubuntu) Importance: Undecided Status: New -- ccache should add a group of alternatives for cc, c++ and gcc https://bugs.launchpad.net/bugs/127376 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127649] nm-applet doesn't work unless I start dhclient manually
Public bug reported: Binary package hint: network-manager-gnome Hello! Weird issue with the network-manager applet. (Up-to-date Gutsy, on a laptop with an Intel ipw3945 chipset, running the 2.6.22-8-generic kernel.) This started quite some time ago (maybe more than a month), but I initially dismissed it (I had bigger problems with it). It still didn't go away, though. When I login (at home) the NM attempts to connect automatically to my wifi router, which it knows about and whose password is in the keyring. The keyring asks for the password, I give it, and then the weirdness starts: NM acts as it does during the connection phase, it actually connects (I can see the ESSID associated in iwconfig), but then disconnects and asks for the network key. When I give it the network key it goes through the same stages again, and asks again for the key. While trying to see what's wrong I noticed that if I manually start "sudo dhclient eth1" (eth1 is the wireless card) and _then_ I give NM the key (either at start when I unlock the keyring, or afterwards when it asks for it) the connection is completed correctly. Everything works afterwards (well, there are some bugs with the RF-switch, but that's another bug report.) I'm quite sure NM also starts the dhclient, because sometimes the one I start manually complains about files already existing before quitting. Also, every once in a blue moon NM actually completes the connection itself without me starting the dhclient. I suspect some sort of timeout causes it to thing dhclient isn't working and to kill it, but I'm just guessing. I'm leaving the country in a couple of days, so I may not be able to answer any questions until a couple of weeks from now, but maybe someone can take a look at likely causes and see something fishy. Here's what dmesg says when the card is detected: [ 17.416000] ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.1mp [ 17.416000] ipw3945: Copyright(c) 2003-2006 Intel Corporation [ 17.42] ACPI: PCI Interrupt :0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17 [ 17.42] PCI: Setting latency timer of device :0c:00.0 to 64 [ 17.42] ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection Here's what I have in my /var/log/daemon.log from my last boot around the time NM started. (I'm sorry, I don't remember for sure, but I think I might have started dhclient from the start; if I have time before I leave tomorrow I'll make a new post with a failure recorded, too.) It's mixed with messages from Avahi, I left them as they might be relevant. Jul 23 01:25:18 cimer NetworkManager: starting... Jul 23 01:25:18 cimer NetworkManager: nm_policy_device_change_check:: !old_dev && !new_dev!! Jul 23 01:25:22 cimer pdnsd[8056]: pdnsd-1.2.6-par starting. Jul 23 01:25:22 cimer pdnsd[8056]: icmp ping: sendto() failed: Network is unreachable. Jul 23 01:25:22 cimer pdnsd[8056]: icmp ping: sendto() failed: Network is unreachable. Jul 23 01:25:22 cimer rpc.statd[8189]: Version 1.1.0 Starting Jul 23 01:25:22 cimer rpc.statd[8189]: statd running as root. chown /var/lib/nfs/sm to choose different user Jul 23 01:25:23 cimer ntpd[8324]: ntpd [EMAIL PROTECTED] Fri May 18 15:01:09 UTC 2007 (1) Jul 23 01:25:23 cimer ntpd[8336]: precision = 1.000 usec Jul 23 01:25:23 cimer ntpd[8336]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jul 23 01:25:23 cimer ntpd[8336]: Listening on interface #1 wildcard, ::#123 Disabled Jul 23 01:25:23 cimer ntpd[8336]: Listening on interface #2 lo, ::1#123 Enabled Jul 23 01:25:23 cimer ntpd[8336]: Listening on interface #3 lo, 127.0.0.1#123 Enabled Jul 23 01:25:23 cimer ntpd[8336]: kernel time sync status 0040 Jul 23 01:25:23 cimer ntpd[8336]: frequency initialized -19.599 PPM from /var/lib/ntp/ntp.drift Jul 23 01:25:23 cimer ntpd[8336]: Cannot find existing interface for address 82.211.81.145 Jul 23 01:25:23 cimer ntpd[8336]: configuration of 82.211.81.145 failed Jul 23 01:25:25 cimer NetworkManager: eth1: Device is fully-supported using driver 'ipw3945'. Jul 23 01:25:25 cimer NetworkManager: nm_device_init(): waiting for device's worker thread to start Jul 23 01:25:25 cimer NetworkManager: nm_device_init(): device's worker thread started, continuing. Jul 23 01:25:25 cimer NetworkManager: Now managing wireless (802.11) device 'eth1'. Jul 23 01:25:25 cimer NetworkManager: Deactivating device eth1. Jul 23 01:25:25 cimer NetworkManager: eth0: Device is fully-supported using driver 'tg3'. Jul 23 01:25:25 cimer NetworkManager: nm_device_init(): waiting for device's worker thread to start Jul 23 01:25:25 cimer NetworkManager: nm_device_init(): device's worker thread started, continuing. Jul 23 01:25:25 cimer NetworkManager: Now managing wired Ethernet (802.3) device 'eth0'. Jul 23 01:25:25 cimer NetworkManager: Deactivating device eth0. Jul 23 01:25:25 cimer NetworkManager: [1185146725.996723] nm_hal_device_added(): New device
[Bug 127649] Re: nm-applet doesn't work unless I start dhclient manually
Actually no, the SSID is broadcasted. But your post reminded me to post a bit more info: The network is based around a IEEE 802.11 a/b/g router, set up to function only as "g". Security is WPA2-PSK(AES). $ iwconfig lono wireless extensions. eth0 no wireless extensions. eth1 IEEE 802.11g ESSID:"SpeedTouch324B2B" Mode:Managed Frequency:2.472 GHz Access Point: 00:14:7F:78:42:89 Bit Rate:54 Mb/s Tx-Power:15 dBm Retry limit:15 RTS thr:off Fragment thr:off Power Management:off Link Quality=95/100 Signal level=-32 dBm Noise level=-33 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:38332 Missed beacon:0 -- nm-applet doesn't work unless I start dhclient manually https://bugs.launchpad.net/bugs/127649 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127649] Re: nm-applet doesn't work unless I start dhclient manually
I've just done a restart and recorded the logs for the entire procedure. When I log in, the first thing that pops up is the keyring dialog asking for the keyring password. I started iwevent in a console (so every event that came up before this doesn't appear), then: (1) I unlocked the keyring. The events from the start until about 09:56:09 are from that time. Then, the NM dialog asking for the wireless password comes up. (Interestingly, the not-associated message at 9:56:27 comes up _after_ the dialog appears. (2) Then I give the network password, and the same thing happens. (The dialog asking for the password appears before the "non-associated" event. While I was opening a console to start dhclient, I noticed that the cycle of association/disassociation comes up several times, without me entering the password. (3) I start "sudo dhclient eth1" and give the network password to NM. The address comes up immediately: ** $ sudo dhclient eth1 [sudo] password for bogdanb: Internet Systems Consortium DHCP Client V3.0.5 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth1/00:18:de:b2:c8:80 Sending on LPF/eth1/00:18:de:b2:c8:80 Sending on Socket/fallback DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPACK from 192.168.1.254 bound to 192.168.1.66 -- renewal in 34663 seconds. $ date Mon Jul 23 09:56:07 CEST 2007 ** Below is the /var/log/daemon.log file between the boot time and until after the network started. What I noticed for the first time today is that lots of messages from rrd_update appear at the bottom; I didn't notice them before, they might be caused by the fact that yesterday I uninstalled ntpd. Second, during the password entry above I noticed the system clock does something weird; the clock applet wasn't well synchronized with the timestamps given by iwevent; it seemed about a minute fast. If the cause is a timeout as per my suspicion in the first post, maybe it's caused by some re-aligning of the clock at boot. (Though it's a bit late for that when GDM started already, isn't it?) ** Jul 23 09:43:58 cimer collectd[8849]: Cannot open `/proc/16343/stat': No such file or directory Jul 23 09:43:58 cimer collectd[8849]: Cannot open `/proc/16344/stat': No such file or directory Jul 23 09:43:58 cimer collectd[8849]: Cannot open `/proc/16345/stat': No such file or directory Jul 23 09:54:03 cimer init: tty4 main process (6798) killed by TERM signal Jul 23 09:54:03 cimer init: tty5 main process (6799) killed by TERM signal Jul 23 09:54:03 cimer init: tty2 main process (6803) killed by TERM signal Jul 23 09:54:03 cimer init: tty3 main process (6804) killed by TERM signal Jul 23 09:54:03 cimer init: tty1 main process (6805) killed by TERM signal Jul 23 09:54:03 cimer init: tty6 main process (6806) killed by TERM signal Jul 23 09:54:08 cimer NetworkManager: nm_signal_handler(): Caught signal 15, shutting down normally. Jul 23 09:54:08 cimer NetworkManager: Caught terminiation signal Jul 23 09:54:08 cimer NetworkManager: [1185177248.695828] nm_print_open_socks(): Open Sockets List: Jul 23 09:54:08 cimer NetworkManager: [1185177248.695875] nm_print_open_socks(): Open Sockets List Done. Jul 23 09:54:08 cimer NetworkManager: Deactivating device eth1. Jul 23 09:54:08 cimer avahi-daemon[8647]: Withdrawing address record for 192.168.1.66 on eth1. Jul 23 09:54:08 cimer avahi-daemon[8647]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.66. Jul 23 09:54:08 cimer avahi-daemon[8647]: Interface eth1.IPv4 no longer relevant for mDNS. Jul 23 09:54:08 cimer avahi-daemon[8647]: Withdrawing address record for fe80::218:deff:feb2:c880 on eth1. Jul 23 09:54:08 cimer dhclient: receive_packet failed on eth1: Network is down Jul 23 09:54:08 cimer dhclient: receive_packet failed on eth1: Network is down Jul 23 09:54:08 cimer NetworkManager: Deactivating device eth0. Jul 23 09:54:08 cimer avahi-daemon[8647]: Disconnected from D-Bus, exiting. Jul 23 09:54:08 cimer avahi-daemon[8647]: Got SIGQUIT, quitting. Jul 23 09:54:10 cimer pdnsd[8056]: Caught signal 15. Exiting. Jul 23 09:54:13 cimer rpc.statd[8189]: Caught signal 15, un-registering and exiting. Jul 23 09:55:15 cimer NetworkManager: starting... Jul 23 09:55:15 cimer NetworkManager: nm_policy_device_change_check:: !old_dev && !new_dev!! Jul 23 09:55:19 cimer pdnsd[8165]: pdnsd-1.2.6-par starting. Jul 23 09:55:19 cimer pdnsd[8165]: icmp ping: sendto() failed: Network is unreachable. Jul 23 09:55:19 cimer pdnsd[8165]: icmp ping: sendto() failed: Network is unreachable. Jul 23 09:55:19 cimer rpc.statd[8298]: Version 1.1.0 Starting Jul 23 09:55:19 cimer rpc.statd[8298]: statd running as root. chown /var/lib/nfs/sm to choose different user Jul 23 09:55:22 cimer NetworkManager: eth1: Device is fully-supported using driver 'ipw3945'. Jul 23 09:55:22 cimer NetworkManager: nm_dev
[Bug 76788] Re: pulseaudio-module-hal does not detect sound hardware
Is there a way to tell when this is actually available? That is, either to anticipate in what package version of the kernel it'll be present, or to follow it somehow? I'd like to know when I can try if it works, and I have no idea how long it takes between the fix being merged upstream and apt-get installing it. -- pulseaudio-module-hal does not detect sound hardware https://launchpad.net/bugs/76788 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84467] md5sum can't read md5 files with CRLF line terminators
Public bug reported: Binary package hint: coreutils I know this is going to be weird, but... I'd very much like it if tools like md5sum handled files with CRLF terminators better. I just tried checking a set of files using an .md5 summary generated on windows, and it doesn't work. (1) This is really annoying. It took me five minutes to figure out that it was the line terminators that were the problem. This was compounded by the fact that neither "cat", "vi" nor "gedit" show any sign of the distinction by default. (2) This kind of issue is never going away, and it'll only grow with more people using both systems. Already most tools, including almost every text editor, do this by default. (3) It's more than annoying: I intended to write a script that (among many other things) checks such files often. If I need to check the line terminators myself, it's going to take several times more effort. (Well, at least double the amount.) And this will have to be done for all such scripts. (4) In the case of md5sum, there really is no excuse not to accept the other kind of terminators. The syntax of the .md5 files is _very_ easy to parse, CRLF terminators never change in any way the semantic, and reading the .md5 files is a negligible effort compared with actually checking the hashes, so there's no "inefficiency" problem. There's no chance of backwards incompatibility, as long as output always uses the same terminators it used to. (5) The current errors shown for such files are nonsensical. (More precisely, they don't indicate the problem unless you're already familiar with it.) This feature request is written for md5sum because that's where I had a problem, but I'm sure this applies for many other core utils. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: Unconfirmed -- md5sum can't read md5 files with CRLF line terminators https://launchpad.net/bugs/84467 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84722] deskbar-applet requires too many keystrokes
Public bug reported: Binary package hint: deskbar-applet The deskbar applet is a bit annoying by needing too many clicks/keystrokes to use. There's a bit too much redundancy. Consider the attached screenshot: I write picard in the entry. The first line accessible with the arrows is the "Action" category -- which is unnecessary because there's no other category right now. Also, assuming the deskbar guessed right, it seems that you have to click 'down' twice to get at the first result. (I know I just have to press Enter, but that's not obvious; perhaps the "active" line should be selected, so I have a suggestion of what would happen when I press Enter.) Then, running Picard is presented twice. There's no difference between the two options. Perhaps they should be combined, or at least move the least likely one at the bottom of the list (the one taken from the apps menu is prettier). As it is now, if I wanted to actually search for picard in beagle, I would have to press 'down' four times, then Enter, when it fact it is the second option. As it should be, the first entry should be always selected (and activated at the first Enter press), the 'search in picard' should be immediately below it, and the first 'down arrow' press should select it. Another thing: since the deskbar is supposed to allow keyboard navigation, the most likely entries should have shortcuts, either like Alt+3 to _run_ the third option or Alt+b to choose beagle search, Alt+g for google, etc. for some standard ones. Actually, since beagle also searches for applications and stuff, perhaps it would be nice to actually display beagle search _results_ in real time in the box. It would jump over one new window display and one Enter press. ** Affects: deskbar-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
Nevermind that last paragraph, I just found out it can do live search. ** Attachment added: "screenshot of the issues in the first post" http://librarian.launchpad.net/6398010/screenshot.png -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
But I still don't like it because of navigation issues :-)
For the same simple search ("picard"), I get a screen-high list of
things --- with a scrollbar, that can' be mouse-clicked! -- that is
near-impossible to walk through.
In this example, categories with more than, say, five entries, should display
only the likeliest three (or the first if there's no other info) and allow easy
navigation: for instance, in this example:
- the Files section should display only three entries, among which should be
the picard folder (that's currently near the bottom)
- the Files section should have an Alt-F shortcut marked near its title. When I
press it, the section should be selected, and:
- left/right should navigate between pages
- space should toggle between the contracted and and "expanded" list
- enter should probably open the first hit, and 'down arrow' should probably
select the second hit.
** Attachment added: "too large list"
http://librarian.launchpad.net/6398022/Screenshot2.png
--
deskbar-applet requires too many keystrokes
https://launchpad.net/bugs/84722
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
Here's a sketch of how it could (and I think it should) work by default (compare with the previous "too large list" screenshot): *) sections: - Section markers can't be "selected" (only action-lines can be), but the one containing the currently selected action is "active". Up-down skips the section markers. - The currently inactive sections have shortcuts to be reached quickly. - the active section shows useful keys: up/down, space for a short section, left/right, space for a large section. Up/down work for large selections too, of course, but left/right is a bit more important (it changes the page). - space toggles the current section between normal (at-most-three entries), expanded (see last panel) and compacted. When one selection is expanded this way, the others are compacted. I think "expanded" status should be forgotten between uses, but compacted should be remembered (as it is now). - the active section should be visibly marked as "selected" by color (it was too hard to draw, I show this as a bar of color). This should be less striking than the color used to highlight the current action (black in my sketch, it could just be darker). - sections with more than 4 entries are paged by each 3 elements (unless there are no other sections for a particular search) - sections with few entries (which are not paged) don't display the number on the right. *) Actions: - sections are paged/compacted so that no more than a dozen actions are shown - users can add a short-cut for important actions -- Alt-G for google in this case. - All other visible actions are given a number from 1 to 0 as a shortcut. Pressing Alt+4 in the first panel would open album.py - Except: the currently selected action has Enter shown. The numbers are "recycled" when the selection is moved with up/down. (see last panel) - Also, actions with shortcuts are skipped. - Since no more than 10-12 actions are shown, we shouldn't run out of numbers. The left panel is what should be shown after just typing "picard". Note: - the redundant "execute picard" is hidden from the actions - the most likely choice (Launch picard) is selected. It shows "Enter" to the left, meaning that Enter will execute that option. - pressing Alt+1-9 or Alt-G would execute the respective action. - pressing down would select "search for picard using beagle" - launch picard will show (alt+)1 as a shortcut, because enter now starts the search Pressing Alt+F moves to the middle panel: - the files section is active - since it has many results, it's paged into "threes". If the 'web' section wouldn't be there, it could be paged into sixes. - because it's now active, it shows useful key-strokes - because it's paged, left-right can cycle between pages; space would move to the right-most panel - because it's no longer active, the "Actions" section shows a short-cut instead of actions. - the "Open [folder] picarded" action is the first in the active section, so it's selected - it gets the "enter" shortcut, and the numbers are redistributed. - down would move to "open album.py" - up would move the selection to "Search for picard using Beagle", and the Actions section would become active. Pressing "space" expands the current section if it's paged. This moves to the rightmost panel (but the list of files shouldn't change, neither the selection): - all inactive sections are colapsed - pressing their shortcut would de-expand and de-activate the files section. - even short sections show the number of actions in this state - the active section expands to fill all 10 action-slots available - pressing space again would reverse the expansion - any sections 'colapsed' before the expansion remain colapsed - if it has more than 10 entries, it is still paged with left/right ** Attachment added: "mock of desired navigation" http://librarian.launchpad.net/6399505/sketch.png -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68020] Re: Azureus 2.5.0.0 crashes
As a summary for anyone who might work on this: 1) Running under GCJ fixes the crash on start for me, but it seems to use at least three time more memory and processor, so I didn't run it long enough to discover more crashes. 2) Under Java, it seems to crash whenever anything goes wrong: a) if the WiFi connection drops temporarily. By the way, if I turn from WiFi to Ethernet Azureus crashes on start for ever, even with GCJ, until I re-enable WiFi. b) I have Azureus move files on an almost-always connected USB drive. If it's read-only or not connected, it crashes. c) if anything unusual happens to the files it's using (like, if I delete or move by mistake a file that's being written to or read from. d) if the gnome-panel is restarted (!) as a result of an update. (No other program crashes in that case.) Usually these can be worked around by fixing the cause, then deleting the crash report and the log. Unfortunately, sometimes there's something wrong with the config file, which needs deleting the whole ~/.azureus directory and manually re-configuring and re-starting the torrents. Which is annoying. Seeing as it seems to crash whenever anything unusual happens, as well as on startup after it, I think it's related in all cases to the warning dialog it tries to show. (Someone earlier pointed out it's the pop-up window that seems to be the problem.) I couldn't find a way to disable warnings, but I just toggled all related options to see if it changes anything (sliding, on top, auto-hide). -- Azureus 2.5.0.0 crashes https://launchpad.net/bugs/68020 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82463] Re: monitor remains blank after quick close/open lid cycle
Damn it, each time I post a bug report I forget to say what linux I use... OK, here they come: [EMAIL PROTECTED]:~$ uname -a Linux bogdanb-d620 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux (By the way, this shouldn't matter, but I used to use the -lowlatency kernel too, with the same results.) ** Attachment added: "Output of "sudo lspci -vv"" http://librarian.launchpad.net/6423816/lspci-vv.txt -- monitor remains blank after quick close/open lid cycle https://launchpad.net/bugs/82463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82463] Re: monitor remains blank after quick close/open lid cycle
** Attachment added: "Output of "sudo lspci -vvn"" http://librarian.launchpad.net/6423817/lspci-vvn.txt -- monitor remains blank after quick close/open lid cycle https://launchpad.net/bugs/82463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82463] Re: monitor remains blank after quick close/open lid cycle
** Attachment added: "Output of "sudo dmidecode"" http://librarian.launchpad.net/6423818/dmidecode.txt -- monitor remains blank after quick close/open lid cycle https://launchpad.net/bugs/82463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82463] Re: monitor remains blank after quick close/open lid cycle
And of course, I forgot again. This is on Ubuntu Feisty. -- monitor remains blank after quick close/open lid cycle https://launchpad.net/bugs/82463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82463] Re: monitor remains blank after quick close/open lid cycle
'lshal -m' doesn't output anything, even with sudo. I tried "lshal --monitor" and it works: First, I started the monitor, I closed the lid, counted to ten, then I opened it. (Incidentally, gnome-screensaver refuses to unlock the screen, but this is unrelated, I think, because they often happen separately.) $ sudo lshal --monitor Start monitoring devicelist: - acpi_LID property button.state.value = true acpi_LID condition ButtonPressed = lid acpi_BAT0 property battery.voltage.current = 12421 (0x3085) acpi_LID property button.state.value = false acpi_LID condition ButtonPressed = lid acpi_BAT0 property battery.voltage.current = 12420 (0x3084) *** Then I restarted 'ls-hal --monitor', I closed the lid and re-opened it immediately; it remained blank. I counted to ten and then again closed and opened it immediately. The second time it turned on. $ sudo lshal --monitor Start monitoring devicelist: - acpi_LID condition ButtonPressed = lid acpi_LID condition ButtonPressed = lid acpi_LID property button.state.value = true acpi_LID condition ButtonPressed = lid acpi_BAT0 property battery.voltage.current = 12419 (0x3083) acpi_LID property button.state.value = false acpi_LID condition ButtonPressed = lid acpi_BAT0 property battery.voltage.current = 12420 (0x3084) -- monitor remains blank after quick close/open lid cycle https://launchpad.net/bugs/82463 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76788] Re: pulseaudio-module-hal does not detect sound hardware
Yes, it works now. Thanks everyone! -- pulseaudio-module-hal does not detect sound hardware https://launchpad.net/bugs/76788 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85791] when sound hardware fails, amarok locks the computer trying to play all songs in playlist
Public bug reported: Binary package hint: amarok This is rather unpleasant issue. I'm having some problems with pulseaudio, which means that occasionally the sound hardware goes down and Amarok receives an error from Xine. This is not Amarok's fault. The problem is that when that happens, Amarok displays a warning message, but instead of stopping it keeps trying to play each track in the playlist in turn. Each time a track starts playing Amarok hogs the processor -- I assume it starts building the 'track info' panel and even decoding the file before it notices the sound doesn't work. So it moves to the next file and again hogs the processor. The result is that (a) nothing works on my computer anymore until it finishes the playlist and (b) I can't turn Amarok off until it finishes the playlist (because it didn't allow me to press any buttons, and I couldn't even start a terminal or switch to a console; and it was a looong playlist). I suppose if I had auto-repeat on I would need to restart the computer. This is double-weird as I have a Core Duo processor and low-latency kernel... Note that I have had the same problem with Amarok with different causes (i.e., external drive failed, etc). So I see it as a general issue, rather than just the 'sound hardware doesn't work'. I think Amarok should stop trying to play things automatically when it detects the same error consecutively for a few times, until it receives user direction. Also, this is a bit of an Ubuntu problem too, as it amounts to a nice denial of service technique. Would it be possible to dynamically nice a normal-priority process that has been using up 90% of the processor for the last second or so? (Excepting, perhaps, root processes and maybe higher-than-normal priority processes.) The point is, you should be able to at least move to a console and start a terminal to kill an aberrant process. ** Affects: amarok (Ubuntu) Importance: Undecided Status: Unconfirmed -- when sound hardware fails, amarok locks the computer trying to play all songs in playlist https://launchpad.net/bugs/85791 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 85791] Re: when sound hardware fails, amarok locks the computer trying to play all songs in playlist
This is probably the same issue as Bug #45814, but in his case it was the codec that was missing, so presumably the system was still responsive. -- when sound hardware fails, amarok locks the computer trying to play all songs in playlist https://launchpad.net/bugs/85791 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 85791] Re: when sound hardware fails, amarok locks the computer trying to play all songs in playlist
Dammit, I _always_ forget to say things like that. It just happened with 1.4.5, but it had this behavior for as long as I've been using it, i.e. at least five months. I'm using Feisty, but it did the same on Edgy, too. -- when sound hardware fails, amarok locks the computer trying to play all songs in playlist https://launchpad.net/bugs/85791 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 85791] Re: when sound hardware fails, amarok locks the computer trying to play all songs in playlist
Well, the pulseaudio issue is not relevant for the Amarok problems. The Amarok bug manifests itself whenever the sound hardware becomes unavailable, no matter why. In this case it was triggered by a pulseaudio problem, but that's not relevant. It's Amarok's behavior that blocks the computer. (If you just want to simulate the bug, I _think_ you can install pulseaudio, configure it to intercept alsa, and kill the pulseaudio daemon while Amarok is playing. This should cause the same effect. In my case the bug was caused by Flash 9 hogging the audio server, but really that's another issue. I have a support question up about it.) -- when sound hardware fails, amarok locks the computer trying to play all songs in playlist https://launchpad.net/bugs/85791 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 86031] amarok has large delay on play/pause when using pulseaudio/xine
Public bug reported: Binary package hint: amarok Hi! Just so I don't forget, this is about Amarok on Ubuntu Feisty. All mentioned packages are from the repositories and up-to-date. The computer is a Centrino Duo, running the latest of either linux-generic or linux-lowlatency (the problems below happen on both). I installed Pulseaudio recently, and got it working on most applications. Amarok uses the Xine engine, which has the option of using Pulseaudio directly or through Alsa. (Because pulseaudio simulates an Alsa output.) If I use the Alsa version, it plays OK. However each time I press play or pause there is a ~2.5 second delay before it actually happens. This is rather annoying. (I don't have any fadeouts/crossfades enabled.) If I use the Pulseaudio output, it gets even more annoying: play and stop don't have any delay (anyway, less than a sec). However, if I press pause while playing the sound stops immediately, but Amarok freezes for 10-12 seconds. During this time "amarokapp" is still displayed in the Pulseaudio Manager, and it disappears the moment Amarok unfreezes. I tried the xine player with the same settings, and it doesn't have any delay with neither Alsa nor Pulseaudio output. ** Affects: amarok (Ubuntu) Importance: Undecided Status: Unconfirmed -- amarok has large delay on play/pause when using pulseaudio/xine https://launchpad.net/bugs/86031 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86033] libtunepimp is compiled without mp4/m4a support
Public bug reported: This is about Ubuntu Feisty. As the summary says, libtunepimp is compiled without support for mp4 (and, implicitly, m4a) files. This means that such files cannot be tagged using applications that rely on it, e.g. Picard. ** Affects: libtunepimp (Ubuntu) Importance: Undecided Status: Unconfirmed -- libtunepimp is compiled without mp4/m4a support https://launchpad.net/bugs/86033 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68020] Re: Azureus 2.5.0.0 crashes
After I disabled the sliding animation/on top for error dialogs --- see Options/Interface/Display, near the bottom of the panel --- I don't think I had crashes on start-up anymore. I just restarted my computer because of a display bug, and Azureus was running. Usually that means that it will crash on restart, unless I delete the log/crash files. However, now it just displayed a normal dialog warning me of it not being closed normally, and then everything worked normally. The bug is still there, I suppose, but this is a good work-around until it will be fixed. -- Azureus 2.5.0.0 crashes https://launchpad.net/bugs/68020 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79633] Network-config doesn't start the network
Public bug reported:
Binary package hint: gnome-system-tools
Hi! I have a Dell Latitude D620 laptop, which includes both wireless and
Ethernet adapters. For some reason, the network-admin applet doesn't
seem to work anymore. It worked just fine a couple of hours ago.
I have an ADSL modem+router that allows both wired and wireless
connection at home. I prefer to use wireless, and it worked just fine
until this morning. I went to school, where I use a wired connection.
Everything (at home and at school) is DHCP-configured.
For some reason when I got home I couldn't get the network-admin applet
to do anything. I would click on the network icon on the panel, pick my
ssid and enter the password for the wireless link, enable DHCP, click
OK, and nothing happens.
As far as I can tell, some Perl scripts are frozen:
[EMAIL PROTECTED]:~$ ps -A -f |grep perl
root 6151 1 0 21:09 ?00:00:00 perl
/usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m
HostsConfig
root 6155 1 0 21:09 ?00:00:00 perl
/usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m Platform
root 6161 1 1 21:09 ?00:00:00 perl
/usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m
IfacesConfig
bogdanb 6234 6057 0 21:09 pts/000:00:00 grep perl
**
I couldn't get the wired connection either, but I'm not sure if it's because
there's some process hanging. (I did kill the perl scripts before trying,
though.)
After several trials I had to enable the wired connection by hand
("ifconfig eth0 up" and "dhclient eth0"). I have no idea how to start
the wireless by hand, though.
Let me know if there's any info that I can give to elucidate this.
** Affects: gnome-system-tools (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Network-config doesn't start the network
https://launchpad.net/bugs/79633
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80274] gnome-app-install crashes on start
Public bug reported: Binary package hint: gnome-app-install I started the gnome-app-install applet from the Applications menu and it crashed. The window appeared, with all in-window controls disabled, and a progress bar advancing rapidly. (Presumably, it enumerated the installed package list or something like that.) As far as I could see it crashed either during or immediately after that stage. The bug reporter asked me to add a .crash file, I'll do it right away. I use Synaptic and aptitude usually, this was just a whim, so I'm not sure if it's common. (By the way, Synaptic works right now, so the package lists should be OK.) I'll try again later to see if it still crashes. Let me know if I can add any information. ** Affects: gnome-app-install (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-app-install crashes on start https://launchpad.net/bugs/80274 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80274] Re: gnome-app-install crashes on start
** Attachment added: "Crash summary." http://librarian.launchpad.net/5778443/_usr_bin_gnome-app-install.1000.crash -- gnome-app-install crashes on start https://launchpad.net/bugs/80274 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80274] Re: gnome-app-install crashes on start
Yes, it still crashes while that first progress-bar is growing. -- gnome-app-install crashes on start https://launchpad.net/bugs/80274 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80444] kde settings mess-up
Public bug reported: Binary package hint: kde OK, this is one of the weirdest issues I had with Ubuntu. I'm not sure where to put it, I though I'd place it in "kde" and see if anyone can suggest a better spot. Bear with me: I use Ubuntu Feisty (all repositories including multiverse; I installed Dapper and updated from there), with the Gnome interface, on a Dell Latitude D620 laptop. (I'll fill in with more details if asked.) The only KDE thing I use is Amarok (well, Qt, anyway). My problems all started when I noticed that the fonts in Amarok got rendered uglier than those in the other applications. As far as I can tell, they were (and still are) rendered with anti-aliasing (grayscale, I think) without hinting. (I had fonts set-up to my taste, using the default Gnome applet, when I installed Ubuntu, with full hinting and sub-pixel AA. It worked just right in both Gnome apps and Amarok.) I don't know what triggered the change, it was probably an update of some Qt thing. I didn't notice this right away, so I'm not sure. I tried looking for info on the forums -- http://ubuntuforums.org/showthread.php?t=336229 -- because I'm not really familiar with KDE. A few guys tried to help me by suggesting I install kcontrol and use it to change KDE's font settings. (That's what I wanted to do, I just didn't know the name of the package.) For some reason, the kcontrol window did not display any actual settings pages. I tried installing kde-core, kdebase, and finally the whole kde package. After any number of restarts/logins, I still didn't find any controls in kcontrol. I also tried qt3-qtconfig, but it only allows picking fonts, not the rendering options. Any idea what I can do? I'm really only interested about fixing the font rendering, but if I can help with tracing the kcontrol problem (and it doesn't involve reinstalling the entire OS), I'm willing to try. ** Affects: meta-kde (Ubuntu) Importance: Undecided Status: Unconfirmed -- kde settings mess-up https://launchpad.net/bugs/80444 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80444] Re: kde settings mess-up
This is a screenshot showing both issues: (1) kcontrol has nothing in it (the screenshot is taken in a KDE session, btw). (2) Note how hinting is not correctly used -- for example the menu of kcontrol. Notice how the i and l letters (lowercase L) are thickened (try zooming a lot) and look dirty or blurry. Compare with the piece of the Gimp window visible in the background, where all vertical lines are very clean. ** Attachment added: "screenshot of the issues" http://librarian.launchpad.net/5781569/Screenshot.png -- kde settings mess-up https://launchpad.net/bugs/80444 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80444] Re: kde settings mess-up
I just noticed that the fonts have the same (or a very similar) problem in Open Office. I thought OO uses Java, but neither Azureus nor Eclipse have this problem. -- kde settings mess-up https://launchpad.net/bugs/80444 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78167] Re: azureus crashes on startup
OK, I'm having similar issues here, but I can't tell if it's exactly the same bug. Azureus (2.5.0.0 on Ubuntu Feisty) worked for a bit after the install, then (I suppose it was force-closed by a log-out) it stopped starting. The main window would appear for a bit and then it just died. At first I was using the gcj java, and the errors in the console looked like: $ azureus DEBUG::Thu Jan 18 16:11:30 GMT+01:00 2007::org.gudy.azureus2.core3.security.impl.SESecurityManagerImpl::initialise::-1: No SSL provider available SESecurityManager::initialise::-1,ConfigurationChecker::setSystemProperties::-1,ConfigurationManager::initialise::-1,ConfigurationManager::getInstance::-1,LoggerImpl::init::-1,Logger-1,Class::initializeClass::-1,Logger::isEnabled::-1,StartServer-1,Main-1,Main::main::-1 DEBUG::Thu Jan 18 16:11:30 GMT+01:00 2007::org.gudy.azureus2.core3.security.impl.SESecurityManagerImpl::initialise::-1: No SSL provider available SESecurityManager::initialise::-1,CryptoManagerImpl-1,CryptoManagerImpl::getSingleton::-1,CryptoManagerFactory::getSingleton::-1,AzureusCoreImpl-1,AzureusCoreImpl::create::-1,AzureusCoreFactory::create::-1,Main-1,Main::main::-1 DEBUG::Thu Jan 18 16:11:32 GMT+01:00 2007::org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl::writeStats::-1: java.io.FileNotFoundException: /Azureus_Stats.xml (Permission denied) at gnu.java.nio.channels.FileChannelImpl.open(libgcj.so.70) at gnu.java.nio.channels.FileChannelImpl.(libgcj.so.70) at gnu.java.nio.channels.FileChannelImpl.create(libgcj.so.70) at java.io.FileOutputStream.(libgcj.so.70) at java.io.FileOutputStream.(libgcj.so.70) at java.io.FileOutputStream.(libgcj.so.70) at org.gudy.azureus2.core3.stats.impl.StatsWriterImpl.write(Azureus2.jar.so) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.writeStats(Azureus2.jar.so) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.update(Azureus2.jar.so) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl$1.runSupport(Azureus2.jar.so) at org.gudy.azureus2.core3.util.AEThread.run(Azureus2.jar.so) Aborted (core dumped) Then I did a "$ sudo update-java-alternatives -s java-6-sun" and I got: $ azureus DEBUG::Thu Jan 18 16:15:38 CET 2007::org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl::writeStats::206: java.io.FileNotFoundException: /Azureus_Stats.xml (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:70) at org.gudy.azureus2.core3.stats.impl.StatsWriterImpl.write(StatsWriterImpl.java:63) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.writeStats(StatsWriterPeriodicImpl.java:203) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.update(StatsWriterPeriodicImpl.java:102) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl$1.runSupport(StatsWriterPeriodicImpl.java:235) at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69) # # An unexpected error has been detected by Java Runtime Environment: # # Internal Error (53484152454432554E54494D450E435050020F), pid=14667, tid=3085020048 # # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing) # An error report file with more information is saved as hs_err_pid14667.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Aborted (core dumped) ** Then I looked for work-arounds and one of the similar bugs reported suggested to delete "~/.azureus/logs/*", which I did, and now it starts. The funny thing is that one of the exceptions is still showing: ** ~$ azureus DEBUG::Thu Jan 18 16:17:21 CET 2007::org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl::writeStats::206: java.io.FileNotFoundException: /Azureus_Stats.xml (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:70) at org.gudy.azureus2.core3.stats.impl.StatsWriterImpl.write(StatsWriterImpl.java:63) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.writeStats(StatsWriterPeriodicImpl.java:203) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl.update(StatsWriterPeriodicImpl.java:102) at org.gudy.azureus2.core3.stats.impl.StatsWriterPeriodicImpl$1.runSupport(StatsWriterPeriodicImpl.java:235) at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69) [but the program works here] This is really annoying, can't anyone figure out what's wrong? By the way,
[Bug 78167] Re: azureus crashes on startup
OK, that java.io.FileNotFoundException: /Azureus_Stats.xml (Permission denied) error is probably a silly bug somewhere, setting a wrong path as default. I created the file and chown-ed it to me, and now the error is no longer displayed. However, it still won't start. I'm really reluctant to delete the home directory. I always spend half a day configuring Azureus to my liking, and it crashes after less time than that sometimes. -- azureus crashes on startup https://launchpad.net/bugs/78167 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
