[Touch-packages] [Bug 1571786] Re: Broadcom 43602 requires module to be reloaded to work
Same here with DELL XPS15 9550. in case of failure Network Manager recognizes the Wifi adapter as "PCI ethernet" not as Wifi adapter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1571786 Title: Broadcom 43602 requires module to be reloaded to work Status in network-manager package in Ubuntu: Confirmed Bug description: Running 16.04, and a recent update (last week?) introduced the following issue. I have a Broadcom wireless card: 02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC (rev 01) Upon startup the network will connect fine. Then after about a minute it will drop out. Possibly related to the following in dmesg: [ 163.870916] brcmfmac :02:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 If I rmmod and re-insert brcmfmac it works until the next reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448917] Re: apt-get -o quiet=1 dist-upgrade isn't quiet anymore
Oops, no need for such a (kind of) rude answer =( Yes, I mean the (Reading database... messages and I have not looked into the code of apt to tell where they come from. All I know is that the call to apt-get with quiet option isn't quiet anymore, the behaviourof apt-get from a user point of view has changed from Utopic to Vivid, so this is a valid bug report for this package and the version mentioned. It is a real life problem as it breaks at least the package cron-apt as I mentioned in the bug report above. The maintainer of it should now decide how to proceed with it... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1448917 Title: apt-get -o quiet=1 dist-upgrade isn't quiet anymore Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 15.04 Release: 15.04 apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Current: Until updating from Utopic to Vivid apt-get with command line parameter -o quiet 1 did not output the progress as formatted text. Since the update the progress is written to stdout as formatted text. This breaks a lot of scripts, e.g. the cron-apt package with mail send enabled. The attached text is no longer text only and will be encoded as binary, so the mail is unreadable. Expected: Same behaviour as with version from Utopic, no progress output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1448917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448917] [NEW] apt-get -o quiet=1 dist-upgrade isn't quiet anymore
Public bug reported: Description:Ubuntu 15.04 Release:15.04 apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Current: Until updating from Utopic to Vivid apt-get with command line parameter -o quiet 1 did not output the progress as formatted text. Since the update the progress is written to stdout as formatted text. This breaks a lot of scripts, e.g. the cron-apt package with mail send enabled. The attached text is no longer text only and will be encoded as binary, so the mail is unreadable. Expected: Same behaviour as with version from Utopic, no progress output ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: Output of apt-get with quiet=1 parameter https://bugs.launchpad.net/bugs/1448917/+attachment/4385375/+files/apt-get.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1448917 Title: apt-get -o quiet=1 dist-upgrade isn't quiet anymore Status in apt package in Ubuntu: New Bug description: Description: Ubuntu 15.04 Release: 15.04 apt: Installed: 1.0.9.7ubuntu4 Candidate: 1.0.9.7ubuntu4 Version table: *** 1.0.9.7ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Current: Until updating from Utopic to Vivid apt-get with command line parameter -o quiet 1 did not output the progress as formatted text. Since the update the progress is written to stdout as formatted text. This breaks a lot of scripts, e.g. the cron-apt package with mail send enabled. The attached text is no longer text only and will be encoded as binary, so the mail is unreadable. Expected: Same behaviour as with version from Utopic, no progress output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1448917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot
Same here with an 14.10 AMD64 installation on a KVM machine. The workaround with mount -a in rc.local doesn't help much for daemons that need the mounted NFS share at startup. They're failing when the mount isn't present at boot time. I've stopped further deployment of Utopic until this bug has been fixed. It is really a showstopper and needs a fix very soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1384502 Title: fstab entry for nfs /home fails to mount on boot Status in “mountall” package in Ubuntu: Triaged Bug description: i'm uncertain exactly when this issue started as we use cfengine (verifies all expected mounts in place, manually mounts those that are not). from a note i have i believe it goes back as far as lucid. the symptom is that an /etc/fstab entry for an nfs-mounted /home is not mounted during the system boot. once the system is network- accessible, manually running `mount -tnfs -av` as root (or using cfengine or any number of other solutions) is sufficient. per lp#836533 i added --verbose to /etc/init/mountall.conf and will attach the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the smoking gun appears to be: mount.nfs: Failed to resolve server nfs-home: Temporary failure in name resolution ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: mountall 2.53 ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8 Uname: Linux 3.13.0-38.65-generic x86_64 .run.mount.utab: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 16:35:47 2014 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf nomdmonisw bootdegraded=true SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1384502/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
