[Bug 1687910] Re: [Lenovo W520] Linux Freezing Issue At Boot
One year later, bug still valid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687910 Title: [Lenovo W520] Linux Freezing Issue At Boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687910] Re: [Lenovo W520] Linux Freezing Issue At Boot
Yes, with several 4.x kernels and even with kernel 5.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687910 Title: [Lenovo W520] Linux Freezing Issue At Boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796057] Re: Laoptop-lid-close-suspend setting in mate-power-preferences no longer effective
Sorry, my name is not Linus :-) I still believe in the ability of future mankind (O.-M.-G.! There is MAN in that! Must be wrong.) to deal with views and arguments they don't share in other ways than trying to ban them. Maybe they even learn again to have a laugh at them !!1! (well, I am an optimist). I have enjoyed writing my report the way it is, otherwise there may not be a report at all. If you didn't find anything humorous in it you are probably a GNOME- and/or systemd developer. :-P I apologize for the digress. Cheer up :-) ** Description changed: - Problem: In Ubuntu Mate 18.04, dconf and the mate-power-preferences offer a setting switch to determine what happens when the laptop lid is closed. If you change this from "suspend" to "do nothing", the setting remains without effect. Reason: The allmighty pizza-baking and clothes-washing systemd has drive-by- devoured this functionality and incorporated it into logind which happyly ignores the users GUI-set wish to keep his device running. To - avoid that, a manual change to the text configuration - /etc/systemd/logind.conf seems to be inevitably required at the moment. + avoid that, root permissions, a manual change to the text configuration + /etc/systemd/logind.conf and a logind restart seem to be inevitably + required at the moment. possible Solutions coming to mind: 1) stop using systemd (probably an unrealistic approach due to religious reasons) 2) remove the setting from the GUI so users are no longer confused by it making them believe it would actually have any effect. After all, taking away existing functionality because it might confuse users is a classical GNOME move. 3) But since this aint GNOME but Mate (which, I hope, strives to revert what GNOME destroyed to a certain extent) you might even try to make mate-power-manager reconfigure logind in some way. Free of any systemd knowledge, I can only presume that systemd has probably invented its own, new and incompatible-to-everything-existing messaging bus to make this happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796057 Title: Laoptop-lid-close-suspend setting in mate-power-preferences no longer effective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-power-manager/+bug/1796057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796057] [NEW] Laoptop-lid-close-suspend setting in mate-power-preferences no longer effective
Public bug reported: Problem: In Ubuntu Mate 18.04, dconf and the mate-power-preferences offer a setting switch to determine what happens when the laptop lid is closed. If you change this from "suspend" to "do nothing", the setting remains without effect. Reason: The allmighty pizza-baking and clothes-washing systemd has drive-by- devoured this functionality and incorporated it into logind which happyly ignores the users GUI-set wish to keep his device running. To avoid that, a manual change to the text configuration /etc/systemd/logind.conf seems to be inevitably required at the moment. possible Solutions coming to mind: 1) stop using systemd (probably an unrealistic approach due to religious reasons) 2) remove the setting from the GUI so users are no longer confused by it making them believe it would actually have any effect. After all, taking away existing functionality because it might confuse users is a classical GNOME move. 3) But since this aint GNOME but Mate (which, I hope, strives to revert what GNOME destroyed to a certain extent) you might even try to make mate-power-manager reconfigure logind in some way. Free of any systemd knowledge, I can only presume that systemd has probably invented its own, new and incompatible-to-everything-existing messaging bus to make this happen. ** Affects: mate-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: gui mate-power-manager preferences suspend-resume systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796057 Title: Laoptop-lid-close-suspend setting in mate-power-preferences no longer effective To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-power-manager/+bug/1796057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728855] [NEW] gkrellm network settings code can lead to reproducable instant X server crashes
Public bug reported: A user that uses gkrellm alonside virtualbox for some months will experience problems that may crash X instantly and reproducably. Steps to reproduce: * Use gkrellm with network monitors * Use virtualbox for some time. It will create virtual network devices with names that constantly change. Apparently gkrellm tracks all of them in its config file and never forgets any of them. After some time you will have a gkrellm user-config filled with hundrets of lines like this: net enables veth52730d0 1 1 0 net enables veth56844d4 1 1 0 net enables veth59140bf 1 1 0 net chart_config veth59140bf 40 300 0 1 0 0 : 0 0 0 0 500 : 0 0 0 0 500 net enables vethfc4e0e4 1 1 0 net chart_config vethfc4e0e4 40 5 0 1 0 0 : 0 0 0 0 500 : 0 0 0 0 500 net enables vethf11a8dd 1 1 0 net enables vethf94ed79 1 1 0 net enables vethf620cbd 1 1 0 net enables vethfeca6a1 1 1 0 net enables veth59748a4 1 1 0 net chart_config veth59748a4 40 300 0 1 0 0 : 0 0 0 0 500 : 0 0 0 0 500 net enables veth2214351 1 1 0 * now try to open the network monitor config panel in gkrellm. Your X will crash instantly. ** Affects: gkrellm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728855 Title: gkrellm network settings code can lead to reproducable instant X server crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gkrellm/+bug/1728855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1490293] [NEW] STARTTLS Handshake problem introduced in 1:31.8.0+build1
Public bug reported: I am running trusty. After the update from 1:31.7.0+build1 to 1:31.8.0+build1 i suddenly was no longer able to send mail via my provider. The mail server is running exim and uses STARTTLS for connection encryption. When hitting the send button, Thunderbird informed me that it is connecting to the mail server, immediately followed by a popup informing me that sending failed due to an "unknown error" and that I should talk to my network admin. I then made sure they had not changed anything in the exim server config (for quite some time actually). When I tried to send mail, the server would just have an entry in its log like this: 2015-08-30 15:35:04 TLS error on connection from (my.host.some.where) [176.198.xxx.yyy] (gnutls_handshake): A TLS packet with unexpected length was received. Sending mail from Android or with Evolution still works. I then grabbed a backup and downgraded thunderbird to the previous version 1:31.7.0+build1. The problem went away immediately. A simple test using #> openssl s_client -connect mail.my.provider.com:25 -starttls smtp does not exhibit anything uncommon, the handshake goes through without a hickup. Since thunderbird is not totally uncommon (although noone else seems to have complained yet), I could arrange a test login for anyone willing to run an investigation on the issue. I just don't want to publish server names or IPs here. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Description changed: + I am running trusty. After the update from 1:31.7.0+build1 to 1:31.8.0+build1 i suddenly was no longer able to send mail via my provider. + The mail server is running exim and uses STARTTLS for connection encryption. When hitting the send button, Thunderbird informed me that it is connecting to the mail server, immediately followed by a popup informing me that sending failed due to an "unknown error" and that I should talk to my network admin. - I am running trusty. After the update from 1:31.7.0+build1 to 1:31.8.0+build1 i suddenly was no longer able to send mail via my provider. - The mail server is running exim and uses STARTTLS for connection encryption. When hitting the send button, Thunderbird informed me that it is connecting to the mail server, immediately followed that sending failed due to an "unknown error" and that I should talk to my network admin. - - I then made sure they had not changed anything in the exim config (for - quite some time). Also, doing a STARTTLS handshake with When I tried to - send mail, the server would just have an entry in its log like this: + I then made sure they had not changed anything in the exim server config + (for quite some time actually). When I tried to send mail, the server + would just have an entry in its log like this: 2015-08-30 15:35:04 TLS error on connection from (my.host.some.where) [176.198.xxx.yyy] (gnutls_handshake): A TLS packet with unexpected length was received. + + Sending mail from Android or with Evolution still works. I then grabbed a backup and downgraded thunderbird to the previous version 1:31.7.0+build1. The problem went away immediately. A simple test using #> openssl s_client -connect mail.my.provider.com:25 -starttls smtp does not exhibit anything uncommon, the handshake goes through without a hickup. Since thunderbird is not totally uncommon (although noone else seems to have complained yet), I could arrange a test login for anyone willing to run an investigation on the issue. I just don't want to publish server names or IPs here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490293 Title: STARTTLS Handshake problem introduced in 1:31.8.0+build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1490293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 976032] Re: Place plugin problem with panel in fullscreen and gnome classic
I'd like to mention that I just had exactly this problem with ubuntu-
mate 14.04 ("trusty") compiz version
1:0.9.11.3+14.04.20150313-0ubuntu1.1
Disabling the place plugin "healed" the problem instantly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/976032
Title:
Place plugin problem with panel in fullscreen and gnome classic
To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/976032/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1112336] Re: [hardy->lucid] unresolvable problem occurred while calculating the upgrade
I found the cause of this problem: A held package was blocking python from being upgraded properly. The error messages of the upgrader were not very helpful in finding out the real reason, though. It might be a good idea to have the updater issue a general, prominent warning when it encounters held packages on the system BEFORE caclulating the upgrade - or at least if calculating an upgrade fails. ** Summary changed: - [hardy->lucid] unresolvable problem occurred while calculating the upgrade + held packages can cause "unresolvable problem" error on upgrade. no comprehensive hint given. ** Summary changed: - held packages can cause "unresolvable problem" error on upgrade. no comprehensive hint given. + held packages may cause "unresolvable problem" error on upgrade. no comprehensive hint given. ** Attachment removed: "Required log files (see bug text)" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1112336/+attachment/3510077/+files/var-log-dist-upgrade.tbz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1112336 Title: held packages may cause "unresolvable problem" error on upgrade. no comprehensive hint given. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1112336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1112336] [NEW] [hardy->lucid] unresolvable problem occurred while calculating the upgrade
Public bug reported: Since hardy is nearing the end of its support cycle I initiated an upgrade to lucid. Unfortunately it failed miserably. What I tried so far: * disabling (the single one) ppa we had (git) and uninstall their git packages * looking for broken packages (none found) * making sure everything is the latest version * starting do-release-upgrade in server and desktop mode (wont help) Now I am out of ideas. Uninstalling update-manager-core looks like being a really bad move for an update so I didnt try that one. --- root@server:~# do-release-upgrade -m server Checking for a new ubuntu release Done Upgrade tool signature Done Upgrade tool Done downloading authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg' extracting 'lucid.tar.gz' tar: Removing leading `/' from member names Reading cache Checking package manager Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Done downloading Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done No candidate ver: libpci2 No candidate ver: libntfs-3g16 No candidate ver: libldap2 No candidate ver: libopencdk8 No candidate ver: libsnmp10 No candidate ver: vmware-server No candidate ver: libdirectfb-0.9-25 No candidate ver: libntfs-3g12 No candidate ver: libcrypto++6 Updating repository information WARNING: Failed to read mirror file Done downloading Checking package manager Reading package lists: Donelucid-security/multiverse Packages: 98 9 Reading state information: Done Reading state information: Done Reading state information: Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade: The package 'update-manager-core' is marked for removal but it is in the removal blacklist. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report. Restoring original system state Aborting Reading package lists: Done hardy-security/multiverse Packages: 98 9 Reading state information: Done ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade distribution do-release-upgrade hardy lts lucid ** Attachment added: "Required log files (see bug text)" https://bugs.launchpad.net/bugs/1112336/+attachment/3510077/+files/var-log-dist-upgrade.tbz ** Tags removed: upgrade ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1112336 Title: [hardy->lucid] unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1112336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936928] Re: This package is so totally debian (v1.10 = 2009!) Please package an update (current = 4.03!)
Excuse my question, but... what is the supposedly correct way to indicate a package is totally outdated and should be either removed or updated? Is any report like this invalid (so I can spare me the effort in the future), as long as the respective package version in debian is ancient, too? Just asking to make sure that neither me nor you will have unnecessary workload in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936928 Title: This package is so totally debian (v1.10 = 2009!) Please package an update (current = 4.03!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zpaq/+bug/936928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936928] [NEW] This package is so totally debian (v1.10 = 2009!) Please package an update (current = 4.03!)
Public bug reported: It is 2012 and you are still shipping 2009 code here. There was a time when people chose ubuntu because of the up to date software packages. If you need help with a new source package let me know. ** Affects: zpaq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936928 Title: This package is so totally debian (v1.10 = 2009!) Please package an update (current = 4.03!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zpaq/+bug/936928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918200] [NEW] local calendars inaccessible after upgrade from natty (workaround included)
Public bug reported: Upgrading Evolution from 2.3x (natty) to 3.2 (oneiric), seemingly came with a lot of changes of internal data storage formats. Unfortunately the conversion process leaves room for improvement. After the upgrade, calendar kept crashing on me often and randomly. Also, I could not accept new meeting requests. Instead, evolution showed the following error message: Could not load calendar >XYZ< (No backend factory for 'file' of 'VEVENT') Also, the mentioned calendar can neither be opened nor deleted. According to this source: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=716448 It helps to edit some rather complicated xml values in gconf-editor which apparenty became flawed during the upgrade. In my case, fixing the base_uri helped somewhat; the above mentioned error message was replaced by a different one, for which I'll probably open another bug after some closer examination. Anyway, it may be worth checking whether this is the only case of a malformed base_uri and if the upgrade process could be changed to double-check for them. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918200 Title: local calendars inaccessible after upgrade from natty (workaround included) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/918200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 489830] Re: Settings of gpointing-device-settings are non-persistent
Am Samstag, den 07.01.2012, 01:13 + schrieb Tom Gelinas: > Hiroyuki Ikezoe is probably busy, if you're this impassioned you > should go upstream to gnome git. This isn't a binary module, fix it > yourself, pay someone or politely ask a capable person to help. Don't > whine in an echo chamber. Telling people who report bugs to "go fix it yourself" instead of honouring their effort by at least taking them seriously is the most efficient way to drive them away from reporting anything at all. If that is what you want, go ahead and continue doing so. kind regards, Fionn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/489830 Title: Settings of gpointing-device-settings are non-persistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpointing-device-settings/+bug/489830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 489830] Re: Settings of gpointing-device-settings are non-persistent
On Fri, 06.01.2012, 07:46 + Tom Gelinas wrote : > > I can confirm the issue on a ThinkPad W510 with Ubuntu 11.10. Please > – > > this is annoying as hell and renders the gpointing-device-settings > > completely useless. > > > Under Ubuntu 11.10, I don't think gpointing-device-settings is > necessary for simple TrackPoint style middle-click+downward-motion > scrolling. It works fine on my end by default. So, you basically write here "not using the faulty software doesn't cause problems on my end". That, of course, will always be true and is - sorry to have to say this - an utterly useless statement. You need GDS if you're NOT satisfied with the xorg defaults. If you happen to have an application that makes you need to change Wheel Emulation to Button3 instead of Button2 then you either need extensive xorg knowledge and a text editor or gpointing-device-settings to make the change happen. After having changed the setting with gpointing-device-settings this setting will be reset to the Button2 default on every suspend or reboot. So the choice is to either fix gpointing-device-settings to be a tool that actually works up to its promises or remove it from ubuntu entirely, because, as it is, it wont work fine on ANY end. Since removing usability from gnome/ubuntu seems to be the way to go these days, I suspect the latter will happen. kind regards, Fionn -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/489830 Title: Settings of gpointing-device-settings are non-persistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpointing-device-settings/+bug/489830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363241] Re: Automatic connect not engaging for openvpn
This bug is valid for all releases at least up to maverick! Moreover, when working in an insecure enviroment it may be pretty dangerous to use NM with openvpn since NM immediately flags any unencrypted connection as valid without starting openVPN as desired. This may result in applications like evolution and firefox beginning to run unencrypted data transfers immediately which not only is a security risk but also slows down or even completely inhibits the user from being able to establish the VPN manually (see also: bug #420411 ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/363241 Title: Automatic connect not engaging for openvpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/363241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 420411] Re: vpn connection handshake times out too soon
Being able to set the timeout is becoming increasingly important as more and more people start using nettops / mobile internet solutions which may run on GPRS or EDGE speed at any given time. On my laptop, using NM to esablish an openVPN connection is almost only possible with an UMTS quality link. Anything slower migth or might not work, depending on your luck and other automated tasks that start as soon as NM flags a valid network connection (Dont try to do vpn while evolution is already syncing your mail via the unencrypted line, automatically...) Using a GRPS link, openvpn via network-manager is currently completely impossible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/420411 Title: vpn connection handshake times out too soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/420411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 702550] Re: X forgets xinput settings on suspend
Although this bug is most certainly not a duplicate of bug #554984, it might (or might not) be related to bug #489830 which seems to have useful hints in the comments. Whether or not this actually is the same issue should be properly investigated before flagging this as dupe again, IMHO. HTH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702550 Title: X forgets xinput settings on suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/702550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 702550] Re: X forgets xinput settings on suspend
I'd like to strongly emphasize my opinion that this is certainly NOT a duplicate of #554984. Bug #554984 is about enabling tracpoint scrolling generally. THIS bug, however, is about X forgetting certain settings, namely the trackpoint wheel emulation, which have been enabled via xinput, during an S3 (suspend to ram) cycle. Since X is not being restarted in the course of this event, it should also not change or forget its settings. Putting the required statements into .xsessionrc as recommended in #554984 as a workaround does not apply for this bug, too, since that file is only evaluated at X startup and not at resume from s3. ** This bug is no longer a duplicate of bug 554984 [lucid] enable trackpoint scroll emulation by default -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702550 Title: X forgets xinput settings on suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/702550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 757314] [NEW] "copy link location" in gtkhtml does no longer copy URLs to X copybuffer
Public bug reported: Binary package hint: gnome-desktop-sharp2 Recently some update changed the behaviour of gnome widgets, namely the gtkhtml widget, when it comes to copying links embedded in the displayed text. Formerly you could select "copy link location" and the link was copied both to the clipboard and to the X copybuffer. Recently, the link is copied only to the clipboard and the X copybuffer is left unmodified. IMHO this behaviour is severely irritating as I (and probably a lot of other users) routinely use MMB link pasting in Firefox and since this change you always get unwanted results from that. The new policy forces the user to click into the URL widget, mark all and then insert the URL via Ctrl-V, which is several times more effort than just MMB-clicking somewhere into the Firefox window. All I want to know is whether this change in behaviour was an unintentional glitch and can be fixed or was it part of some "make gnome more painful to use"-strategy and must be swallowed as is? ** Affects: gnome-desktop-sharp2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/757314 Title: "copy link location" in gtkhtml does no longer copy URLs to X copybuffer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 671802] [NEW] munmap_chunk: invalid pointer
Public bug reported: Problem arose when trying to access a DDV chip card in a CM4000 reader via aqhbci / gwenhyfar. This is not reliably reproducable. Sometimes the chip card works as expected. I usually issue a command line "chipcard-tool atr" before I try to use the card productively because this seems to increase chances of everything working as expected. Ubuntu Version 10.04 with all updates as of 2010-11-06 libchipcard-tools 4.2.8-1ubuntu1 r...@rtfm[~] /etc/init.d/libchipcard-tools start Starting libchipcard daemon: 3:2010/11/06 11-42-50:(null)(7022):chipcardd.c: 1236: Closing GWEN chipcardd4. r...@rtfm[~] *** glibc detected *** /usr/lib/chipcard/server/drivers/ifd: munmap_chunk(): invalid pointer: 0x096ec6e8 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6(+0x6b591)[0x17b591] /lib/tls/i686/cmov/libc.so.6(+0x6c80e)[0x17c80e] /usr/lib/libgwenhywfar.so.47(GWEN_Memory_dealloc+0x27)[0xa8ebc7] /usr/lib/libgwenhywfar.so.47(GWEN_Buffer_free+0x52)[0xa83a02] /usr/lib/chipcard/server/drivers/ifd(LCD_Slot_SetAtr+0x33)[0x805b2a3] /usr/lib/chipcard/server/drivers/ifd(DriverIFD_DisconnectSlot+0x83)[0x804ed83] /usr/lib/chipcard/server/drivers/ifd(LCD_Driver_DisconnectSlot+0x2f)[0x8051b5f] /usr/lib/chipcard/server/drivers/ifd(DriverIFD_DisconnectReader+0xec)[0x804d71c] /usr/lib/chipcard/server/drivers/ifd(LCD_Driver_DisconnectReader+0x37)[0x8052397] /usr/lib/chipcard/server/drivers/ifd[0x8058ba2] /usr/lib/chipcard/server/drivers/ifd(LCD_Driver_Work+0x1ac)[0x805975c] /usr/lib/chipcard/server/drivers/ifd(main+0xb0)[0x8051380] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x126bd6] /usr/lib/chipcard/server/drivers/ifd[0x804ca41] === Memory map: 0011-00263000 r-xp fc:02 33668448 /lib/tls/i686/cmov/libc-2.11.1.so 00263000-00264000 ---p 00153000 fc:02 33668448 /lib/tls/i686/cmov/libc-2.11.1.so 00264000-00266000 r--p 00153000 fc:02 33668448 /lib/tls/i686/cmov/libc-2.11.1.so 00266000-00267000 rw-p 00155000 fc:02 33668448 /lib/tls/i686/cmov/libc-2.11.1.so 00267000-0026a000 rw-p 00:00 0 0026a000-0030 r-xp fc:02 17424240 /usr/lib/libgnutls.so.26.14.12 0030-00304000 r--p 00095000 fc:02 17424240 /usr/lib/libgnutls.so.26.14.12 00304000-00305000 rw-p 00099000 fc:02 17424240 /usr/lib/libgnutls.so.26.14.12 00305000-00307000 r-xp fc:02 33795796 /lib/tls/i686/cmov/libdl-2.11.1.so 00307000-00308000 r--p 1000 fc:02 33795796 /lib/tls/i686/cmov/libdl-2.11.1.so 00308000-00309000 rw-p 2000 fc:02 33795796 /lib/tls/i686/cmov/libdl-2.11.1.so 00309000-00318000 r-xp fc:02 17423733 /usr/lib/libtasn1.so.3.1.7 00318000-00319000 r--p e000 fc:02 17423733 /usr/lib/libtasn1.so.3.1.7 00319000-0031a000 rw-p f000 fc:02 17423733 /usr/lib/libtasn1.so.3.1.7 0031a000-0031e000 r-xp fc:02 50919155 /usr/local/lib/pcsc/drivers/libcm4000.so 0031e000-0031f000 rw-p 3000 fc:02 50919155 /usr/local/lib/pcsc/drivers/libcm4000.so 0049e000-004d5000 r-xp fc:02 16810159 /lib/libdbus-1.so.3.4.0 004d5000-004d6000 r--p 00036000 fc:02 16810159 /lib/libdbus-1.so.3.4.0 004d6000-004d7000 rw-p 00037000 fc:02 16810159 /lib/libdbus-1.so.3.4.0 005c-0063 r-xp fc:02 17394996 /lib/libgcrypt.so.11.5.2 0063-00631000 r--p 0007 fc:02 17394996 /lib/libgcrypt.so.11.5.2 00631000-00633000 rw-p 00071000 fc:02 17394996 /lib/libgcrypt.so.11.5.2 006e2000-006e9000 r-xp fc:02 33795824 /lib/tls/i686/cmov/librt-2.11.1.so 006e9000-006ea000 r--p 6000 fc:02 33795824 /lib/tls/i686/cmov/librt-2.11.1.so 006ea000-006eb000 rw-p 7000 fc:02 33795824 /lib/tls/i686/cmov/librt-2.11.1.so 00714000-00715000 r-xp 00:00 0 [vdso] 00779000-00789000 r-xp fc:02 16861694 /usr/lib/libhal.so.1.0.0 00789000-0078a000 r--p f000 fc:02 16861694 /usr/lib/libhal.so.1.0.0 0078a000-0078b000 rw-p 0001 fc:02 16861694 /usr/lib/libhal.so.1.0.0 008e6000-00903000 r-xp fc:02 17337709 /lib/libgcc_s.so.1 00903000-00904000 r--p 0001c000 fc:02 17337709 /lib/libgcc_s.so.1 00904000-00905000 rw-p 0001d000 fc:02 17337709 /lib/libgcc_s.so.1 00945000-0095a000 r-xp fc:02 33795818 /lib/tls/i686/cmov/libpthread-2.11.1.so 0095a000-0095b000 r--p 00014000 fc:02 33795818 /lib/tls/i686/cmov/libpthread-2.11.1.so 0095b000-0095c000 rw-p 00015000 fc:02 33795818 /lib/tls/i686/cmov/libpthread-2.11.1.so 0095c000-0095e000 rw-p 00:00 0 009e6000-00a01000 r-xp fc:02 17430490 /lib/ld-2.11.1.so 00a01000-00a02000 r--p 0001a000 fc:02 17430490 /lib/ld-2.11.1.so 00a02000-00a03000 rw-p 0001b000 fc:02 17430490 /lib/ld-2.11.1.so 00a57000-00b5 r-xp fc:02 16777685 /usr/lib/libgwenhywfar.so.47.11.3 00b5-00b51000 r--p 000f8000 fc:02 16777685 /usr/lib/libgwenhywfar.so.47.11.3 00b51000-00b52000 rw-p 000f9000 fc:02 16777685 /usr/lib/libgwenhywfar.so.47.11.3 00b94000-00b97000 r-xp fc:02 17364578
[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 We had the issue with two more servers today, one of them did not have a separate /var partition. The real reason for the immediate death of the boot process was /etc/default/locale which contained the line LC_ALL without further assignment. This led to the following boot message: [1.779805] kjournald starting. Commit interval 5 seconds [1.779828] EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. /etc/default/locale: 9: LC_ALL: not found init: mountall main process (311) terminated with status 127 With the default quiet / splash on you end up with a black screen and nothing happens. Pressing keys does not help. So this is probably a totally different problem than the one originally reported. (And I have no idea where to file this properly) -- kernel 2.6.32-32 makes machine hang during boot https://bugs.launchpad.net/bugs/576001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 Andreas, please note that I did not report a mount problem but (suspectedly) some sort of a race condition. Pressing 's' or 'm' did NOT help in our case either! - Presumably because ureadahead hung itself up when trying to write data before storage was available. -- kernel 2.6.32-32 makes machine hang during boot https://bugs.launchpad.net/bugs/576001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614662] Re: A better mountall
See also: bug #638228 -- A better mountall https://bugs.launchpad.net/bugs/614662 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571444] Re: Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected)
See also: bug #638228 -- Boot hangs and unable to continue when automount disk in fstab is not available (Off or Disconnected) https://bugs.launchpad.net/bugs/571444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 See also: bug #638228 -- kernel 2.6.32-32 makes machine hang during boot https://bugs.launchpad.net/bugs/576001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638228] [NEW] Give us back a rescue mode that deserves the name!
Public bug reported: Since Ubuntu 9.10 we have plymouth, ureadahead and upstart and whatnot, which are nice to have in many ways. Something being out of order is not one of them. Way too often, small configuration problems that were no problem in earlier versions do now cause the system to hang at boot time with no obvious reason being offered to the user. This would not be a major issue if the usual rescue option in grub would still deserve its name, which it does not. If, for example, a mount entry does not resolve properly you are totally out of luck as an admin with no direct console access because the so-called "rescue" system will get you exactly nowhere. (As a personal side note: The bug reporting that has been open for months and still is without being fixed which is an EPIC FAIL regarding the fact that Ubuntu apparently heads for the enterprise server market with tools like launchpad and stuff...) Bottom line is: What is needed BADLY in 9,04 and up is a dedicated rescue solution, maybe on its own initrd, that leaves out all the cuddly comfort crap and gets you to a shell, no matter what! Period. Thanks for reading. Click on "this bug affects me" if you agree. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - - Since Ubuntu 9.10 we have plymouth, ureadahead and upstart and whatnot, which are nice to have in many ways. + Since Ubuntu 9.10 we have plymouth, ureadahead and upstart and whatnot, + which are nice to have in many ways. Something being out of order is not one of them. Way too often, small configuration problems that were no problem in earlier versions do now cause the system to hang at boot time with no obvious reason being offered to the user. This would not be a major issue if the usual rescue option in grub would still deserve its name, which it does not. If, for example, a mount entry does not resolve properly you are totally out of luck as an admin with no direct console - access because the so-called "rescue" system with get you exactly + access because the so-called "rescue" system will get you exactly nowhere. (As a personal side note: The bug reporting that has been open for months and still is without being fixed which is an EPIC FAIL regarding the fact that Ubuntu apparently heads for the enterprise server market with tools like launchpad and stuff...) Bottom line is: What is needed BADLY in 9,04 and up is a dedicated rescue solution, maybe on its own initrd, that leaves out all the cuddly comfort crap and gets you to a shell, no matter what! Period. Thanks for reading. Click on "this bug affects me" if you agree. -- Give us back a rescue mode that deserves the name! https://bugs.launchpad.net/bugs/638228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638221] [NEW] does not work with a USB-ified iso Image
Public bug reported: Since several releases, Ubuntu supports installing from USB stick by providing a tool that puts the standard iso system images onto a USB stick and makes it bootable. If you boot this stick (text installer), trying to launch the rescue system does end up in an error message telling you that the cd rom drive is not available. ** Affects: rescue (Ubuntu) Importance: Undecided Status: New -- does not work with a USB-ified iso Image https://bugs.launchpad.net/bugs/638221 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 Oh, well, for the records: We encountered this problem with linux-image-2.6.32-24-server. It seems to have been fixed by moving /var up to the top in fstab. -- kernel 2.6.32-32 makes machine hang during boot https://bugs.launchpad.net/bugs/576001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 *** https://bugs.launchpad.net/bugs/571444 Do you happen to have /var on a separate partition? If yes, try moving the /var entry in fstab up to the top and let us know if it helps. I suspect this has to do something with like ureadahead in initialisation mode and /var not being available for ureadahead data storage or so. -- kernel 2.6.32-32 makes machine hang during boot https://bugs.launchpad.net/bugs/576001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571408] Re: libvirt-bin on latest lucid: heavy packet loss
I've got the problem back on the same server. This time I cant switch it off, whatever I do. However, this forced me to strip down the issue to the following fact: Switching on ip_forwarding starts the packet loss. Apparently it was only by accident that launching libvirt-bin switched it on. And I totally fail to see, how I could switch it off and on again to have it work. As it is now, forwarding on means packet loss, forwarding off does not. Even using a kernel that works flawlessly on a similar computer with a similar networking card in the very same computing center fails to solve the issue. The Hoster's netboot rescue system, however, does NOT expose the problem. I am totally lost on this and will problably have to reinstall the whole system. So, just to clarify, it seems not to be a libvirt-bin problem but some sort of general networking/hardware problem. -- libvirt-bin on latest lucid: heavy packet loss https://bugs.launchpad.net/bugs/571408 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590496] Re: after upgrade (9.04->10.04) LUKS partitions on USB volumes are no longer recognized/automounted
Is there anything I can add to this issue to bring it forward? -- after upgrade (9.04->10.04) LUKS partitions on USB volumes are no longer recognized/automounted https://bugs.launchpad.net/bugs/590496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546285] Re: Lucid does not detect HUAWEI 3G USB dongle.
In the mean time I found out that the stick is indeed properly configured as a modem. It attaches to ttyUSB0 and I can send commands and receive output quite nicely. Its just itching me pretty much that NM managed this stick so nicely on ubuntu jaunty and now it is not even listed by NM in lucid. I'd really appreciate hints on what to do to make NM recognize that there actually is a modem waiting for commands! ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- Lucid does not detect HUAWEI 3G USB dongle. https://bugs.launchpad.net/bugs/546285 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 473230] Re: Evolution always send e-mail through default smtp account
In a business context, this bug is hardly bearable because it can cause extremely embarassing situations to send read receipts with unwanted Sender addresses. I'd greatly appreciate if this bug could be escalated to at least "Normal" priority because it renders an important MUA feature almost unusable for business users with multiple identities. I just reported this upstream and then found out its already present here. Upstream Bug URL: https://bugzilla.gnome.org/show_bug.cgi?id=621585 ** Bug watch added: GNOME Bug Tracker #621585 https://bugzilla.gnome.org/show_bug.cgi?id=621585 ** Also affects: evolution (Debian) via https://bugzilla.gnome.org/show_bug.cgi?id=621585 Importance: Unknown Status: Unknown -- Evolution always send e-mail through default smtp account https://bugs.launchpad.net/bugs/473230 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 546285] Re: Lucid does not detect HUAWEI 3G USB dongle.
I'd like to add my personal experience here, maybe it helps. I googled and found that seems to be necessary to setup usb-modeswitch for the stick to work. However, When I plug in the stick now, syslog tells me that modeswitch claims to have switched the stick into modem mode, like: Jun 11 17:37:55 rtfm kernel: [89219.604681] usb 1-3: new high speed USB device using ehci_hcd and address 22 Jun 11 17:37:55 rtfm kernel: [89219.747603] usb 1-3: configuration #1 chosen from 1 choice Jun 11 17:37:58 rtfm usb-modeswitch: switching 12d1:1003 (HUAWEI Technology: HUAWEI Mobile) Jun 11 17:37:58 rtfm kernel: [89222.480839] usb 1-3: USB disconnect, address 22 Jun 11 17:37:59 rtfm kernel: [89223.729534] Initializing USB Mass Storage driver... Jun 11 17:37:59 rtfm kernel: [89223.729586] usbcore: registered new interface driver usb-storage Jun 11 17:37:59 rtfm kernel: [89223.729758] USB Mass Storage support registered. Jun 11 17:38:03 rtfm kernel: [89227.356076] usb 1-3: new high speed USB device using ehci_hcd and address 23 Jun 11 17:38:03 rtfm kernel: [89227.499669] usb 1-3: configuration #1 chosen from 1 choice Jun 11 17:38:03 rtfm kernel: [89227.522536] scsi45 : SCSI emulation for USB Mass Storage devices Jun 11 17:38:03 rtfm kernel: [89227.522872] usb-storage: device found at 23 However, as you can see, directly after reconfiguring the device is beind reconnected and re-detected as mass storage and pops up the inevitable drive icon instead of being listet by network-manager. If you need any more logs, please tell me so and I will glady provide any info you request. -- Lucid does not detect HUAWEI 3G USB dongle. https://bugs.launchpad.net/bugs/546285 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590496] [NEW] after upgrade (9.04->10.04) LUKS partitions on USB volumes are no longer recognized/automounted
Public bug reported: Binary package hint: hal Since the upgrade from jaunty to lucid I have to manually mount LUKS partitions from USB disks every time. They do not show up in the usual gnome places as crypt partitions and they there is no visible attempt (visible as in syslog) to unlock or mount them even though the key is in the chain and all this had been working before the upgrade. blkid seems to correctly identify the crypted partitions so it is not the "old cryptsetup vs blkid" bug. If you have any hints on how to debug this, I'll gladly provide more info. ** Affects: hal (Ubuntu) Importance: Undecided Status: New -- after upgrade (9.04->10.04) LUKS partitions on USB volumes are no longer recognized/automounted https://bugs.launchpad.net/bugs/590496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589643] [NEW] missing mount targets in fstab block startup completely
Public bug reported: Binary package hint: upstart I do systems administration a lot and as lucid came out, there were several occasions on which customers demanded an upgrade to lucid. On at least two of these the system completely failed to boot after the upgrade. In one case, recovery required a lot of time because the fs was actually on a cryptroot and not easy to access physically. In both cases the cause of the problem was an fstab entry, which referred to a disk that did not exist at boot time. While this was totally ok with older versions of ubuntu, it causes the startup to hang indefinitely on lucid, with somewhat uncorrelated (ureadahead termination) error messages on the console being the last thing to be seen by the user. Shell access is not available. Rescue boot option fails the very same way, too It is arguably not a good practice to have dangling mounts in the fstab, but this should NEVER EVER inhibit the system from booting without any means for recovery!! IMHO this is a very, very serious glitch, especially for remote and/or server upgrades. To the best of my knowledge system startup is now handled by upstart in lucid so from my POV this is an upstart problem. If you see better fit, go ahead and move this report somewhere else but make sure it gets fixed. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: fstab lockup mount serious upstart -- missing mount targets in fstab block startup completely https://bugs.launchpad.net/bugs/589643 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 571408] Re: libvirt-bin on latest lucid: heavy packet loss
Am Montag, den 03.05.2010, 14:09 + schrieb C de-Avillez: > Thank you for opening this bug and helping make Ubuntu better. This is > interesting... are there log entries for libvirt? In fact, any log > entries related to this packet loss? Actually not. I tried syslog, dmesg, then xtail on /var/log but no relevant entry seemed to appear. The packets just fell off the wagon. It looks like some in-kernel issue to me, especially regarding the "fix" I found. I just wonder why it did not happen earlier... -- libvirt-bin on latest lucid: heavy packet loss https://bugs.launchpad.net/bugs/571408 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545536] Re: not able to boot
I would like to add that this problem may occur if the system fails to mount a partition that is in fstab. Due to an apparent bug in upstart the mount problem handling does only kick in every n-th boot, and n may be >10 if you are out of luck. Otherwise only the above mentioned ureadahed error mesage is visible and the rest of the screen stays black which is a very unfortunate situation. -- Not able to boot https://bugs.launchpad.net/bugs/545536 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571408] [NEW] libvirt-bin on latest lucid: heavy packet loss
Public bug reported: I have to report a very strange bug here which I came upon today: I am running a quad core server with 4 KVM guests. Host and all guests are all lucid latest. Guests run in a bridged setup for outside communication as well as in the default KVM network for guest-to-guest communications. This setup is complete and worked already while I setup the guests, until yesterday the Host and all guests started to show heavy packet loss on their network interfaces. The host computer did not expose any packet loss if libvirt was not started on boot and when libvirt was started, packets began to fall into oblivion. Overall, the loss rate was about 75-95%. I first thought that one of the latest libvirt or kernels updates might be the the culprit but downgrading all libvirt and kvm packages as well as going back one kernel version did not change the situation. Then I began to experiment with iptables and network settings and after a couple of hours found out: When the packet loss occurs, doing sysctl -w net.ipv4.ip_forward=0 stops the packet loss problem immediately. But even more interestingly, setting ip_forward back to 1 does NOT cause the packet loss problem to reappear! The system does now run as expected again and I made a little checker script that will execute the two sysctls with some seconds in between, should packet loss be detected again. Nevertheless, I thought this might be worth reporting and maybe one of you developers wants to have additional information. Package information: linux-image-2.6.32-21-server2.6.32-21.32 qemu-kvm0.12.3+noroms-0ubuntu9 libvirt-bin 0.7.5-5ubuntu27 libvirt00.7.5-5ubuntu27 python-libvirt 0.7.5-5ubuntu27 ubuntu-virt-server 1.2 qemu-common 0.12.3+noroms-0ubuntu9 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- libvirt-bin on latest lucid: heavy packet loss https://bugs.launchpad.net/bugs/571408 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561560] Re: upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore.
Thanks; issue solved with your hint. However, the error message presented in this case is pretty misleading and should be improved. Therefor I'd like to propose changing this item to wishlist priority and leaving it valid until fixed. -- upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore. https://bugs.launchpad.net/bugs/561560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561560] Re: upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore.
** Attachment added: "update-manager log files" http://launchpadlibrarian.net/43927821/logs.tar.bz2 -- upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore. https://bugs.launchpad.net/bugs/561560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561560] [NEW] upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore.
Public bug reported: Binary package hint: update-manager r...@cardassian ~ # do-release-upgrade -d Checking for a new ubuntu release Done Upgrade tool signature Done Upgrade tool Done downloading extracting 'lucid.tar.gz' authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg' tar: Removing leading `/' from member names tar: /etc/apt/preferences: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors Reading cache Checking package manager Continue running under SSH? This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. If you continue, an additional ssh daemon will be started at port '9004'. Do you want to continue? Continue [yN] y Starting additional sshd To make recovery in case of failure easier, an additional sshd will be started on port '9004'. If anything goes wrong with the running ssh you can still connect to the additional one. Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Done downloading Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Updating repository information WARNING: Failed to read mirror file Third party sources disabled Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager. Done downloading Checking package manager Reading package lists: Donem lucid/partner Packages: 00 ackages: 00 Reading state information: Done Reading state information: Done Reading state information: Done Invalid package information After your package information was updated the essential package 'ubuntu-minimal' can not be found anymore. This indicates a serious error, please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report. Restoring original system state Aborting Reading package lists: Donem karmic/partner Packages: 99 ackages: 99 Reading state information: Done Reading state information: Done Reading state information: Done ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- upgrade 9.10->10.04 fails: 'ubuntu-minimal' can not be found anymore. https://bugs.launchpad.net/bugs/561560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534999] Re: Exception during pm.DoInstall()
** Attachment added: "/var/log/dist-upgrade/ log files" http://launchpadlibrarian.net/40580983/logs.tbz -- Exception during pm.DoInstall() https://bugs.launchpad.net/bugs/534999 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 534999] [NEW] Exception during pm.DoInstall()
Public bug reported: Binary package hint: update-manager r...@cardassian ~ # lsb_release -rd Description:Ubuntu 9.10 Release:9.10 r...@cardassian ~ # do-release-upgrade -d Checking for a new ubuntu release Done Upgrade tool signature Done Upgrade tool Done downloading extracting 'lucid.tar.gz' authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg' Reading cache Checking package manager Continue running under SSH? This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. If you continue, an additional ssh daemon will be started at port '9004'. Do you want to continue? Continue [yN] y Starting additional sshd To make recovery in case of failure easier, an additional sshd will be started on port '9004'. If anything goes wrong with the running ssh you can still connect to the additional one. Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Done downloading Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Updating repository information Third party sources disabled Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager. Done downloading Checking package manager Reading package lists: Donelucid-security/multiverse Packages: 99 Reading state information: Done Reading state information: Done Reading state information: Done Calculating the changes Support for some applications ended Canonical Ltd. no longer provides support for the following software packages. You can still get support from the community. Demoted: libcompress-bzip2-perl, libiw29, netcat-traditional Calculating the changes Starting Starting 2 Investigating libparted1.8-12 Package libparted1.8-12 has broken Conflicts on libparted0 Considering libparted0 as a solution to libparted1.8-12 4 Reinst Failed because of protected libparted0 Removing libparted1.8-12 rather than change libparted0 Investigating parted Package parted has broken Depends on libparted1.8-12 Considering libparted1.8-12 4 as a solution to parted 3 Re-Instated parted Done Do you want to start the upgrade? 3 packages are going to be removed. 65 new packages are going to be installed. 313 packages are going to be upgraded. You have to download a total of 168M. This download will take about 21 minutes with a 1Mbit DSL connection and about 6 hours with a 56k modem. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be cancelled. Continue [yN] Details [d]y Fetching Done downloading Upgrading Done downloading Exception during pm.DoInstall(): E:Couldn't configure pre-depend libplymouth2 for mountall, probably a dependency cycle. Could not install the upgrades The upgrade is now aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report. installArchives() failed Upgrade complete The upgrade is completed but there were errors during the upgrade process. r...@cardassian ~ # d update-manager ii update-manager-core 1:0.126.9 manage release upgrades ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- Exception during pm.DoInstall() https://bugs.launchpad.net/bugs/534999 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 314692] Re: Brainstorm SSL problem, site not accessible (FF3)
Am Montag, den 04.01.2010, 15:25 + schrieb Matthew Nuzum: > Fionn, a better question we might ask is, "Why are you using SSL?" > Normally that site should be accessed using HTTP. Did you find a link > or feature on that site that directs you to the SSL version which > causes you to get this error? I wanted to log in securely via https because I was on a corporate WLan and my user credentials are not meant to reside in my customer's proxy logs or whatever. However it seems they "fixed" the problem in the mean time by disabling SSL altogether. kind regards, Fionn -- Brainstorm SSL problem, site not accessible (FF3) https://bugs.launchpad.net/bugs/314692 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314692] Re: Brainstorm SSL problem, site not accessible (FF3)
Why dont you guys invest a few seconds and try to reproduce the problem before those "Are you still having this problem" requests? Is this a template? I get them at least on every second bug report I write (after 6-18 months of inactivity of course). Trying to access "https://brainstorm.ubuntu.com/"; currently results in a network timeout, probably due to unavailability of a server. so the correct answer would be: No, I am no longer getting this error. I get another one. Eagerly awaiting the next activity on this bug (within 12 monthes). -- Brainstorm SSL problem, site not accessible (FF3) https://bugs.launchpad.net/bugs/314692 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425347] Re: nntp: delisted newsgroups cant be unsubscribed
Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=605176 ** Bug watch added: GNOME Bug Tracker #605176 https://bugzilla.gnome.org/show_bug.cgi?id=605176 ** Changed in: evolution (Ubuntu) Status: Invalid => New -- nntp: delisted newsgroups cant be unsubscribed https://bugs.launchpad.net/bugs/425347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384833] Re: After locale change, default folders duplicate, crash when changing settings
The problem disappered with the latest Evolution version in Jaunty. The duplicate folder disappeared. There still is another problem as now the default "Persönlichl" Adress book is no longer duplicate and can be renamed. But after a restart of evolution the name flips back to the default name "Persönlich" (aka "Personal"). But I guess that is another bug to be reported elsewhere. -- After locale change, default folders duplicate, crash when changing settings https://bugs.launchpad.net/bugs/384833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391380] Re: When I connect to Jabber MUC Pidgin crashes.
After some web research I found the cause for the crash. Apparently it is a bug in a pidgin plugin named "X-Chat Chats" Version 2.2.0 and according to other reports that bug is dangling around since at least one year. It triggers when you try to join (aka create) a previously nonexistant chat. Workaround: start "pidgin -n" and disable the buggy plugin before going online. -- When I connect to Jabber MUC Pidgin crashes. https://bugs.launchpad.net/bugs/391380 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 391380] Re: When I connect to Jabber MUC Pidgin crashes.
I am experiencing exactly the same problem. Very annoying. ** Changed in: pidgin (Ubuntu) Status: New => Confirmed -- When I connect to Jabber MUC Pidgin crashes. https://bugs.launchpad.net/bugs/391380 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425347] [NEW] nntp: delisted newsgroups cant be unsubscribed
Public bug reported: Binary package hint: evolution The folder subscription dialogue does not list all subscribed folders. Instead it lists the folders that are listed as subscribable by the server. So if you subscribe to a newsgroup and this group is being delisted on the server then it will stay in your newsgroup list forever as a zombie because the subscription dialogue will not list it and therefor it is impossible uncheck its subscription status. This adds one up to the count of unfortunate UI bugs in the subscription dialogue. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: ath_hal Package: evolution 2.26.1-0ubuntu2 ProcEnviron: SHELL=/usr/bin/zsh PATH=(custom, user) LANG=de_DE.UTF-8 SourcePackage: evolution Uname: Linux 2.6.28-13-generic i686 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- nntp: delisted newsgroups cant be unsubscribed https://bugs.launchpad.net/bugs/425347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 425347] Re: nntp: delisted newsgroups cant be unsubscribed
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/31399214/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/31399215/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/31399216/ProcStatus.txt -- nntp: delisted newsgroups cant be unsubscribed https://bugs.launchpad.net/bugs/425347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375746] Re: [jaunty]: wish: consider backporting more recent version of calibre; current version is rather out of date
This bug is still valid because the update hasnt made it into the backports repository for months, despite the ppa availablility. Why is this so? ** Changed in: calibre (Ubuntu) Status: Invalid => Incomplete ** Changed in: calibre (Ubuntu) Status: Incomplete => New -- [jaunty]: wish: consider backporting more recent version of calibre; current version is rather out of date https://bugs.launchpad.net/bugs/375746 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281622] Re: segfault / error 4 in libc-2.8.90.so
I get the same error when I try to connect pidgin to the internal jabber server at work. This error turns up in the syslog and pidgin completely crashes with a segfault. For me this is a bit of a problem since I need to have acces to the jabber network at my company. -- Jul 24 10:04:12 rtfm kernel: [119073.212576] pidgin[14215]: segfault at 0 ip b76e2613 sp bf8c08d8 error 4 in libc-2.9.so[b766b000+15c000] -- This is a fresh jaunty install. Until last week I was on hardy and everything worked fine there. -- segfault / error 4 in libc-2.8.90.so https://bugs.launchpad.net/bugs/281622 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221144] Re: After upgrading to hardy, gnome-terminal windows are not properly restored on login
** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Confirmed -- After upgrading to hardy, gnome-terminal windows are not properly restored on login https://bugs.launchpad.net/bugs/221144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221144] Re: After upgrading to hardy, gnome-terminal windows are not properly restored on login
Just for the records: I just installed a clean, new shiny jaunty and gnome-terminal STILL does not properly restore!? I really wonder how all you coding guys survived the last YEARS!? Do you really re-open and re-arrange all your terminals each time you login? Thank god I saved my ancient gnome-terminal 2.18 packages from gutsy(!) and with a little tweaking they installed even on jaunty. Anyway, this means two years of broken session management - if you ever wondered why QT and KDE are about to win on the desktop, this sort of "maintenance" may be part of the answer. -- After upgrading to hardy, gnome-terminal windows are not properly restored on login https://bugs.launchpad.net/bugs/221144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384833] Re: After locale change, default folders duplicate, crash when changing settings
Version Question: I cant remember exactly, it was in 2007. I think they were at version 2 already when I switched. Profile hint: Is there a howto for this somewhere? I am keeping tens of thousands of mails and hundreds of contacts in evolution, not to mention an extensively used calendar. Not losing data is imperative for me. If there is an easy way of exporting and re-importing all this, I'll gladly give it a try (yes, I am doing backups almost daily). -- After locale change, default folders duplicate, crash when changing settings https://bugs.launchpad.net/bugs/384833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384833] Re: After locale change, default folders duplicate, crash when changing settings
** Attachment added: "Screenshot" http://launchpadlibrarian.net/27649437/gkrellShoot_06-08-09_172552.png -- After locale change, default folders duplicate, crash when changing settings https://bugs.launchpad.net/bugs/384833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 384833] [NEW] After locale change, default folders duplicate, crash when changing settings
Public bug reported: Binary package hint: evolution Affected: all Versions of Evolution I ever used (currently: 2.22.3.1) Distro: Ubuntu Hardy (with all updates up to Jun 08 2009) Description: I once used Evolution with default (English) locale. Later, I switched from Debian to Ubuntu and began using evolution with German locale. Some time after switching, I recognized that the default section folders in the sidebar had been duplicated. That means: In the Address book section I have a category "On this Computer" and "Auf diesem Computer" (the latter being the same as the first in English). Moreover I have "Personal", respectively "Persönlich" Address books in both of them which apparently are pointing to the same physical database. I attached a screenshot for visualization of the problem. In the Calendar and Task list this behaviour gets very irritating because all "Personal" appointments show up twice in the calendar until I switch one of the duplicate translations off manually. Moreover, I can no longer change settings like Calendar/Task entry colors for "Personal" section (They are pink, I hate pink :-]). In the screenshot you can nicely see, that one of the "Personal" localisations has green color icon attached, the other has none. the entries of the "Non-color" localisation appear in pink (see screenshot). Which one of the localizations is green appears to be randomly changing (probably a race condition at startup). If I try to change settings for the section folder that has no color icon, Evolution crashes. I'd really like to get rid of the "On this Computer" section permanently but since it is a default section it can not be removed. Even if it could I would be afraid to lose data because it points to the same data as the localized section folder. What can I do to get rid of those duplicate entries in my calendar and tasks? Maybe there is an XML file I can manipulate or anything else? ** Affects: evolution (Ubuntu) Importance: Low Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Incomplete ** Tags: gui locale usability -- After locale change, default folders duplicate, crash when changing settings https://bugs.launchpad.net/bugs/384833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366051] Re: huawei usb-modem (12d1:1003) not detected
Update: Using the rules file from https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/346835/comments/11 solved the problem for me. Thanks! -- huawei usb-modem (12d1:1003) not detected https://bugs.launchpad.net/bugs/366051 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366051] Re: huawei usb-modem (12d1:1003) not detected
I can confirm this bug. Since I urgently need a working UMTS stick, I'd be very glad if someone could please tell me what I can do now to work around this problem. (Dist-Upgrading hardy is not an option at the moment and the older packages apparently left ppa already so I cant go back). -- huawei usb-modem (12d1:1003) not detected https://bugs.launchpad.net/bugs/366051 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340151] Re: ICQ protocol update [March 2009]
Yes, please, I have been waiting for a week for the fix on hardy now, still no luck :-( So I'd like to say "me too" here!!1! ;-) And: "pleeze, send filez" -- ICQ protocol update [March 2009] https://bugs.launchpad.net/bugs/340151 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211252] Re: Cannot receive files using bluetooth
The underlying bug in bluez-utils is now known for almost a year. A fix is known for more than six months. Why the hell hasnt it been released yet? Does LOW (as in priority) mean "let others wait" ? -- Cannot receive files using bluetooth https://bugs.launchpad.net/bugs/211252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 323392] [NEW] Nautilus should queue multi-file ops properly for identical source and dest device
Public bug reported: Binary package hint: nautilus When copying or moving multiple files to and from slow sources/destinations, it should be possible to queue them properly instead of having them running in parallel. Especially with network drives the thoughput is heavily dropping with multiple parallel operations. Unfortuantely Nautilus can list them all nicely in that tray window but instead of building a proper queue it tries to run them all at the same time. I suggest the default behaviour for all types of network drives should be queueing instead of parallel I/O. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: suggestion -- Nautilus should queue multi-file ops properly for identical source and dest device https://bugs.launchpad.net/bugs/323392 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319538] Re: streamtuner in Hardy currently mostly useless, request backport from intrepid
** Attachment added: "Backport of Streamtuner for Hardy (Shoutcast issue fixed)" http://launchpadlibrarian.net/21501710/streamtuner_0.99.99-14ubuntu1_i386.deb -- streamtuner in Hardy currently mostly useless, request backport from intrepid https://bugs.launchpad.net/bugs/319538 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319538] [NEW] streamtuner in Hardy currently mostly useless, request backport from intrepid
Public bug reported: Binary package hint: streamtuner Streamtuner in Hardy is unable to parse the shoutcast station list because the page changed. This problem has been fixed already in intrepid for months now and is still present in Hardy. A backport is a matter of a minute, I tried with the intrepid source packages and it was no problem at all. Does "long term support" mean "support takes long time"? ;-) Backported package is attached for your convenience. Please take the minute and release a version that works for Hardy. Thank you. ** Affects: streamtuner (Ubuntu) Importance: Undecided Status: New -- streamtuner in Hardy currently mostly useless, request backport from intrepid https://bugs.launchpad.net/bugs/319538 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314692] [NEW] Brainstorm SSL problem, site not accessible (FF3)
Public bug reported: Trying to access "https://brainstorm.ubuntu.com/"; with firefox 3 (latest version from Hardy) I get a failure page with "Error code: ssl_error_rx_record_too_long". My best guess is that this might be due to an oversized intermediate certificate file on the server. I just wanted to let you know that I may not be the only one who is not able to access the site at all currently. ** Affects: ubuntu Importance: Undecided Status: New -- Brainstorm SSL problem, site not accessible (FF3) https://bugs.launchpad.net/bugs/314692 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 309607] Re: seahorse shows up in "Accessories" menu instead of System
Although I see this has been tagged invalid, I just feel an urge to add that I just was about to file the very same suggestion after having a HARD time finding out where on earth the keyring-editing functionality of "gnome-keyring-manager" had gone! (see also: https://answers.launchpad.net/ubuntu/+source/gnome-keyring- manager/+question/56533) -- seahorse shows up in "Accessories" menu instead of System https://bugs.launchpad.net/bugs/309607 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154833] Re: Epson DX4850 usb printer does not work after upgrading from 7.04 to 7.10
Sorry, looks like I overlooked the solution and posted too fast. The udev rules fixed this for me. -- Epson DX4850 usb printer does not work after upgrading from 7.04 to 7.10 https://bugs.launchpad.net/bugs/154833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154833] Re: Epson DX4850 usb printer does not work after upgrading from 7.04 to 7.10
I found to be hit by exactly the same problem! Why is this still "undecided"? The printer is basically no longer working and I would greatly appreciate at least a workaround. :-) -- Epson DX4850 usb printer does not work after upgrading from 7.04 to 7.10 https://bugs.launchpad.net/bugs/154833 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225357] [NEW] MAX_CACHE_SAMPLE_SIZE too small -> many startup sounds dont play
Public bug reported: Binary package hint: pulseaudio Many sound fonts for Gnome or KDE System sounds have rather largish startup tunes (>= 10 sec). These sounds played fine with esound but do not play with pulseaudio, apparently because some buffer is too small. In this case, the syslog reports a line like: pulseaudio[1234]: protocol-esound.c: pulsecore/protocol-esound.c: Sample too large (3178496 bytes). While this is not a serious issue, I strongly suggest to find a solution because static buffer boundaries are just not a thing to use in the 21st century and this sort of disturbs the user experience. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- MAX_CACHE_SAMPLE_SIZE too small -> many startup sounds dont play https://bugs.launchpad.net/bugs/225357 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221144] Re: After upgrading to hardy, gnome-terminal windows are not properly restored on login
Hi, I would just like to CONFIRM this bug. In addition I can add the experience that downgrading gnome-terminal to the latest gutsy version does indeed seem to FIX the issue. I guess this indicates it is not a WM problem. ALSO I experienced that the terminals changed size and position when the video mode changed so that not the entire desktop is visible on screen (e.g. 800x600 vidmode on 1600x1200 screen) This also messes up panel icon placements but thats another (but possibly related) bug. -- After upgrading to hardy, gnome-terminal windows are not properly restored on login https://bugs.launchpad.net/bugs/221144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191026] Re: Please sync taxbird (0.11-1) from Debian unstable (main) (was: Package unusable, new upstream version available)
a gutsy backport would be nice since most users are probably not yet on hardy -- Please sync taxbird (0.11-1) from Debian unstable (main) (was: Package unusable, new upstream version available) https://bugs.launchpad.net/bugs/191026 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 191026] Re: Please sync taxbird (0.11-1) from Debian unstable (main) (was: Package unusable, new upstream version available)
0.10 is for fiscal year 2007. 0.11 has support for 2008. I think 0.11 will not be (logically) outdated before end of 2008. -- Please sync taxbird (0.11-1) from Debian unstable (main) (was: Package unusable, new upstream version available) https://bugs.launchpad.net/bugs/191026 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 191026] [NEW] Package unusable, new upstream version available
Public bug reported: Binary package hint: taxbird This package is outdated and currently unusable because it only supports tax reports for 2007 while reports for 2008 are due already. A new upstream version is available. It is already present in DEBIAN. Please update this asap. ** Affects: taxbird (Ubuntu) Importance: Undecided Status: New -- Package unusable, new upstream version available https://bugs.launchpad.net/bugs/191026 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 182268] Re: pidgin occasionally overwrites "accounts.xml" file with NULL bytes
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/11307660/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/11307661/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/11307662/ProcStatus.txt -- pidgin occasionally overwrites "accounts.xml" file with NULL bytes https://bugs.launchpad.net/bugs/182268 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 182268] pidgin occasionally overwrites "accounts.xml" file with NULL bytes
Public bug reported: Binary package hint: pidgin I had it for the second time now within 2 Months, that pidgin was greeting me with "you have no IM accounts configured yet...". Looking into the configuration files, I found out that accounts.xml has been filled with NULL bytes while still having its original size. All other xml files are apparently not affected. Thank god I have backups but this bug stinks. ProblemType: Bug Architecture: i386 Date: Sat Jan 12 13:04:42 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/pidgin NonfreeKernelModules: fglrx ath_hal Package: pidgin 1:2.2.1-1ubuntu4.1 PackageArchitecture: i386 ProcCmdline: pidgin ProcCwd: /home/fionn ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games [EMAIL PROTECTED] SHELL=/bin/zsh SourcePackage: pidgin Uname: Linux rtfm 2.6.21.3 #1 PREEMPT Mon Jun 4 14:59:16 CEST 2007 i686 GNU/Linux ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- pidgin occasionally overwrites "accounts.xml" file with NULL bytes https://bugs.launchpad.net/bugs/182268 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 179190] Totally outdated binary; Unable to connect; Should be updated or removed ASAP
Public bug reported: Binary package hint: anon-proxy The mix binary in this package is so old, it can no longer connect to any running mix cascade. Therefor, this package is totally useless and nothing but a potential source of problems for users who are interested in anonymity. The JAP project is building their own up-to-date debian packages. I strongly recommend to remove this package from the repositories ASAP and adapt their package for ubuntu. Instructions about how to get a usable version can be found at this URL: http://anon.inf.tu-dresden.de/operators/help/mixsetupDebian_en.html Instructions on how to configure the mix as a local proxy can be found here: http://anon.inf.tu-dresden.de/operators/help/cmdjap_en.html ** Affects: anon-proxy (Ubuntu) Importance: Undecided Status: New -- Totally outdated binary; Unable to connect; Should be updated or removed ASAP https://bugs.launchpad.net/bugs/179190 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
Re: [Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
Turbo Fredriksson wrote:
> The patch at https://bugs.launchpad.net/ubuntu/+source/network-
> manager/+bug/64173/comments/12 actually didn't work for me. I still get
> all the disconnects.
I hope you have understood that the patch itself will not change
anything in network-manager, unless you use nm-tool to increase the
timeout values at runtime. So if you just patched your source and
nothing else, everything will be like before.
kind regards,
Fionn
--
Wireless network keeps reconnecting (ubuntu edgy)
https://bugs.launchpad.net/bugs/64173
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
Re: [Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
Alexander Sack wrote: > For the patch ... its much appreciated, but making a user-defined > variable out of this isn't the right way to go imo. In the end it > would only help expert users, which is not what we want. Well, changing a hardcoded value to some other hardcoded value isnt exactly elegant, too. The patch creates the possibility to e.g. have an "/etc/default/network-manager" file, store the timeout there and have it set in the dbus startup script for network-manager. That sure is a little more complicated but next time the timeout doesnt fit the setup of someone, it will be as easy as starting a text editor for them to have it fixed. More so if you would place a hint in the not yet existing man-page for network-manager (possibly along with some instructions on how to restart network-manager properly because it tends to get stuck on some dbus queue congestion issue after some quite large number of reconnects. I really should file a bug on that and the missing manpage). kind regards, Fionn -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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
Re: [Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
Lars M Bengtsson wrote: > > Although I am the guy who created this bug report, I'm beginning to feel > like I have to come to the defence of NetworkManager here :) > [...] > I have never seen networkmanager completely break an existing connection > with an access point and go through the whole interface setup procedure Well, I have experienced exactly this and it still happens regularly when I dont change timeouts. Interesting enough the problem seems to be gone sometimes (rarely) after a reboot for some time but then I suspend and change networks and when I come back the disconnects are there again. In the worst case NM actually interrupts and reconnects about once a minute which renders the connection basically unusable. >From what I read here, I am not quite the only one who had this problem. So, although I am glad for you that your problems have gone away, there are apparently still some for a significant number of users. > [...] NetworkManager can be somewhat > tricky to use at times, but when it has established a connection it is > rock solid from there on. Not true for everyone. > My apologies if the initial report was not clear enough I think there is no fault whatsoever on your side. Although the original intent of your report might have shifted somewhat due to the numerous additional comments, there still IS a problem here that isnt fixed. kind regards, Fionn -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
I'd like to second Kansei's motion - again. In my opinion, the need for WiFi networking that "just works" becomes increasingly important for any OS to gain momentum. Unexplainable network outages every few minutes or even seconds that can not be fixed with a few clicks are a lot more likely to scare away new or live CD users than, say, a year before. As I already pointed out in comment #8, changing ONE single number in the code apparently makes the problems go away for most people who tried. My patch has not been accepted by upstream for reasons that I can understand (its a patch, not a fix). On the other hand the question is: how long are you willing to wait for a "proper" solution, possibly losing new users every day along the way? From that perspective, changing at least the timeout as suggested for the upcoming release until a better solution has been found might be the most pragmatic approach. kind regards, Fionn -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: patch
Sorry, the patch certainly applies to FEISTY. Havent had the time to look at gutsy yet. kind regards, Fionn -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: bug fixed !?
Re: Chris: How could this bug possibly be fixed in madwifi, since users of Intel WiFi chipsets are also reporting the same problems? I have attached a working patch for the latest network-manager in edgy, 0.6.4-6ubuntu7. Details can be found above. kind regards, Fionn ** Attachment added: "patch which extents network-manager with functionality to set user-defined reconnection timeouts" http://launchpadlibrarian.net/8603452/reconnect-timeout.diff.gz -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
Regarding the package versions problem: You can always decide which version of a package you want to install. To do this in Synaptic you click on the package you want to install, then you choose "force version" from the menu "Package" (or press Ctrl+E) and choose what you want to have. On the command line you list your available options by typing: #> apt-cache policy network-manager Then you choose which version you want to install and do so by typing #> apt-get -f install network-manager=x.y.z-ubuntuN <--- preferred version as reported by above cmd for example #> apt-get -f install network-manager=0.6.4-6ubuntu3f As I already mentioned I dont have time to keep up with ubuntu release cycles. I'll release an update whenever the package will break for me (e.g. must be updated because it keeps other software from installing or running properly). -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
mowerm wrote: > $ sudo wpa_cli > > ap_scan 0 Well, on my system, this yields: Could not connect to wpa_supplicant - re-trying Then, nothing happens until I press Ctrl-C. So this doesnt seem to be a fix for people who use network-manager to drive wpa_supplicant. I'd also like to point out that THIS bug has initially been reported by an Intel Wifi user. It is NOT a specific atheros/madwifi issue! -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 37821] Re: Regular network drops with madwifi
This bug neither is necessarily caused by wpa_supplicant, nor by madwifi. For more info and a different approach to fixing visit Bug #64173 , please. -- Regular network drops with madwifi https://bugs.launchpad.net/bugs/37821 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 83627] Re: fuse-utils doesn't include mount.fuse
The issue is apparently still valid for all edgy users (unless they use the unofficial flomertens repo). An easy fix can be found on the following page: http://www.john-hunt.com/linux/2006/10/30/fixing-fuse-for-auto-mounting-in-your-fstab-via-sshfs/ This is just in case you dont want to upgrade to feisty just to be able to mount your stuff like debian people did for years... -- fuse-utils doesn't include mount.fuse https://bugs.launchpad.net/bugs/83627 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 107513] Plugin can not be deactivated (crash)
Public bug reported: In addition to bug #95451 the plugin can not be deactivated normally. If you try to deselect the plugin in the gkrellm plugin manager, gkrellm will crash instantly. When gkrellm is restarted, the plugin shows up as active again. I completely removed the plugin from my computer to get rid of it. So this is the second grave functionality bug in this package. This time it affects the whole gkrellm system. You might want to consider the complete removal of this package from the repositories until it acutally does something useful. ** Affects: gkremldk (Ubuntu) Importance: Undecided Status: Unconfirmed -- Plugin can not be deactivated (crash) https://bugs.launchpad.net/bugs/107513 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 93380] Re: First Start: clicking on "Add Account" -> Crash
The bug seems to be no longer present in the latest (feisty) packages -- First Start: clicking on "Add Account" -> Crash https://bugs.launchpad.net/bugs/93380 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 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
You dont need to sign anything to use any repository on the net. The signing key importing procedure is just optional, to avoid warning messages about unknown signing keys. Please do not post inquiries on this bug thread about topics which are not related to the original network manager bug. -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 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 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
I would suspect that the last post is probably closer related to mutual RF interference than to a software problem. -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
I did not take it as such. I was just voicing my slight disappointment about the fact my efforts to bring forth a fix that could easily be adopted by the developers were apparently futile. I will put up my fixed debs at http://fionn.de/software/debian/ tonight (which is about 6 hrs from the moment I posted this). You may want to subscribe there tomorrow and download the latest fixed package until the original works for you again. Dont expect me to keep up with unbuntu packaging cycles on a regular basis though. I tend to keep using a fix for as long as it works for me. -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
It appears like the upstream developers didnt feel like incorporating the patch into their code - despite the positive feedback. I do not have the time to adapt my patch to new upstream code every other day. So, if their code does not work for you because they dont include redily submitted fixes, please COMPLAIN TO THEM. I'll happily compile a new patch as soon as I know they will actually use it. -- Wireless network keeps reconnecting (ubuntu edgy) https://bugs.launchpad.net/bugs/64173 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 64173] Re: Wireless network keeps reconnecting (ubuntu edgy)
On Do, 2007-03-29 at 02:10 +, pterandon wrote: > Edgy 6.10 worked fine on my box. > > Feisty 7.04 beta does not connect to my WEP-encrypted network. > > Here's some useful data: I was able to connect to my neighbor's > unencrypted (and very weak) wifi signal intermittently as a test. My > guess is that Fawn isn't storing properly the WEP password. This report does not sound like it is related to this particular bug. More like some problem with wpa-supplicant or gnome-keyring. Keep in mind that network-manager itself does no key management by itself at all. It uses the mentioned external programs for that. Fionn -- Wireless network keeps reconnecting (ubuntu edgy) https://launchpad.net/bugs/64173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95451] Plugin fails to reconnect to server
Public bug reported: The plugin is nice - as long as you have a stable network connection to your mldonkey server. Nowhere in the plugin there seems to be a way to handle or at least force a renewal of the server link. Once the link goes down - e.g. because you take your notebook to work and back or you send your notebook to sleep for the night - the plugin keeps displaying the last valid values forever. Even setting a new server in the prefs does not recover the display - gkrellm has to be completely restarted to get the plugin to work again. This disability is a serious downer for everyone wanting to actually use the monitor for extended amounts of time. A software that relies on a network connection should be able to detect a connection failure and reinstate the link once it is broken. ** Affects: gkremldk (Ubuntu) Importance: Undecided Status: Unconfirmed -- Plugin fails to reconnect to server https://launchpad.net/bugs/95451 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93380] Re: First Start: clicking on "Add Account" -> Crash
telepathy-gabble 0.3.10-0ubuntu2 libtelepathy2 0.0.37-0ubuntu1 -- First Start: clicking on "Add Account" -> Crash https://launchpad.net/bugs/93380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93380] Re: First Start: clicking on "Add Account" -> Crash
For the books: I tried gossip-telepathy 0.23~svn20070222-0ubuntu1 on edgy. -- First Start: clicking on "Add Account" -> Crash https://launchpad.net/bugs/93380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93380] First Start: clicking on "Add Account" -> Crash
Public bug reported: Binary package hint: gossip-telepathy I wanted to try gossip-telepathy after I found the GUI of cohoba a bit awkward. Unfortunately the software is entirely unusable due to the fact that it crashes reproducibly the very moment I try to configure an account. Clicking the the "Add" Button in the Accounts windows yields a SIGSEV. Backtrace below. #>gossip Key file does not have key 'Name' Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1227221296 (LWP 30428)] 0x080c86f0 in gossip_telepathy_cmgr_list_protocols () (gdb) bt #0 0x080c86f0 in gossip_telepathy_cmgr_list_protocols () #1 0x080665ff in gossip_protocol_chooser_new () #2 0x08069f84 in gossip_accounts_dialog_show () #3 0xb78629d9 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #4 0xb785562b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #5 0xb7866103 in g_signal_override_class_closure () from /usr/lib/libgobject-2.0.so.0 #6 0xb7867627 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #7 0xb78677e9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #8 0xb7a54093 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 #9 0xb7a55cde in gtk_button_set_alignment () from /usr/lib/libgtk-x11-2.0.so.0 #10 0xb78629d9 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #11 0xb7853e49 in g_value_set_boxed () from /usr/lib/libgobject-2.0.so.0 #12 0xb785562b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #13 0xb786659a in g_signal_override_class_closure () from /usr/lib/libgobject-2.0.so.0 #14 0xb7867627 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #15 0xb78677e9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #16 0xb7a54123 in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0 #17 0xb7a54181 in gtk_button_released () from /usr/lib/libgtk-x11-2.0.so.0 #18 0xb7b23b00 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #19 0xb7853e49 in g_value_set_boxed () from /usr/lib/libgobject-2.0.so.0 #20 0xb785562b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #21 0xb7866753 in g_signal_override_class_closure () from /usr/lib/libgobject-2.0.so.0 #22 0xb78673ef in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #23 0xb78677e9 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #24 0xb7c375f8 in gtk_widget_get_default_style () from /usr/lib/libgtk-x11-2.0.so.0 #25 0xb7b1cef3 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #26 0xb7b1e0f7 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #27 0xb79a77ea in _gdk_events_init () from /usr/lib/libgdk-x11-2.0.so.0 #28 0xb77e3df2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0xb77e6dcf in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #30 0xb77e7179 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #31 0xb7b1e574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #32 0x080915f3 in main () ** Affects: gossip-telepathy (Ubuntu) Importance: Undecided Status: Unconfirmed -- First Start: clicking on "Add Account" -> Crash https://launchpad.net/bugs/93380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64173] Possible fix
As promised I am releasing a patch that seems to help at least on my system, as far as I could test yet. the patch is for the current feisty source. The patch also includes a little fix for Bug #91698 which makes backporting easier. If you remove the top 47 lines from the patch, the patch will also apply to the edgy source tree. Just apt-get source, apt-get build-dep, patch and dpkg-buildpackage. Dont blame me if things get stuck. As you can read in my earlier posts I originally intended to make the timeout configurable via gconf. I dropped this idea for now since network-manager itself is not capable of using gconf at all. It receives all its configuration via dbus command sequences. So I hacked "nm-tool" to include an option for setting the timeout. Feel free to add the functionality to the gnome applet - it can store the settings via gconf then. Once you have applied the patch you can set the reconnection timeout to e.g. 20 seconds when NM is running by issuing the following command: #> nm-tool --set-timeout 2 You can do this automatically in a script and even adjust the timeouts for different connection situations. Just drop the script in /etc/NetworkManager/dispatcher.d/ See also "man NetworkManagerDispatcher" for info Happy patching. And report back if it does not do you any good! ** Attachment added: "Patch that enables the user to dynamically set link failure reconnection timeouts" http://librarian.launchpad.net/6824480/reconnect-timeout.diff.gz -- Wireless network keeps reconnecting (ubuntu edgy) https://launchpad.net/bugs/64173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
