[Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
For me this was due to my panel no longer having an indicator applet. Adding it back did not work. I managed to "fix" it by resetting the panel config (right click on the panel, select 'Reset Panel'). That got me an indicator appled, with the nm-appled being displayed correctly. (I do get an error message once on each login about the applet crashing, but clicking reload works. That should probably should be a separate bug.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714803] [NEW] Search list in resolv.conf breaks resolving for that domain
Public bug reported: Ubuntu 17.04 systemd 232-21ubuntu5 Adding a domain to the search list in /etc/resolv.conf breaks resolving for that domain. Not only does the search list not get used as expected, but host names in the domain cannot be resolved by systemd-resolved at all. I just ran into this after upgrading from ubuntu 16.04 to 17.04 which enabled systemd-resolved. I have for a long time used resolveconf to add a 'search my-domain'-line to my /etc/resolv.conf. Example of expected behaviour. With Googles DNS server (8.8.8.8) and ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve can resolve www.ubuntu.com and www: $ cat /etc/resolv.conf nameserver 8.8.8.8 search ubuntu.com $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 501 IN A 91.189.89.115 $ dig +search +nostat +nocmd www ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 382 IN A 91.189.89.103 $ systemd-resolve www.ubuntu.com www.ubuntu.com: 91.189.89.115 -- Information acquired via protocol DNS in 2.7ms. -- Data is authenticated: no $ systemd-resolve www www: 91.189.90.59 (www.ubuntu.com) -- Information acquired via protocol DNS in 3.8ms. -- Data is authenticated: no Ubuntu 17.04 default config, with the systemd-resolved name server in /etc/resolv.conf and no search list. www.ubuntu.com can still be resolved correctly: $ cat /etc/resolv.conf nameserver 127.0.0.53 $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 482 IN A 91.189.89.110 $ systemd-resolve www.ubuntu.com www.ubuntu.com: 91.189.90.58 -- Information acquired via protocol DNS in 18.2ms. -- Data is authenticated: no Broken behaviour, using the systemd-resolved name server and specify ubuntu.com in search list. Resolving fails for www.ubuntu.com and www, both using dig (DNS) and using sytemd-resolve: $ cat /etc/resolv.conf nameserver 127.0.0.53 search ubuntu.com $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A $ dig +search +nostat +nocmd www ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A $ systemd-resolve www.ubuntu.com www.ubuntu.com: resolve call failed: No appropriate name servers or networks for name found $ systemd-resolve www www: resolve call failed: All attempts to contact name servers or networks failed ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714803 Title: Search list in resolv.conf breaks resolving for that domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307627] Re: Error wiping USB stick: UDisks2.Error.Failed: Error synchronizing after initial wipe: Timed out waiting for object
*** This bug is a duplicate of bug 1294877 *** https://bugs.launchpad.net/bugs/1294877 I think this is a duplicate of 1059872 , not 1294877. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307627 Title: Error wiping USB stick: UDisks2.Error.Failed: Error synchronizing after initial wipe: Timed out waiting for object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1307627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376966] Re: gpu-manager treats all files in /etc/modprobe.d as config files
Oh, I didn't even think of that. Since the regexp don't begin with a ^, of course it also matches comments. :-( If I was not clear about versions in the original report. This is a regression introduced in the SRU ubuntu-drivers-common 1:0.2.91.7, in Ubuntu 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376966 Title: gpu-manager treats all files in /etc/modprobe.d as config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376966] Re: gpu-manager treats all files in /etc/modprobe.d as config files
Attached patch solve both issues. ** Patch added: 1376966_fix_regex_and_only_look_in_conf_files.patch https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+attachment/4238515/+files/1376966_fix_regex_and_only_look_in_conf_files.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376966 Title: gpu-manager treats all files in /etc/modprobe.d as config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374871] Re: upgrade from 0.2.91.6 to 0.2.91.7 breaks my X.org (nvidia)
That is the cause. With the changes in 0.2.91.7 gpu-manager will find the blacklist entries in bumblebee.conf and not load the nvidia module. However, bumblebee appears to be for supporting laptops with NVIDIA Optimus. From a very quick look at the description disabling the nvidia module seems like it could be by design. Are you using bumblebee? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374871 Title: upgrade from 0.2.91.6 to 0.2.91.7 breaks my X.org (nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1374871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373968] Re: GUI does not work after update
Why is this bug against ubuntu-drivers-common then? Since downgrading it didn't help, and your description mentions installing various updates, the problems could be caused by any of them right? You can find out what packages was upgraded when by looking in dpkg log files: /var/log/dpkg.log*. Then you could downgrade the packages. If your system then works again, you would then install one upgrade at a time, to find out what package breaks your system again. This might not be the easiest way to troubleshoot your issues, but it is probably what I would do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376966] [NEW] gpu-manager treats all files in /etc/modprobe.d as config files
Public bug reported: My media center computer have a single nvidia GPU connected to a TV, and have for many years been happily using the nvidia driver. Unfortunately the recent upgrade to version 1:0.2.91.7 broke X. Starting lightdm would fail, delete my xorg.conf and redirect libgl symlinks to mesa. After some debugging I fond that this was done by gpu-manager, because it incorrectly believes that my nvidia module is blacklisted. gpu- manager.log contained Is nvidia blacklisted? yes. More debugging determined that this was happening because I have a several years old file named: /etc/modprobe.d/blacklist.dpkg-old which among other things contain the line blacklist nvidia. However that is _not_ a modprobe config file. modprobe only uses files with a .conf extension. (See the man page modprobe.d(5)). Unfortunately gpu-manager does not have this restriction and looks in all files in /etc/modprobe.d by running: grep -G blacklist.*nvidia[[:space:]]*$ /etc/modprobe.d/* I could work-around the bug by removing the .dpkg-old file. However this will likely break other machines as well. I found two bugs 1373968 and 1374871 about X not working after installing the latest update. However they does not contain enough information to determine if they are duplicates of this bug or not. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376966 Title: gpu-manager treats all files in /etc/modprobe.d as config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1376966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374871] Re: upgrade from 0.2.91.6 to 0.2.91.7 breaks my X.org (nvidia)
Do you have any files in /etc/modprobe.d/ that does not have a .conf extension? If you have, then this could be a duplicate of bug 1376966. Run the following to check: ls /etc/modprobe.d/|grep -v '\.conf$' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374871 Title: upgrade from 0.2.91.6 to 0.2.91.7 breaks my X.org (nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1374871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373968] Re: GUI does not work after update
Do you have any files in /etc/modprobe.d/ that does not have a .conf extension? If you have, then this could be a duplicate of bug 1376966. Log in to the root console, and run the following to check: ls /etc/modprobe.d/|grep -v '\.conf$' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373968 Title: GUI does not work after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1373968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy
After upgrading to saucy my system was unbootable due to this bug. initramfs-tools 0.103ubuntu1.1 fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238194 Title: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy
Why is this bug listed as affecting Precise? I don't see any comments in this bug, or any of the duplicates, that mentions anything other than hitting this after installing or upgrading to saucy. I certainly did not have this bug in precise which I was running until a few weeks ago. I then upgraded to quantal, then to raring and finally to saucy and only got this bug on saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238194 Title: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
