[Desktop-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager still autoconnects just fine after boot. The configuration looks identical on both machines. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: Confirmed Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804457] [NEW] ANSI codes for Save/Restore Cursor Position not working in 0.54.1
Public bug reported: The current version of vte2.91 is 0.54.1 which breaks SCOSC/SCORC ANSI codes for saving the cursor position and returning to it. (Aka. SCP and RCP) This is fixed in 0.54.2 as per https://gitlab.gnome.org/GNOME/vte/issues/48 . Please update package for cosmic. ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1804457 Title: ANSI codes for Save/Restore Cursor Position not working in 0.54.1 Status in vte2.91 package in Ubuntu: New Bug description: The current version of vte2.91 is 0.54.1 which breaks SCOSC/SCORC ANSI codes for saving the cursor position and returning to it. (Aka. SCP and RCP) This is fixed in 0.54.2 as per https://gitlab.gnome.org/GNOME/vte/issues/48 . Please update package for cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1804457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
The error message is: Preparing to unpack .../bash_4.4-2ubuntu1_amd64.deb ... Unpacking bash (4.4-2ubuntu1) over (4.3-15ubuntu1) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu15) ... update-initramfs: deferring update (trigger activated) dpkg: dependency problems prevent processing triggers for cracklib-runtime: cracklib-runtime depends on file; however: Package file is not configured yet. dpkg: error processing package cracklib-runtime (--configure): dependency problems - leaving triggers unprocessed And then that error about the dependency problem with cracklib-runtime repeats over and over until it aborts because of "too many errors". ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+attachment/4862209/+files/apt-term.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Incomplete Bug description: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1681231] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) ** Affects: cracklib2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: New Bug description: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 918657] Re: unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector
I'm on Vivid Beta 1 now and still no gear icon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/918657 Title: unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector Status in Unity Greeter: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Bug description: After updating the package unity-greeter from version 0.1.1-0ubuntu1 - to version 0.2.0-0ubuntu2 I can't select any other desktops - it starts with the former selected unity 3D only. Available desktops are: GNOME (3), TERMINAL (1), UNITY, UNITY-2D Downgrading to the former package allowes to select all. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-greeter 0.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1 Uname: Linux 3.2.0-9-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Thu Jan 19 13:33:33 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity-greeter UpgradeStatus: Upgraded to precise on 2012-01-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/918657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1066484] Re: long delay at shutdown/reboot - network-manager doesn't close correctly
While trying to catch a samba related bug, Steve Langasek pointed me to this NM bug. The screenshot shows the nm-dispatcher.action: Caught signal 15, shutting down... message. Steve's comment (https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/comments/191): Markus, your screenshot shows a network-manager error: nm-dispatcher.action: Caught signal 15, shutting down... This indicates that some part of NM is not being correctly guarded from /etc/init.d/sendsigs, resulting in abnormal termination that breaks the network connection before network filesystems are being unmounted. Network Manager has previously been fixed for such bugs, but it seems to have recurred. ** Attachment added: Shutdown messages https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066484/+attachment/3689222/+files/IMG_20130527_192438.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1066484 Title: long delay at shutdown/reboot - network-manager doesn't close correctly Status in “network-manager” package in Ubuntu: Confirmed Bug description: there is a long delay when shutting down or restarting the system. it looks like the network-manager service hangs when stopping in init6. * Asking all remaining processes to terminate... [OK] * Killing all remaining processes... [fail] nmdispatcher.action caught signal 15 shutting down ... If I manually stop the network-manager service before shutdown/restart then everything works fine this bug is probably related to this old one (solved in 12.04): https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/869635 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Steve, turns out, there already was such a bug report: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1066484/comments/11 Regarding the CIFS mounts: Today, I changed the auto cifs mounts during startup to noauto,user mounts, which get mounted by my user using a script after login. At the end of the day, the delay upon shutdown was gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) Status in “dbus” package in Ubuntu: Fix Released Status in “dhcdbd” package in Ubuntu: Invalid Status in “netbase” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “samba” package in Ubuntu: Invalid Status in “sysvinit” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: Fix Released Status in “dbus” source package in Lucid: New Status in “dhcdbd” source package in Lucid: Invalid Status in “netbase” source package in Lucid: New Status in “network-manager” source package in Lucid: New Status in “samba” source package in Lucid: New Status in “sysvinit” source package in Lucid: New Status in “wpasupplicant” source package in Lucid: New Status in “dbus” source package in Natty: New Status in “dhcdbd” source package in Natty: Invalid Status in “netbase” source package in Natty: New Status in “network-manager” source package in Natty: New Status in “samba” source package in Natty: New Status in “sysvinit” source package in Natty: New Status in “wpasupplicant” source package in Natty: New Status in “sysvinit” package in Debian: New Bug description: IMPORTANT: this bug has enough information; please don't post _anything_ unless a developer asks for specific feedback! By posting to this bug you only make it harder for a developer to spot the gem comments. Please use the me too feature of launchpad to signal that you are affected and would like to see this fixed. I installed smbfs,and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: //ip address of nas box/share name /home/hamish/directory name cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of cifs in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid this number changes And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Here's a screenshot of the last few lines visible before my notebook shuts down. It's 13.04 as of May 27th. ** Attachment added: Shutdown messages https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/+attachment/3688214/+files/IMG_20130527_192438.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) Status in “dbus” package in Ubuntu: Fix Released Status in “dhcdbd” package in Ubuntu: Invalid Status in “netbase” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “samba” package in Ubuntu: Invalid Status in “sysvinit” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: Fix Released Status in “dbus” source package in Lucid: New Status in “dhcdbd” source package in Lucid: Invalid Status in “netbase” source package in Lucid: New Status in “network-manager” source package in Lucid: New Status in “samba” source package in Lucid: New Status in “sysvinit” source package in Lucid: New Status in “wpasupplicant” source package in Lucid: New Status in “dbus” source package in Natty: New Status in “dhcdbd” source package in Natty: Invalid Status in “netbase” source package in Natty: New Status in “network-manager” source package in Natty: New Status in “samba” source package in Natty: New Status in “sysvinit” source package in Natty: New Status in “wpasupplicant” source package in Natty: New Status in “sysvinit” package in Debian: New Bug description: IMPORTANT: this bug has enough information; please don't post _anything_ unless a developer asks for specific feedback! By posting to this bug you only make it harder for a developer to spot the gem comments. Please use the me too feature of launchpad to signal that you are affected and would like to see this fixed. I installed smbfs,and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: //ip address of nas box/share name /home/hamish/directory name cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of cifs in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid this number changes And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
The problem is still there on a fresh Raring installation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/211631 Title: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) Status in “dbus” package in Ubuntu: Fix Released Status in “dhcdbd” package in Ubuntu: Invalid Status in “netbase” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “samba” package in Ubuntu: Invalid Status in “sysvinit” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: Fix Released Status in “dbus” source package in Lucid: New Status in “dhcdbd” source package in Lucid: Invalid Status in “netbase” source package in Lucid: New Status in “network-manager” source package in Lucid: New Status in “samba” source package in Lucid: New Status in “sysvinit” source package in Lucid: New Status in “wpasupplicant” source package in Lucid: New Status in “dbus” source package in Natty: New Status in “dhcdbd” source package in Natty: Invalid Status in “netbase” source package in Natty: New Status in “network-manager” source package in Natty: New Status in “samba” source package in Natty: New Status in “sysvinit” source package in Natty: New Status in “wpasupplicant” source package in Natty: New Status in “sysvinit” package in Debian: New Bug description: IMPORTANT: this bug has enough information; please don't post _anything_ unless a developer asks for specific feedback! By posting to this bug you only make it harder for a developer to spot the gem comments. Please use the me too feature of launchpad to signal that you are affected and would like to see this fixed. I installed smbfs,and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: //ip address of nas box/share name /home/hamish/directory name cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of cifs in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid this number changes And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/211631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966294] Re: gstreamer hangs when accessing webcam (on specific hardware)
Just for the record: Had this problem today with the current 12.10 64-bit installer on a Lenovo E530. The installer was booted via EFI from USB stick. Removing the ubi-webcam.py didn't work. But I noticed a dd process taking ~10% CPU although the installer showed that all files were already copied. A few minutes later this was still the case so I killed that process and voilà - the installer went on and finished successfully. My installation layout: /dev/sda (1TB HDD) /dev/sda1 - /home (999GB) /dev/sda2 - swap (1GB) /dev/sdb (16GB mSATA SSD) /dev/sdb1 - efi (256MB) /dev/sdb2 - / (15.7GB) Maybe it has something to do with it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/966294 Title: gstreamer hangs when accessing webcam (on specific hardware) Status in The GStreamer Multimedia Framework: Fix Released Status in “gstreamer0.10” package in Ubuntu: Fix Released Status in “gstreamer0.10” source package in Precise: Fix Released Bug description: Every time I install ubuntu on this hardware with ubiquity it hangs before the camera loads and after clicking continue on the choose a user screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.3 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 15:56:40 2012 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120327.1) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/966294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 506504] Re: Thunderbird steals focus too often
For me, Thunderbird (+Lightning) just pops up into the foreground without stealing focus. But it's annoying as hell, because it seems to emit some notification which is instantly removed again. And thus, the main window pops up every few minutes without any important message. This is on Ubuntu Oneiric 64bit as of today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/506504 Title: Thunderbird steals focus too often Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird Thunderbird constantly steals focus, which is annoying for several reasons: 1. it disrupts the current activity 2. when thunderbird is running in another desktop, it is difficult to understand what is happening. Disruption windows (popups) include e.g. Domain name mismatch, or failed to connect to server. As I understand, such popups make sense if the user updates the mailbox actively. However, they should be disabled when mailboxes are updated automatically, since these problems do not require immediate attention. System: Ubuntu 9.10 thunderbird: Installed: 2.0.0.23+build1+nobinonly-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/506504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
