[Bug 1028299] Re: Key binding settings are lost and forgotten
Is there a workaround for this, yet? It is truly annoying to configure key bindings, just to find them gone whenever I reboot the laptop with 12.10 (kept up to date using quantal-updates) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028299 Title: Key binding settings are lost and forgotten To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1028299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 962085] Re: [0.9.7.2] gtk-window-decorator receives BadWindow errors
From the above. I'd have assumed this is 1. not in precise and 2. not after 0.9.7.4 I am running precise and compiz-core is ii compiz-core1:0.9.7.6-0ubuntu1 OpenGL window and compositing manager and this is what I find in xsession errors: The program 'gtk-window-decorator' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 575507 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) lucky bringing up ccsm and then disabling and re-enabling window decoration restores nicely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/962085 Title: [0.9.7.2] gtk-window-decorator receives BadWindow errors To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/962085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752445] Re: Intermittent white window contents when maximizing/switching windows
It became a lot better when I changed two things in ccsm: 1. Disable Extras / Window Previews 2. select Force synchronization between GL and GLX in Utility / Workarounds. There still are screen redraw issues, but - for me - no longer in the window content, now the task bar is black, but that may be a compiz reconfigure bug. As long as I can now use all my emacs windows and resize them, I'll be willing to wait for a real fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752445 Title: Intermittent white window contents when maximizing/switching windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/752445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752445] Re: Intermittent white window contents when maximizing/switching windows
Sadly I have to take this back. I have since stressed the settings more and the immediate results are not persistent, sadly. Essentially there are still cases, where emacs does not redraw properly. Pity! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752445 Title: Intermittent white window contents when maximizing/switching windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/752445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410285] Re: Dell Latitude E6500 freezes when put on docking station
Got a E6500 (8GB) with 9.10 64bit here. Intermittent complete freeze (especially when any power management happening, I initially thought this was suspend to something, but it also happens while I'm typing). Additionally I have intermittent USB host controller process errors regardless which type of device is attached. Is this also in place for other people? Messages like the below happen in the log then: [21670.277650] uhci_hcd :00:1d.0: host controller process error, something bad happened! [21670.277679] uhci_hcd :00:1d.0: host controller halted, very bad! [21670.277732] uhci_hcd :00:1d.0: HC died; cleaning up [21670.27] usb 6-1: USB disconnect, address 2 [21670.373614] usb 6-2: USB disconnect, address 3 I tried a new BIOS (A18, which helped a bit), I tried various kernels (-16 and -18 seem to be better than -17), but the intermittent freezes are extremely annoying... -- Dell Latitude E6500 freezes when put on docking station https://bugs.launchpad.net/bugs/410285 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 264265] Re: GNOME non-evdev keyboard config broken
The bug is fixed in Jaunty. I'd suggest to close it. -- GNOME non-evdev keyboard config broken https://bugs.launchpad.net/bugs/264265 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 303074] Re: [intrepid] /etc/init.d/rc level parsing is fragile
Personally I had a few local startup scripts tagged as SA1 to SA3, which I agree is debatable, but happens to work on all flavours of UNIX I have encountered so far. The effect was a double start of all daemons on init level 2. If we discard this as an invalid example, there is no guarantee, that the filename part following S?? has to start with an alphabetic letter, so the current parsing is certainly incorrect. -- [intrepid] /etc/init.d/rc level parsing is fragile https://bugs.launchpad.net/bugs/303074 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 303159] Re: IFUPDOWN - connections that are mapped should be locked to the mapping device
The ifupdown interpretation of the mapping is: a. If auto stanza exists run ifup $DEVICE at startup b. When ifup $DEVICE is run for a mapping, run the mapping script, and apply the config. My personal preference for the ideal user-side experience for a mapping device would be: a. when device is not available hide all $MAPPING::$DEVICE virtual configuration b. when a device becomes available, and an auto stanza exists, run the equivalent of ifup $DEVICE c. when a device becomes available, and no auto stanza exists, offer the user a choice, i.e. don't activate the device, activate one of the $MAPPING::$DEVICE virtual connections, and a $MAPPING::automatic option that runs the script. d. if a device is available, but the user did not activate it at the time it became available, then offer all $MAPPING::$DEVICE combinations Feedback: For this 1. and 2a. are fine. I am not sure 2b. is correct if a mapping device is not locked, yet, but available via hal. I'd prefer to export virtual configuration always when a device is available via hal (if a list of configurations can be made mutually exclusive). This is important, if only to allow the user to override the script decision. About 3. we should only run the single mapping script that this hal-device-available event was for, not all of them, and only if the auto stanza exists (see above). for 4. you mean a reload of the interfaces file? -- IFUPDOWN - connections that are mapped should be locked to the mapping device https://bugs.launchpad.net/bugs/303159 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 303159] Re: IFUPDOWN - connections that are mapped should be locked to the mapping device
I dont think I understand what you are trying to do. We could determine the MAC from HAL, right. The issue is, that we cannot do anything from there, I really wonder how this ever worked for me even with the eth0-XXX naming convention, how did it know which interface to operate on? Consider the following example interfaces file from /usr/share/doc/ifupdown/examples/network-interfaces.gz auto eth0 eth1 mapping eth0 eth1 script /path/to/get-mac-address.sh map 11:22:33:44:55:66 lan map AA:BB:CC:DD:EE:FF internet iface lan inet static address 192.168.42.1 netmask 255.255.255.0 pre-up /usr/local/sbin/enable-masq $IFACE iface internet inet dhcp pre-up /usr/local/sbin/firewall $IFACE both auto and mapping apply to multiple values which the parser does not support as of today, at least I think so. Additionally we don't know the mac address of each interface before HAL registers the device. For the iface stanzas we have no clue, which physical interface they will be applied to. I suspect this example is to work around issues of ethernet device naming without iftab friends. So, a priori we can treat a mapping as a device name (which it is) which can then be used just like a VPN connection, i.e. it can be switched on and off, or we could allow via nm-applet to link one of the unused stanzas to the mapping device, cool but a lot of change. -- IFUPDOWN - connections that are mapped should be locked to the mapping device https://bugs.launchpad.net/bugs/303159 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 303159] Re: IFUPDOWN - connections that are mapped should be locked to the mapping device
** Attachment added: sample /etc/network/interfaces http://launchpadlibrarian.net/20059194/interfaces -- IFUPDOWN - connections that are mapped should be locked to the mapping device https://bugs.launchpad.net/bugs/303159 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 303159] Re: IFUPDOWN - connections that are mapped should be locked to the mapping device
** Attachment added: sample /usr/local/sbin/detect-network http://launchpadlibrarian.net/20059214/detect-network -- IFUPDOWN - connections that are mapped should be locked to the mapping device https://bugs.launchpad.net/bugs/303159 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
For whatever reason I did not find it in intrepid-proposed, so I downloaded the deb and installed it. It seems to work the same as my hand-patched version, so I'd consider this working. The startup race persists, which is expected. With this, the bug can be closed. -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
checked was (from /var/lib/dpkg/status): Package: network-manager Status: install ok installed Priority: optional Section: net Installed-Size: 1940 Maintainer: Ubuntu Core Dev Team [EMAIL PROTECTED] Architecture: i386 Version: 0.7~~svn20081018t105859-0ubuntu1.8.10.1 Replaces: network-manager-pptp ( 0.7~~) Depends: libc6 (= 2.4), libdbus-1-3 (= 1.0.2), libdbus-glib-1-2 (= 0.74), libglib2.0-0 (= 2.16.0), libhal1 (= 0.5.8.1), libnl1, libnm-glib0 (= 0.7~~svn20080908), libnm-util0 (= 0.7~~svn20080908), libnspr4-0d (= 1.8.0.10), libnss3-1d (= 3.12.0~1.9b1), libpolkit-dbus2 (= 0.7), libpolkit2 (= 0.7), libuuid1 (= 1.05), iproute, iputils-arping, lsb-base (= 2.0-6), wpasupplicant (= 0.6.1~), dbus (= 0.60), hal (= 0.5.7.1), update-notifier-common Recommends: network-manager-gnome | network-manager-kde Conflicts: network-manager-pptp ( 0.7~~) Conffiles: /etc/dbus-1/system.d/NetworkManager.conf 2f9a653fcad0a7e091dac46b4288065d /etc/dbus-1/system.d/nm-dhcp-client.conf 5fe2b938444987d8644d782b7cdee710 /etc/dbus-1/system.d/nm-dispatcher.conf e1d16d69e5e8065ca37ac8245b562a42 /etc/dbus-1/system.d/nm-system-settings.conf 21b3892f02ec1acceb48b25baa988ff0 /etc/dbus-1/system.d/nm-avahi-autoipd.conf 1789b8276205e55c633afe1f3eb9b433 /etc/NetworkManager/dispatcher.d/01ifupdown 2bc1ae04a18972cd4b9acfaf6aa2104f /etc/NetworkManager/nm-system-settings.conf bc4a4aa7e1b84e080946bf081dd87eb0 /etc/init.d/NetworkManager 3b22837a479a87d3cbb4a75e5cd9e10e Description: network management framework daemon NetworkManager attempts to keep an active network connection available at all times. It is intended only for the desktop use-case, and is not intended for usage on servers. The point of NetworkManager is to make networking configuration and setup as painless and automatic as possible. If using DHCP, NetworkManager is _intended_ to replace default routes, obtain IP addresses from a DHCP server, and change nameservers whenever it sees fit. . This package provides the userspace daemons. . Homepage: http://www.gnome.org/projects/NetworkManager/ Original-Maintainer: Riccardo Setti [EMAIL PROTECTED] -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 303159] Re: IFUPDOWN - connections that are mapped should be locked to the mapping device
** Description changed: Binary package hint: network-manager When running in managed=true mode, ifupdown will export configurations of a mapping entry in /etc/network/interfaces without locking it to the mapping device origin. + + If a device exists with a mapping stanza then the mapping script may + select any of iface stanza devices. The script is pretty much in + control of the naming of the device, so a $DEV-.* regex is wrong to + assume. A priori not even the link to a physical device is possible + without running the script, as the same mapping may be applicable to + multiple devices. + + Probably the right thing to do is to hide all iface/mapping + connections that do not correspond to HAL-known devices. Then treat a + mapping like a DHCP connection, where a script is called on activation + (as in ifupdown) to select the iface stanza connection for + configuration. -- IFUPDOWN - connections that are mapped should be locked to the mapping device https://bugs.launchpad.net/bugs/303159 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 293755] Re: [intrepid] network manager has startup race
I fixed the double startup problem in /etc/init.d/rc, will report the issue there. The startup race with NetworkManager persists, though, so this was nto the issue. -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 303074] [NEW] [intrepid] /etc/init.d/rc level parsing is fragile
Public bug reported: Binary package hint: sysvinit /etc/init.d/rc attempts to group scripts in calls to startup by level. The code to do this has certain assumptions built in. like a name always starting with a letter. For better compatibility with update-rc.d I'd suggest to strip the prefix and than take the next two characters for the level. This is a lot more stable against double starts. ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New -- [intrepid] /etc/init.d/rc level parsing is fragile https://bugs.launchpad.net/bugs/303074 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 303074] Re: [intrepid] /etc/init.d/rc level parsing is fragile
** Attachment added: patch to set level to the first two chars after [SK] http://launchpadlibrarian.net/20019655/sysvinit_rc.patch -- [intrepid] /etc/init.d/rc level parsing is fragile https://bugs.launchpad.net/bugs/303074 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 293755] Re: [intrepid] network manager has startup race
double startup issue was: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/303074 -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 299284] Re: Network Manager having issues with two concurrent connections
Just to know what it'll attempt to do: what are your /etc/network/interfaces, /etc/NetworkManager/nm-system-settings.conf, nm-tool output, and relevant syslog for both machines? -- Network Manager having issues with two concurrent connections https://bugs.launchpad.net/bugs/299284 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 293755] Re: [intrepid] network manager has startup race
This appears to be in upstart, not network manager. Somehow the rc2 symlinks are started twice, at least I see atd complaining about being started twice as well. Only NetworkManager really fails if being started while running. I suspect that some of the underlying infrastructure like dbus does not handle this gracefully and then nm- applet connects to a different dbus than the running NetworkManager. This also explains, why a restart of NetworkManager resolves the issue. -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 290973] Re: not connected to network when booting
The above statement is certainly incorrect: network-manager in intrepid does not support /etc/network/interfaces configuration. The ifupdown plugin does support interfaces in /etc/network/interfaces, it just does not support mapping stanzas properly. As /etc/init.d/networking is run before /etc/init.d/NetworkManager, it is not really relevant, whether both exist or not, and the ifupdown plugin can be configured to leave certain interfaces alone. -- not connected to network when booting https://bugs.launchpad.net/bugs/290973 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 290973] Re: not connected to network when booting
I am afraid there is currently no such mode as network manager disabled. If you look at the code, all you can do is disable the grab of network manager to all devices. if you disable, you actually only disable network manager for devices configured in /etc/network/interfaces using an iface stanza. All other devices are still handled by network manager even in this mode. The only true disabled mode would be to uses sysv-rc and remove the rc*.d links and even then I'd not be sure whether something in the dbus or gnome config would start it, anyway ;-) -- not connected to network when booting https://bugs.launchpad.net/bugs/290973 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 293755] Re: [intrepid] network manager has startup race
I traced this part now. It seems that it is not NetworkManager per se, but rather start-stop-daemon complaining that NetworkManager is already running. Now I have to find which other mechanism has started NetworkManager earlier. The rc*.d links look perfectly ok... Looking... This now could be an upgrade issue or a subtle change in ubuntu usage of runlevels... -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 293751] Re: [intrepid] network manager does not stop nm-system-settings when stopped
Wouldn't it be better to use inotify on /etc/network and /etc/network/interfaces to have nm-system-settings be notified of any changes in the file? The same would certainly apply to ifcfg for Fedora and SuSE, i.e. /etc/sysconfig/network-scripts for Fedora-based dists. Then the file(s) can just be reloaded, when changed and the need for a daemon restart is gone. Why is nm-system-settings coupled with NetworkManager (started implicitely), anyway? Why can't nm-system-settings be explicitely started and stopped from the init.d script with e.g. a dbus-message nm- system-settings-available and nm-system-settings-unavailable to message state between daemons (to avoid races). Even separate init.d scripts would make sense IMO. -- [intrepid] network manager does not stop nm-system-settings when stopped https://bugs.launchpad.net/bugs/293751 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 293751] Re: [intrepid] network manager does not stop nm-system-settings when stopped
The only thing I'd mean to do with inotify is to make the /etc/network/interfaces cache in memory always represent the content of the file at this time. It does not mean, that this cache has to be used right now. The comparison with ifupdown seems to indicate a deferred application has to be one option (probably even the default), but what I always do in sw: If you don't know for sure which way is the right one, make it configurable. So, my suggestion would be: pass an if_block ** to the parser instead of keeping the static pointer, to create the cached memory structure on init and on inotify. Keep two pointers in the plugin private data: activeFirstIfBlock and currentFirstIfBlock, i.e. separate pointers to separate caches. If the current one is activated the pointer is null'd, if the active one is replaced, it is destroyed. I guess I'll make a proposal in patch form ;-) could nm-tool be extended to have some useful introspection commands? nm-tool plugin ifupdown reload -- reload config of this plugin nm-tool plugin ifupdown config -- dump config of this plugin nm-tool plugin ifupdown status -- dump state of this plugin nm-tool show syslog-level nm-tool set syslog-level debug ... -- [intrepid] network manager does not stop nm-system-settings when stopped https://bugs.launchpad.net/bugs/293751 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
the issue was, that the ifupdown plugin may or may not be part of the GNOME project, I was not sure. upstream of ubuntu is debian then GNOME. I checked the GNOME code now, and you are right, this is the place to report these kinds of cleanup issues. -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
I agree, this is a patch I intend to submit. -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
** Attachment added: ifupdown - treats mapping and iface as well known device http://launchpadlibrarian.net/19345567/ifupdown_unmanage_mapping_and_iface.patch -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
Please note, that this is the minimal patch I'd include in an update, not the changes I'd like to include in this file. memory management in this file is still messed up and syslog messages are pretty inconsistent, and ... I tested, that with this change applied all combinations work (but of course the NetworkManager startup at boot still fails in the managed=false case). -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 293755] [NEW] [intrepid] network manager has startup race
Public bug reported: Binary package hint: network-manager NetworkManager fails the initial startup, but when restarted starts cleanly. Killing off nm-system-settings with NetworkManager down and then starting up does not suffice to replicate this situation. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 293755] Re: [intrepid] network manager has startup race
** Attachment added: interfaces http://launchpadlibrarian.net/19345771/interfaces -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 293755] Re: [intrepid] network manager has startup race
** Attachment added: nm-system-settings.conf http://launchpadlibrarian.net/19345779/nm-system-settings.conf -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 293751] [NEW] [intrepid] network manager does not stop nm-system-settings when stopped
Public bug reported: Binary package hint: network-manager When /etc/init.d/NetworkManager stop is executed as root, the nm-system- settings daemon survives, making it impossible to reload static configuration like Debian's /etc/network/interfaces. network-manager-0.7~~svn20081018t105859 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- [intrepid] network manager does not stop nm-system-settings when stopped https://bugs.launchpad.net/bugs/293751 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 291564] Re: [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode
What is the right place to report bugs in the ifupdown plugin in general? I assume, this component is debian specific, not ubuntu specific. The more I look at the code, the more I have to suggest some cleanup exercise, like memory management. E.g. I do not think interface_parser.c should allocate memory using g_strudup and free it using free. I have to look in more detail, but there are a few locations in the code, that just smell like memory leaks. -- [intrepid] ifupdown network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 293755] Re: [intrepid] network manager has startup race
I think I'll add a bit of debug to my private version of NetworkManager... I only saw the [fail] on the console, and NetworkManager did certainly run, so did nm-system-settings. I wondered whether dbus or hal were not up properly, yet, at the time NetworkManager was started. The logs are in the original bug in the after-boot.zip -- [intrepid] network manager has startup race https://bugs.launchpad.net/bugs/293755 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 291564] Re: [intrepid] network manager must be restarted after every boot
After boot there was no nm-applet icon in the GNOME notification area. I expected to see one there. The applet was running, I suppose, but was not showing in the notification area. At this time, all networking interfaces were killed by NetworkManager. After restart of NetworManager the nm-applet icon did show up (with the red cross indicating no connection), and offered me the mapped interfaces. I'd have expected this to happen after boot, or my interfaces be left alone. Ideal operation for me would have been: after boot nm-applet shows up, the mapping-selected wired connection is active, the others are available for selection, wireless is enabled. If that is not possible, I'd have liked to have NetworkManager handle just wireless, and leave my wired connections completely alone. If that is also not possible, I guess I'll just deinstall NetworkManager ;-) -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
in hal_device_added_cb the code only checks for exact matches in iface names. I suspect it'd make more sense to check by prefix, i.e. for a device of name eth0 check for any iface_connection of name eth0 or starting with eth0-. As it is, there is no way to unmanage a device that does not have an iface line in /etc/network/interfaces -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
an alternative would be to allow for a mapping to be treated as an iface for the hal device added callback. Then the system should also know that eth0 is a managed device. -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode
The current subject line addresses the more important part of the issues, i.e. the inconsistent behavior. With this fix, managed=false should consistently let things alone, if eth0 and eth1 are listed in iface or mapping. We did not yet understand or debug the reason, why NetworkManager does not even start properly during my boot process if I have managed=false. It seems to be half-functional, triggered by a race, and that's a problem in itself. I guess, I'll (as an experiment) try gdb first and then use tracing syslog to nail this one. It should be a separate bug, though. P.S. the more I think about it, the more I believe, that a mapping in /etc/network/interfaces indicates, that this is a well-known device, so unmanage_well_known should apply. It is a pity network manager can not be configured to be completely inactive even for not-well-known devices, maybe that should be an enhancement request... -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode
I think the managed= is very misleading. A better name would be: manage_only_well_known_devices (if this really has to be a boolean) If a SRU is made, perhaps a comment in the defalt nm-system-settings.xml, that explains what this does would be in order. For a future Ubuntu release I'd propose to change the value to be an enumeration: manage=none (not possible, at this moment) manage=known (aka false) manage=all (aka true) -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
yes, it seems to. I tried it this morning. Then nm-applet shows, wireless appears and the mapped interfaces are showing in the nm-applet menu. In managed=false, this seems to be a race of some kind. I used sysv-rc to take NetworkManager out of the boot, and start it for the first time in an xterm, but everything just appeared. Maybe I should create a new runlevel, that is all boot stuff until NetworkManager and then try things in there. Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: autoconnect Nov 2 11:26:42 stephan-lap nm-system-settings:SCPluginIfupdown: management mode: unmanaged Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_11_43_75_eb_d0, iface: eth0) Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_13_ce_e7_d9_f8, iface: eth1) Nov 2 11:26:42 stephan-lap nm-system-settings:Ifupdown: get unmanaged devices count: 1 Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: (152797424) ... get_connections. Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: (152797424) connections count: 6 Nov 2 11:26:42 stephan-lap nm-system-settings:Ifupdown: get unmanaged devices count: 1 Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: end _init. look at the management mode: unmanaged und then the unmanaged devices count. Doesn't this look odd? Which device is managed, even though I set managed=false? -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: after-nm-restart.zip http://launchpadlibrarian.net/19227070/after-nm-restart.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
I noticed by scanning the boot logs, that 1. the interfaces eth0 and eth1 were up and configured correctly by the time NetworkManager started. The NetworkManager startup was marked as fail, but the processes were running, which is why I did not see this. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: after-boot.zip http://launchpadlibrarian.net/19227059/after-boot.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: after-activate.zip http://launchpadlibrarian.net/19227082/after-activate.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
why do you want to use the applet? If you want to use them you should enable managed=true in /etc/NetworkMananger/nm-system-settings.conf otherwise you opt into using the old ifupdown - thats the feature. I would not have complained if that was really the case. The problem is that NetworkManager kills my eth0 and then nm-applet does not offer any way to get network connectivity back. If I restart NetworkManager later, it suddenly works, which is not consistent in its own right. I believe that NetworkManager should have two absolute requirements: 1. if any device is touched at all by NetworkManager, then nm-applet must be visible 2. a restart of NetworkManager may not change nm-applet's view of the NM state. BTW: my wanted operation mode for NM would be to leave my wired connection's initial state alone, or at least leave the /etc/network/interfaces decision on the default interface active. I'd like to use NM for wireless, and I'd be ok to use it for wired (if it'd work). -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
anyway, the other problem that your mapped interfaces do not autoconnect can probably quite easily be solved by propagating the autoconnect state of the main-connection to the mapped connections in the ifupdown legacy plugin. Not sure that would be a solution, right now all I want is NetworkManager to expose its state to nm-applet. meaning: if you have multiple wifi configurations mapped (which probably should be a common use case of mapping), NM will just autoconnect to whatever of the configured SSIDs it has in range ;). In my case I am ok with the wireless connectivity (or better I was until one of the later intrepid alphas). I use mappings for the wired connections, as the script determines whether I am physically related in our Portland office, my home office, out Amsterdam office, or whatever. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: [intrepid] network manager must be restarted after every boot
it does what I consider to be the right thing: offer me all mapping ifaces and if I select one, it works fine. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 290973] Re: not connected to network when booting
I honestly believe this bug should be re-opened. It is IMHO inacceptable that the network manager daemon needs to be restarted before the nm-applet will show. I have a very similar issue, which I'll log as a separate bug, as this one is closed, but it seems that all more interesting /etc/network/interfaces case NetworkManager to go into cryostasis until restarted a bit later. Why it then starts better, I have no clue, yet. -- not connected to network when booting https://bugs.launchpad.net/bugs/290973 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 291564] [NEW] network manager must be restarted after every boot
Public bug reported: Binary package hint: network-manager Network manager must be restarted before nm-applet will show. Then it'll display the different iface lines called from the mapping, and a mapping can manually be selected. The main issue is, that a system boot leave the system unusable, as there is no non-root activity that can revive the system ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: network manager must be restarted after every boot
** Attachment added: interfaces using mapping and then individual iface lines http://launchpadlibrarian.net/19123917/interfaces -- network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: network manager must be restarted after every boot
** Attachment added: syslog mentioning NetworkManager before and after the restart http://launchpadlibrarian.net/19123959/syslog-grep-NetworkManager -- network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 291564] Re: network manager must be restarted after every boot
stephan-lap:~# dpkg -l | grep network-manager ii network-manager 0.7~~svn20081018t105859-0ubuntu1 network management framework daemon ii network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1 network management framework (GNOME frontend) ii network-manager-openvpn 0.7~~svn20081015t024626-0ubuntu1 network management framework (OpenVPN plugin) ii network-manager-pptp 0.7~~svn20081015t024626-0ubuntu1 network management framework (PPTP plugin) ii network-manager-vpnc 0.7~~svn20081015t024626-0ubuntu1 network management framework (VPNC plugin) ** Summary changed: - network manager must be restarted after every boot + [intrepid] network manager must be restarted after every boot ** Description changed: Binary package hint: network-manager Network manager must be restarted before nm-applet will show. Then it'll display the different iface lines called from the mapping, and a mapping can manually be selected. The main issue is, that a system boot leave the system unusable, as there is no non-root activity that can revive the system + + This is on intrepid, as of 2008-10-31 -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 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 290973] Re: not connected to network when booting
I guess bug 291564 is then a potential duplicate. I think the biggest complaint is, that NetworkManager is successful in killing my eth0, but no successful in displaying nm-applet. This makes it impossible for me to use the network, unless I restart NetworkManager as root. Something in the ifupdown plugin feels wrong. I'll now follow the DebuggingNetworManager procedures to see what exactly happens. -- not connected to network when booting https://bugs.launchpad.net/bugs/290973 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 264256] Re: gdm startup is not moved from 21 to 30 on upgrade
I am afraid, I pretty closely follow the intrepid uploads, so there are quite a few upgrades. 2007-10-19 09:25:06 upgrade gdm 2.18.1-0ubuntu1 2.20.0-0ubuntu6 2007-10-19 14:56:30 status installed gdm 2.20.0-0ubuntu6 2007-11-19 22:44:23 upgrade gdm 2.20.0-0ubuntu6 2.20.1-0ubuntu1 2007-11-19 22:49:32 status installed gdm 2.20.1-0ubuntu1 2008-03-26 11:45:16 upgrade gdm 2.20.1-0ubuntu1 2.20.4-0ubuntu2 2008-03-26 13:17:20 status installed gdm 2.20.4-0ubuntu2 2008-04-07 08:50:43 upgrade gdm 2.20.4-0ubuntu2 2.20.4-0ubuntu3 2008-04-07 08:54:38 status installed gdm 2.20.4-0ubuntu3 2008-04-09 13:18:21 upgrade gdm 2.20.4-0ubuntu3 2.20.5-0ubuntu2 2008-04-09 13:28:29 status installed gdm 2.20.5-0ubuntu2 2008-04-22 08:45:29 upgrade gdm 2.20.5-0ubuntu2 2.20.5-0ubuntu3 2008-04-22 08:48:52 status installed gdm 2.20.5-0ubuntu3 2008-05-19 08:14:24 upgrade gdm 2.20.5-0ubuntu3 2.20.6-0ubuntu1 2008-05-19 08:15:23 status installed gdm 2.20.6-0ubuntu1 2008-05-27 07:39:59 upgrade gdm 2.20.6-0ubuntu1 2.20.6-0ubuntu2 2008-05-27 07:43:24 status installed gdm 2.20.6-0ubuntu2 2008-07-17 18:17:52 upgrade gdm 2.20.6-0ubuntu2 2.20.7-0ubuntu2 2008-07-17 18:55:06 status installed gdm 2.20.7-0ubuntu2 2008-07-29 21:05:07 upgrade gdm 2.20.7-0ubuntu2 2.20.7-0ubuntu3 2008-07-29 21:08:32 status installed gdm 2.20.7-0ubuntu3 2008-08-09 12:23:20 upgrade gdm 2.20.7-0ubuntu3 2.20.7-0ubuntu4 2008-08-09 12:24:34 status installed gdm 2.20.7-0ubuntu4 2008-09-03 12:26:13 upgrade gdm 2.20.7-0ubuntu4 2.20.7-0ubuntu5 2008-09-03 12:28:13 status installed gdm 2.20.7-0ubuntu5 2008-09-04 16:27:31 upgrade gdm 2.20.7-0ubuntu5 2.20.8-0ubuntu1 2008-09-04 17:22:58 status installed gdm 2.20.8-0ubuntu1 2008-10-09 07:01:21 upgrade gdm 2.20.8-0ubuntu1 2.20.8-0ubuntu2 2008-10-09 07:02:49 status installed gdm 2.20.8-0ubuntu2 -- gdm startup is not moved from 21 to 30 on upgrade https://bugs.launchpad.net/bugs/264256 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 264256] Re: X cannot load evdev_drv at boot as hal is not ready
** Attachment added: X log with failure http://launchpadlibrarian.net/17258012/Xorg.0.log.old -- X cannot load evdev_drv at boot as hal is not ready https://bugs.launchpad.net/bugs/264256 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 264256] [NEW] X cannot load evdev_drv at boot as hal is not ready
Public bug reported: Since some time between Alpha3 and Alpha4 X is unable to load evdev_drv at gdm startup time. The relevant error message is: (EE) config/hal: couldn't initialise context: (null) ((null)) If gdm is later restarted, everything works fine, so this appears to be a race between hal / dbus startup and gdm / X startup. Description:Ubuntu intrepid (development branch) Release:8.10 hal: Installed: 0.5.11-3~ubuntu7 Candidate: 0.5.11-3~ubuntu7 Version table: *** 0.5.11-3~ubuntu7 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status xserver-xorg-input-evdev: Installed: 1:2.0.3-2 Candidate: 1:2.0.3-2 Version table: *** 1:2.0.3-2 0 500 http://archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status I am tempted to put a delay into the gdm startup to test whether this resolves the issue. ** Affects: ubuntu Importance: Undecided Status: New -- X cannot load evdev_drv at boot as hal is not ready https://bugs.launchpad.net/bugs/264256 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 264265] [NEW] GNOME non-evdev keyboard config broken
Public bug reported: When a Dell keyboard are chosen in the GNOME keyboard control, most keycodes are dumped and not even the cursor keys still work. This impacts both the Dell Latitude keyboard and an external Dell USB Multimedia keyboard. After the GNOME login, the keyboard is unusable until the USB keyboard is un/re-plugged. Switching the config to evde- controlled keyboard works fine. ** Affects: ubuntu Importance: Undecided Status: New -- GNOME non-evdev keyboard config broken https://bugs.launchpad.net/bugs/264265 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 264256] Re: X cannot load evdev_drv at boot as hal is not ready
One effect of this (timing) issue is, that any attempt to enter user/pass at the non-functional gdm login screen followed by a GDM restart will display user and password in the clear on vt7 while X moves to vt8. Without evdev present the input goes to the vt7 and when X no longer displays on this vt... -- X cannot load evdev_drv at boot as hal is not ready https://bugs.launchpad.net/bugs/264256 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 264256] Re: X cannot load evdev_drv at boot as hal is not ready
** Attachment added: X conf, just in case http://launchpadlibrarian.net/17258510/xorg.conf -- X cannot load evdev_drv at boot as hal is not ready https://bugs.launchpad.net/bugs/264256 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 264256] Re: X cannot load evdev_drv at boot as hal is not ready
** Attachment added: X log from immediate restart http://launchpadlibrarian.net/17258018/Xorg.0.log -- X cannot load evdev_drv at boot as hal is not ready https://bugs.launchpad.net/bugs/264256 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 264256] Re: X cannot load evdev_drv at boot as hal is not ready
This actually appears to be a gdm upgrade issue where the update-rc.d is not run correctly to move gdm from 21 to 30. If I manually move gdm to 30 it works fine, otherwise hal starts AFTER gdm. ** Changed in: gdm (Ubuntu) Sourcepackagename: None = gdm ** Summary changed: - X cannot load evdev_drv at boot as hal is not ready + gdm startup is not moved from 21 to 30 on upgrade -- gdm startup is not moved from 21 to 30 on upgrade https://bugs.launchpad.net/bugs/264256 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 242299] Re: evolution can't save as attachment
In case someone does not want to wait (it annoyed me for sure), I took the upstream patch and converted it to a debian patch to be added to evolution-data-server-2.23.4/debian/patches. This fixes the problem if libcamel1.2-12 is updated. ** Attachment added: 70_evolution_attachments.patch http://launchpadlibrarian.net/16250678/70_evolution_attachments.patch -- evolution can't save as attachment https://bugs.launchpad.net/bugs/242299 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 210260] [NEW] evolution word doc attachment throws SIGSEGV
Public bug reported: Binary package hint: libcamel1.2-11 Trying to attach a word doc to an email evolution throws SIGSEGV with the following stacktrace Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb663f740 (LWP 4762)] 0xb7b60795 in camel_header_set_param () from /usr/lib/libcamel-1.2.so.11 (gdb) info stack #0 0xb7b60795 in camel_header_set_param () from /usr/lib/libcamel-1.2.so.11 #1 0xb7b6087e in camel_content_type_set_param () from /usr/lib/libcamel-1.2.so.11 #2 0xb7b5d939 in camel_mime_part_set_filename () from /usr/lib/libcamel-1.2.so.11 #3 0xb7edcecf in e_attachment_new () from /usr/lib/evolution/2.22/libemiscwidgets.so.0 #4 0xb7ede639 in e_attachment_bar_attach () from /usr/lib/evolution/2.22/libemiscwidgets.so.0 #5 0xb64a0f82 in ?? () from /usr/lib/evolution/2.22/components/libevolution-mail.so #6 0x09494018 in ?? () #7 0x0959a7d0 in ?? () #8 0xb64b91be in ?? () from /usr/lib/evolution/2.22/components/libevolution-mail.so #9 0xb7511af9 in gtk_toggle_button_get_active () from /usr/lib/libgtk-x11-2.0.so.0 #10 0xb649e154 in ?? () from /usr/lib/evolution/2.22/components/libevolution-mail.so #11 0x084560b8 in ?? () #12 0x096055b0 in ?? () #13 0x in ?? () home:$ lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 home:$ apt-cache policy evolution libcamel1.2-11 evolution: Installed: 2.22.0-0ubuntu2 Candidate: 2.22.0-0ubuntu2 Version table: *** 2.22.0-0ubuntu2 0 500 http://de.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status libcamel1.2-11: Installed: 2.22.0-0ubuntu2 Candidate: 2.22.0-0ubuntu2 Version table: *** 2.22.0-0ubuntu2 0 500 http://de.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- evolution word doc attachment throws SIGSEGV https://bugs.launchpad.net/bugs/210260 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
