[Bug 1749393] Re: sbrk() not working under qemu-user with a PIE-compiled binary?
I'm running qemu-arm version 4.2.1 (Debian 1:4.2-3ubuntu6.17) on Ubuntu 20.04.03, but I seem to still be affected by this (or something very much like it). In my case it is armhf exim4 crashing while creating a chroot on an amd64 host. The final command run from deeply within exim4's postinst is: /usr/sbin/exim4 -C /var/lib/exim4/config.autogenerated.tmp -bV and produces Exim version 4.93 #5 built 28-Apr-2021 13:19:17 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC Event I18N OCSP PRDR SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) Interestingly, even /usr/sbin/exim4 -C /dev/null -bV produces the same result, so it likely doesn't depend on any configuration at my end and should be reproducible. Please let me know if there is anything I can do to help debug further. Should I create a separate ticket? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749393 Title: sbrk() not working under qemu-user with a PIE-compiled binary? To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1749393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300211] Re: Can't install both gcc-multilib and gcc-arm-linux-gnueabihf
Actually, I was wrong about arm-linux-gnueabihf-gcc! It *also* doesn't find /usr/include/asm, instead correctly finding /usr/arm-linux- gnueabihf/include/asm! So actually, as far as I can tell *nothing* uses /usr/include/asm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300211 Title: Can't install both gcc-multilib and gcc-arm-linux-gnueabihf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1300211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300211] Re: Can't install both gcc-multilib and gcc-arm-linux-gnueabihf
Can someone please explain why /usr/include/asm is needed? It seems to me neither gcc -m32 nor gcc -m64 use it (both finding the ones in /usr/include/i386-linux-gnu and /usr/include/x86_64-linux-gnu instead). arm-linux-gnueabihf-gcc finds it which is not correct, but can be fixed easily enough by sym-linking /usr/include/arm-linux-gnueabihf to /usr/arm-linux-gnueabihf/include. From what I can see, the only things ever finding /usr/include/asm are things which should definitely not be using it (cross compilers). If that is correct, removing that symlink from gcc-multilib should not break anything that's not already broken. And with it removed, the conflicts would no longer be necessary. What am I missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300211 Title: Can't install both gcc-multilib and gcc-arm-linux-gnueabihf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1300211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
In fact, I can confirm that hirsute package cleanly installs in focal and (almost) fixes the issue. Almost because the Address is set to the string "172.25.117.104 (DHCP4)" which is not very useful. Expecting scripts to parse that string and take it apart makes a farce of passing all that information in JSON format in the first place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
Any idea whether this fix can be back-ported to focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772137] Re: networkd-dispatcher starts too late to take effect on boot
Never mind. The scripts were in the wrong directory. /lib instead of /usr/lib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772137 Title: networkd-dispatcher starts too late to take effect on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772137] Re: networkd-dispatcher starts too late to take effect on boot
It appears this has been "unfixed" in focal? root@ttde-kvm6:~# systemctl cat networkd-dispatcher.service # /lib/systemd/system/networkd-dispatcher.service [Unit] Description=Dispatcher daemon for systemd-networkd [Service] Type=notify ExecStart=/usr/bin/networkd-dispatcher $networkd_dispatcher_args # Load /etc/default/networkd-dispatcher EnvironmentFile=-/etc/default/%p [Install] WantedBy=multi-user.target And dispatcher does not run scripts on start-up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772137 Title: networkd-dispatcher starts too late to take effect on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1772137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
Any idea whether this fix can be back-ported to focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
Oh, that's good news. Let us know when it is uploaded and I give it a spin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] Re: smbclient ignores included config files
They were not. Adding a [global] before each include (since sections opened in an include file stay open in the parent) makes them work as expected! Thanks so much Christian for your work on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] Re: smbclient ignores included config files
LOL, I would call that a bit more than "suspicious". More like a smoking gun?! Thanks for putting time into this Christian. Does this bring us any closer to fixing it? Does it need to be raised upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] Re: smbclient ignores included config files
Ok, after a few starting hiccups, I managed to get our management system to support groovy and install a VM. I have only tested the behaviour of the workgroup setting with smbclient -L localhost since it does not rely on any external servers etc. I can confirm that the behaviour is unchanged in groovy (samba version 2:4.12.5+dfsg-3ubuntu3). I.e. the workgroup setting is ignored in the included file but works in the top-level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] Re: smbclient ignores included config files
@Paride: Good catch. The second file's contents are: # Global ttde samba config. Do not edit. [global] workgroup = TEL include=/etc/samba/dhcp.conf encrypt passwords = true # ICT don't like us to rebroadcast printers all over the shop load printers=no show add printer wizard=no disable spools=yes client min protocol = NT1 [Home] comment = /home on %h path = /home writeable = yes However, connecting with smbclient -L localhost asks for WORKGROUP\seb's password not TEL\seb's. So it's definitely not just the client min protocol. However, the above command *does* list the home share. So its also not the entire file that is being ignored. I'd also like to point out that I'm not sure this is a new issue! I only noticed it when I tried to put in the client min protocol which is needed since 20.04. @Christian: I'll try, but that will take a moment longer since I have not yet set our management system up for Groovy since we typically stay with the LTSs and I haven't even managed to get us onto 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] Re: smbclient ignores included config files
I have tried including [global] client min protocol = NT1 in the top-level file both before and after all the includes. In all cases it worked. This seems to indicate that a section can be re-opened and the problem is likely in the include mechanism itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893906] [NEW] smbclient ignores included config files
Public bug reported: Hi, since upgrading to Ubuntu 20.04 I cannot gio mount or otherwise connect to my companies' samba shares due to them requiring the NT1 protocol. Adding client min protocol = NT1 to ~/.smb/smb.conf works, but I need to deploy this to a largish number of managed machines. The file /etc/samba/smb.conf on these machines looks like this: include = /usr/share/samba/smb.conf include = /usr/share/tait-config/ttde-smb.conf include = /etc/samba/user.conf where /usr/share/samba/smb.conf is the config template shipped with samba itself, /usr/share/tait-config/ttde-smb.conf contains config overrides that are deployed via a locally built and hosted config package (the file itself is not a dpkg config file so will get silently rewritten when we update the package) and finally, individual machines' users can customise the config in /etc/samba/user.conf. Unfortunately adding client min protocol = NT1 only works in the first included file but not the second where we really need this to go. It seems that there is a bug in the included config file parser somewhere. ubuntu-bug requested me to include this information though I'm not sure how relevant it is: seb@eragon:~/Documents/work/Terminals[0]$ smbclient -L localhost Enter WORKGROUP\seb's password: Sharename Type Comment - --- print$ Disk Printer Drivers HomeDisk /home on eragon IPC$IPC IPC Service (eragon server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. smbXcli_negprot_smb1_done: No compatible protocol selected by server. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Unable to connect with SMB1 -- no workgroup available ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: smbclient 2:4.11.6+dfsg-0ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 19:24:03 2020 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893906 Title: smbclient ignores included config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1893906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880305] Re: Failed to mount Windows share: Software caused connection abort
I should clarify that it works when I put it in the [global] section in /usr/share/samba/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880305 Title: Failed to mount Windows share: Software caused connection abort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880305] Re: Failed to mount Windows share: Software caused connection abort
I tried to apply the work-around given here (min client protocol), but am having trouble. It works if I put it into ~/.smb/smb.conf or /etc/samba/smb.conf. However, for various reasons neither file is really appropriate in my case. Instead, I would like to add it to a file that is included from /etc/samba/smb.conf. My /etc/samba/smb.conf looks like this: include = /usr/share/samba/smb.conf include = /usr/share/tait-config/ttde-smb.conf include = /etc/samba/user.conf If I include the work-around in the [global] section in /usr/share/tait- config/ttde-smb.conf, it is being ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880305 Title: Failed to mount Windows share: Software caused connection abort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
Looks like the secondary problem is here is the same as https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
So does this silence mean people have tried to reproduce this but couldn't or that they could and are working on it or that nobody has tried? I would have thought this kind of corruption is hinting at a possibility of there being some possibility that this could be exploited and get a bit more "interest". It is 100% reproducible for me, so if there's anything I can do to help debug this, please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: networkd-dispatcher gives corrupted information
Ok, it looks like the networkd crash & error message about enslaving a bridge to a bridge was caused by the fact that the network file for one of the bridge ports had a Match on MACAddress and came before the bridge's own network file. Therefore, on restarting networkd matched the port network file to the bridge itself (which had inherited that ports mac address) and hence tried to enslave the bridge to itself with obviously bad consequences. It did not used to do that on Eoan, but changing the ports Match section to match on the interface's name means I can now restart networkd without it crashing (and without me loosing comms). However, the dispatcher json is still just as mangled as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] [NEW] networkd-dispatcher gives corrupted information
Public bug reported:
I just reinstalled my RPI3 router from Eoan to Focal but a lot of things
about networkd broke. I'm not sure whether they are related or not.
The first thing I noticed was, that I did not get my upstream DNS
servers. I use a dispatcher script to extract the information from the
json environment variable when my uplink becomes routable. Using a test
script to dump the environment I found this:
IP6_ADDRS=
PWD=/
json={"A": ["ress: 119.224.106.22 (DHCP4)"], "AdministrativeState":
"configuring", "Auto negot": ["tion: yes", "peed: 100Mbps", "plex: full",
"Port: mii"], "G": ["eway: 119.224.106.21", "DNS: 202.180.64.10",
"202.180.64.11", ""], "HW A": ["ress: b8:27:eb:b6:a5:f4 (Raspberry Pi
Foundation)", "MTU: 1500 (max: 65535)"], "InterfaceName": "wan", "Jun 20
00:01:49": ["mnus systemd-networkd[534]: wan: netdev ready", "mnus
systemd-networkd[534]: wan: Link UP", "mnus systemd-networkd[534]: wan: Gained
carrier"], "Jun 20 00:01:50": ["mnus systemd-networkd[534]: wan: Lost
carrier"], "Jun 20 00:01:51": ["mnus systemd-networkd[534]: wan: Gained
carrier"], "Jun 20 00:01:53": ["mnus systemd-networkd[534]: wan: DHCPv4 address
119.224.106.22/30 via 119.224.106.21"], "Lin": ["File:
/usr/lib/systemd/network/99-default.link"], "Networ": ["File:
/etc/systemd/network/07-wan.network", "Type: vlan", "tate: routable
(configured)", "iver: 802.1Q VLAN Support"], "OperationalState": "routable",
"Queue Length (": ["/Rx): 1/1"], "State": "routable (configuring)", "Type":
"vlan"}
AdministrativeState=configuring
IFACE=wan
LANG=en_NZ.UTF-8
INVOCATION_ID=384cc7de4e8d45e48ecb2ecf3cb55508
IP_ADDRS=
ESSID=
ADDR=
NOTIFY_SOCKET=/run/systemd/notify
SHLVL=1
STATE=routable
JOURNAL_STREAM=9:35403
OperationalState=routable
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
networkd_dispatcher_args=--run-startup-triggers
Note that the script worked perfectly fine on Eoan.
Also when I tried to get the dump above, I ran the following command after
installing the test-script:
ip link delete wan type vlan; systemctl restart systemd-networkd
in order to force networkd to recreate and reconfigure my uplink interface.
Doing this resulted in all connectivity with the router being lost (up- and
downstream). After a restart, I found the following in the networkd journal
indicating that networkd had in fact crashed.
Jun 19 23:59:58 tumnus systemd-networkd[539]: wan: Link DOWN
Jun 19 23:59:58 tumnus systemd-networkd[539]: wan: Lost carrier
Jun 19 23:59:58 tumnus systemd-networkd[539]: wan: DHCP lease lost
Jun 19 23:59:58 tumnus systemd[1]: Stopping Network Service...
Jun 19 23:59:58 tumnus systemd[1]: systemd-networkd.service: Succeeded.
Jun 19 23:59:58 tumnus systemd[1]: Stopped Network Service.
Jun 19 23:59:58 tumnus systemd[1]: Starting Network Service...
Jun 19 23:59:59 tumnus systemd-networkd[1986]: private: netdev ready
Jun 19 23:59:59 tumnus systemd-networkd[1986]: Enumeration completed
Jun 19 23:59:59 tumnus systemd[1]: Started Network Service.
Jun 19 23:59:59 tumnus systemd-networkd[1986]: private: netdev exists, using
existing without changing its parameters
Jun 20 00:00:00 tumnus systemd[1]: systemd-networkd.service: Main process
exited, code=dumped, status=11/SEGV
Jun 20 00:00:00 tumnus systemd[1]: systemd-networkd.service: Failed with result
'core-dump'.
Jun 20 00:00:00 tumnus systemd[1]: systemd-networkd.service: Scheduled restart
job, restart counter is at 1.
Jun 20 00:00:00 tumnus systemd[1]: Stopped Network Service.
Jun 20 00:00:00 tumnus systemd[1]: Starting Network Service...
Jun 20 00:00:01 tumnus systemd-networkd[2034]: private: netdev ready
Jun 20 00:00:01 tumnus systemd-networkd[2034]: Enumeration completed
Jun 20 00:00:01 tumnus systemd[1]: Started Network Service.
Jun 20 00:00:01 tumnus systemd-networkd[2034]: private: netdev exists, using
existing without changing its parameters
Jun 20 00:00:01 tumnus systemd-networkd[2034]: wan: Link UP
Jun 20 00:00:01 tumnus systemd-networkd[2034]: wan: Gained carrier
Jun 20 00:00:01 tumnus systemd-networkd[2034]: private: Could not join netdev:
Can not enslave a bridge to a bridge. Too many levels of symbolic links
Jun 20 00:00:01 tumnus systemd-networkd[2034]: private: Failed
Jun 20 00:00:01 tumnus systemd-networkd[2034]: wan: DHCPv4 address
119.224.106.22/30 via 119.224.106.21
Jun 20 00:01:22 tumnus systemd[1]: Stopping Network Service...
Jun 20 00:01:22 tumnus systemd-networkd[2034]: wan: DHCP lease lost
Jun 20 00:01:22 tumnus systemd[1]: systemd-networkd.service: Succeeded.
Jun 20 00:01:22 tumnus systemd[1]: Stopped Network Service.
-- Reboot --
However, no crash file had been generated.
The system is running systemd 245.4-4ubuntu3.1 and networkd-dispatcher 2.0.1-1.
** Affects: networkd-dispatcher (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/1884248
Title:
[Bug 1879559] Re: net/bpfilter: remove superfluous testing message
Same issue on Raspberry PI running Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879559 Title: net/bpfilter: remove superfluous testing message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Ok, this is interesting. I just downgraded to bionic (18.04) and now the dongle is working! So something went wrong somewhere along the way but the H/W is definitely good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875298] [NEW] Focal Fossa is missing libfakechroot:i386 package
Public bug reported: The title kind of says it all. libfakechroot:amd64 is the same version in 20.04 as it was in 19.10, but libfakechroot:i386 is missing from the repo. ** Affects: fakechroot (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/1875298 Title: Focal Fossa is missing libfakechroot:i386 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fakechroot/+bug/1875298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840941] Re: kdump fails to start with secure boot enabled
BUT, if I manually download the versions that do work together from the PPA, then kexec works! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840941 Title: kdump fails to start with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1840941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840941] Re: kdump fails to start with secure boot enabled
And the PPA mentioned above now holds a set of packages with broken dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840941 Title: kdump fails to start with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1840941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840941] Re: kdump fails to start with secure boot enabled
Still an issue with 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840941 Title: kdump fails to start with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1840941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Ok, I tried again but changed the command with the version above to: make SUBLEVEL=0 EXTRAVERSION=-46-generic modules_prepare Now I get in dmesg: [ 7851.540982] usb 10-1: new full-speed USB device number 4 using xhci_hcd [ 7851.788016] usb 10-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 [ 7851.788022] usb 10-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 7851.788026] usb 10-1: Product: CSR8510 A10 [ 7851.802391] usbcore: registered new interface driver btusb [ 7851.963660] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7851.963662] Bluetooth: BNEP filters: protocol multicast [ 7851.963667] Bluetooth: BNEP socket layer initialized [ 7853.817073] Bluetooth: hci0: command 0x1001 tx timeout [ 7861.977389] Bluetooth: hci0: CSR: Local version failed (-110) seb@eragon:~/btDongleTest/linux-source-5.3.0[0]$ hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 seb@eragon:~/btDongleTest/linux-source-5.3.0[1]$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) Otherwise behaviour is unchanged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Here are the steps I followed (all on Eoan):
sudo apt install kernel-package linux-source flex bison libssl-dev libelf-dev
tar xf /usr/src/linux-source-5.3.0.tar.bz2
cd linux-source-5.3.0
make mrproper
cp /usr/lib/modules/5.3.0-46-generic/build/{.config,Module.symvers} .
make oldconfig
patch -p1 < ../btusb-Enablement-of-HCI_QUIRK_BROKEN_STORED_LINK_KEY-quirk.patch
make EXTRAVERSION=-ubuntu1-1 modules_prepare
make M=drivers/bluetooth
xz drivers/bluetooth/btusb.ko
sudo cp -f drivers/bluetooth/btusb.ko.xz
/usr/lib/modules/5.3.0-46-generic/updates
sudo depmod
sudo modprobe -r btusb
Now when I insert the dongle, I get
[ 4831.984499] btusb: version magic '5.3.18-ubuntu1-1 SMP mod_unload ' should
be '5.3.0-46-generic SMP mod_unload '
Obviously, the EXTRAVERSION isn't right yet, but why is that module
reporting itself as 5.3.18 when I built it from 5.3.0 source?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873718
Title:
CSR8510 based BTA-402 Bluetooth device cannot be started
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Gave it another try with linux-image-unsigned-5.7.0-999-generic on Eoan, same behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Sorry for the delay. I have just installed 20.04 to try but the behaviour is the same. Dmesg log when I plug in the dongle: [ 230.119651] usb 10-1: new full-speed USB device number 3 using xhci_hcd [ 230.375357] usb 10-1: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=88.91 [ 230.375362] usb 10-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 230.375365] usb 10-1: Product: CSR8510 A10 [ 230.479445] Bluetooth: Core ver 2.22 [ 230.479465] NET: Registered protocol family 31 [ 230.479466] Bluetooth: HCI device and connection manager initialized [ 230.479470] Bluetooth: HCI socket layer initialized [ 230.479472] Bluetooth: L2CAP socket layer initialized [ 230.479475] Bluetooth: SCO socket layer initialized [ 230.504741] usbcore: registered new interface driver btusb [ 230.672496] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 230.672497] Bluetooth: BNEP filters: protocol multicast [ 230.672501] Bluetooth: BNEP socket layer initialized In the settings screen for BT it shows "BT Turned Off". When flip the switch nothing happens. seb@eragon:~[0]$ hciconfig hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 seb@eragon:~[1]$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873718] [NEW] CSR8510 based BTA-402 Bluetooth device cannot be started
Public bug reported: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873716] [NEW] Information on how to report a bug is incorrect
Public bug reported: I'm trying to report a bug about my Bluetooth dongle. I googled and was directed to https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html.en for direction on how to do so. I followed the instructions on that page, but they do not work: 1. I run ubuntu-bug without arguments since I don't know which program to report against. 2. A menu shows up asking me what kind of problem I would like to report. 3. I choose the only vaguely matching option "Other Problem" 4. ubuntu-bug aborts with an error message that I need to choose a package. There was nothing in the instructions about a package and in any case (while I can guess I should maybe report it against bluez), most people wouldn't know which package to choose anymore than what program is involved. Another menu entry for "hardware" or something of the sort would be useful. ** Affects: ubuntu-docs (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/1873716 Title: Information on how to report a bug is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1873716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599459] Re: cannot bootstrap from repositories without InRelease files when --debian-installer set
It looks as though this has been fixed in Ubuntu somewhere between Bionic and Eoan. Shouldn't this bug be updated accordingly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599459 Title: cannot bootstrap from repositories without InRelease files when --debian-installer set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1599459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565448] Re: [needs-packaging] User-mode-linux package missing in Ubuntu
It seems it never made it from bionic-proposed to bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565448 Title: [needs-packaging] User-mode-linux package missing in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/user-mode-linux/+bug/1565448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801643] Re: msiextract corrupts it's output
Any chance to have this fixed in Bionic? ** Also affects: gcab (Ubuntu) Importance: Undecided Status: New ** No longer affects: gcab (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801643 Title: msiextract corrupts it's output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msitools/+bug/1801643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801643] Re: msiextract corrupts it's output
I tried to add gcab (to point out that the bug is, apparently, in libgcab) for bionic, but I can't seem to select a particular release as a target. So I removed it again since it probably didn't add any new information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801643 Title: msiextract corrupts it's output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/msitools/+bug/1801643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791200] [NEW] grub-pc does not allow preseeding install_devices
Public bug reported: Background: Upon configuration the postinst maintainer script checks to see whether it needs to convert the debconf variable install_devices from the old device name format to the new 'by-id' format. It bases this decision on a version comparison against the "previously installed". In a new installation, this comparison is successful since the empty version string is older than any other version. postinst then goes on to check a few special cases where it can make informed decisions on whether the conversion was good without involving the user. Failing those checks it forces the debconf question to be presented to the user again with the converted device ids for confirmation. Problem: If an administrator has preseeded the install_devices question (using the new 'by-id' format) before installing grub-pc, then the above algorithm incorrectly decides that the user needs to confirm the devices again. Solution: The attached patch adds another special case that checks if the device IDs where already in the new 'by-id' format and in that case accepts them without asking the user again. Versions: I have observed this bug for many years, but only now gotten around to tracking it to its source. The patch is against version 2.02-2ubuntu8.4 of grub-pc. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Patch added: "patch against version 2.02-2ubuntu8.4 of grub-pc" https://bugs.launchpad.net/bugs/1791200/+attachment/5185869/+files/grub-pc.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791200 Title: grub-pc does not allow preseeding install_devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1791200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776818] Re: [MIR] vde2
Is it really this hard to get 885 lines of code promoted into main? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776818 Title: [MIR] vde2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vde2/+bug/776818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699110] Re: nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build
I just logged into my system, the update-manager popped up and said there where a number of updates. When I told it to install them it went ahead, but in the middle of the update it reported that Ubuntu had experienced a problem (the update went on though) and when I reported it it offered me a largish number of issues that might be duplicates. I chose this one because it had the exact same subject line as the bug report generated for me. I searched under /var/lib/dkms/ and there where no files named DKMSBuildLog.txt there. However, the was /var/lib/dkms/nvidia-375/375.66/4.4.0-83-generic/x86_64/log/make.log with a timestamp matching approximately when the error occurred. However, it didn't appear to have any errors in it. /var/log/apt/term.log was slightly more interesting. It had the following in it: Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Error! Bad return status for module build on kernel: 4.4.0-83-generic (x86_64) Consult /var/lib/dkms/nvidia-375/375.66/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that theme. W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic I'll attach it as well. The log file mentioned (/var/lib/dkms/nvidia-375/375.66/build/make.log) however, does not exist. ** Attachment added: "apt log of the update that I believe caused the issue." https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1699110/+attachment/4907234/+files/term.log ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699110 Title: nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1699110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Also observed with 4.4.0-1054-raspi2. I'm now back on 4.4.0-1038-raspi2. I think that one was ok. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647298] Re: kexec does not appear to work
Can somebody at least comment on whether this is expected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647298 Title: kexec does not appear to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1647298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin
For every-body who has this issue, the following command works around it until the package maintainers find a solution: sudo dpkg-divert --divert /lib/firmware/brcm/brcmfmac43430-sdio-2.bin --package linux-firmware-raspi2 --rename --add /lib/firmware/brcm/brcmfmac43430-sdio.bin Please note that this will set up a diversion for the conflicting file in your system and may have to be un-done once a permanent solution is found. If the chosen solution is to remove the file from linux-firmware and leave it in linux-firmware-raspi2, then the file /lib/firmware/brcm/brcmfmac43430-sdio.bin will end up missing in your system. In this case you can remove the diversion by replacing --add with --remove in the above command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691729 Title: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
linux-raspi2 version 4.4.0.1055.56 that is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
This is still an issue in the current linux-raspi2 version. Where those changes ported to that kernel? ** Also affects: linux-raspi2 (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/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin
Actually it wasn't stuck. It has now tried to install 1.157.10 and failed as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691729 Title: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
I went ahead and raised a separate issue (1691729) in any case, just to be sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691729] [NEW] linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin
Public bug reported: I just tried to do a fresh install of xenial on a raspberry pi (I'm not using a pre-made image but rather create a full install from scratch using debootstrap etc) and it failed because it couldn't install linux- firmware-raspi2 (1.20161020-0ubuntu1~0.2~rpi3) because the file /lib/firmware/brcm/brcmfmac43430-sdio.bin was already owned by linux- firmware 1.157.10. This caused me to go back to my already installed and running RPI and sure enough, it was stuck on linux-firmware 1.157.8. linux-firmware-raspi2 should probably not include this file if it already is in linux-firmware. Alternatively it should use dpkg-divert to divert linux-firmware's version of the file out of the way. ** Affects: linux-firmware-raspi2 (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/1691729 Title: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578745] Re: Update firmware for Raspberry Pi 3 support
I'm not sure whether this is the right place for this, but I just tried to do a fresh install of xenial on a raspberry pi (I'm not using a pre- made image but rather create a full install from scratch using debootstrap etc) and it failed because it couldn't install linux- firmware-raspi2 (1.20161020-0ubuntu1~0.2~rpi3) because the file /lib/firmware/brcm/brcmfmac43430-sdio.bin was already owned by linux- firmware 1.157.10. This caused me to go back to my already installed and running RPI and sure enough, it was stuck on linux-firmware 1.157.8. Is this the right place to comment or do I need to raise a new issue for this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578745 Title: Update firmware for Raspberry Pi 3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1578745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Thanks Andy, that makes sense. I'm not aware of any other hooks having problems. I have also neither checked apt-auto-remove nor noticed the issue recently. So I'll take you word for it that the hook itself has been fixed in which case we can close this one as Not-A-Bug or whatever seems appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Why doesn't linux-image-extra's postrm simply run update-initramfs. That seems the more sensible thing to do as it is the same as with any other package that wants to put things into the initrd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599459] Re: cannot bootstrap from repositories without InRelease files when --debian-installer set
I'm also affected by this. The attached patch fixes the problem using only posix shell mechanisms. Please note that the paths in the diff are absolute to patch the problem in-system. ** Patch added: "functions.diff" https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1599459/+attachment/4873850/+files/functions.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599459 Title: cannot bootstrap from repositories without InRelease files when --debian-installer set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1599459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602536] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives
I believe this happens because unattended-upgrades gets and releases the lock a couple times (such as between installing upgrades and then removing now no longer required automatically installed packages) and dies if it cannot re-aquire the lock (rather than gracefully handling it). The high frequency is easily explained since apt-daily runs both unattended-upgrades and aptd (via dbus triggers both from Update-Post- Invoke-Success (or whatever it was called) and directly from the apt- daily script) and this sets up a race with a fairly high chance of hitting unattended-upgrades somewhere where it hurts. Even when it does not lead to a crash it often causes upgrades not to be installed. This can be seen by setting APT::Periodic::Verbose to 3 and monitoring the logs. Often one or another of the steps of apt-daily will fail because it could not acquire the lock. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602536 Title: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin /unattended- upgrade@1468:main:do_auto_remove:cache_commit:commit:_fetch_archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1602536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] Re: Resolver ignores ndots option
Interesting. At the very least then the man page is inconsistent since >From man resolv.conf, search option: Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. However, I believe the subsequent query with the search-list appended is simply bad no matter whether it corresponds to the man page or not. The problem is, that the second lookup may actually return a result that is bad (namely when one of the searched domains has a wildcard) and that then gets cached. When I connect to a VPN later, the first entry isn't even tried again since we hold a cached result. As far as I can tell, the ndots option is the resolvers way of figuring out whether a name is absolute or relative given that host names don't usually have the trailing period to indicate that they are FQDNs. So, I think, it should EITHER use the search list or not depending on ndots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841173/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841175/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841174/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841176/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841169/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841172/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841168/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841167/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841170/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841171/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841166/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] Re: Resolver ignores ndots option
apport information ** Tags added: apport-collected xenial ** Description changed: This is a re-report of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that one was apparently closed as no-fix simply because it was too old. This still occurs in xenial. Original description: Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned from the DNS server then resolver always try another attempt with the original name extended by what is in search option. For example, if you're looking for very.long.url.nowhere and there is a line "search ubuntu.com" in resolv.conf you will get addres of server very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should occurs only for urls having less that ndots option dots in its name. My system is a standard Ubuntu Xenial desktop amd64 using network manager and the default configured Wired Connection 1 (i.e. DHCP). To reproduce: - sudo install /dev/fd/0 /etc/NetworkManager/dnsmasq.d/domain <<<'log-queries=extra' - sudo killall dnsmasq - ping some.long.non-existent.name - Watch /var/log/syslog In my case: Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 query[A] some.long.non-existent.name from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 forwarded some.long.non-existent.name to 192.168.5.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 reply some.long.non-existent.name is NXDOMAIN Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 query[A] some.long.non-existent.name.sebunger.dnsalias.org from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 forwarded some.long.non-existent.name.sebunger.dnsalias.org to 192.168.5.1 Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply some.long.non-existent.name.sebunger.dnsalias.org is Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply sebunger.dnsalias.org is 203.173.156.30 My /etc/resolv.conf (which is a sym-link to ../run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 search sebunger.dnsalias.org options ndots:1 (I added the options ndots with no effect) + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + IwConfig: + enp2s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. GA-MA770-UD3 + NonfreeKernelModules: nvidia_uvm nvidia + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=/dev/mapper/vg0-root ro rootdelay=120 quiet splash + ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.4.0-66-generic N/A + linux-backports-modules-4.4.0-66-generic N/A + linux-firmware1.157.8 + RfKill: + + Tags: xenial xenial + Uname: Linux 4.4.0-66-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy kvm lpadmin plugdev sambashare ssh sudo users video + _MarkForUpload: True + dmi.bios.date: 06/12/2009 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: FB + dmi.board.name: GA-MA770-UD3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd06/12/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: GA-MA770-UD3 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1674273/+attachment/4841165/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] Re: Resolver ignores ndots option
I don't think this is a recent regression. I have seen the symptoms for a while and have only gotten around to investigating it yesterday. Also see the linked bug which describes exactly this issue and which was raised in 2009. However, I am inclined to believe that this is more a glibc rather than a kernel bug. In particular this is likely somewhere in libnss_dns.so, the DNS plugin to the NSS system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401202] Re: Resolver ignores ndots option
As requested, I have filed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/401202 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674273] [NEW] Resolver ignores ndots option
Public bug reported: This is a re-report of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/401202 since that one was apparently closed as no-fix simply because it was too old. This still occurs in xenial. Original description: Regardless of ndots option in /etc/resolv.conf, when NXDOMAIN is returned from the DNS server then resolver always try another attempt with the original name extended by what is in search option. For example, if you're looking for very.long.url.nowhere and there is a line "search ubuntu.com" in resolv.conf you will get addres of server very.long.url.nowhere.ubuntu.com if such exists. It is incorrect, it should occurs only for urls having less that ndots option dots in its name. My system is a standard Ubuntu Xenial desktop amd64 using network manager and the default configured Wired Connection 1 (i.e. DHCP). To reproduce: - sudo install /dev/fd/0 /etc/NetworkManager/dnsmasq.d/domain <<<'log-queries=extra' - sudo killall dnsmasq - ping some.long.non-existent.name - Watch /var/log/syslog In my case: Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 query[A] some.long.non-existent.name from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 forwarded some.long.non-existent.name to 192.168.5.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 46 127.0.0.1/40646 reply some.long.non-existent.name is NXDOMAIN Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 query[A] some.long.non-existent.name.sebunger.dnsalias.org from 127.0.0.1 Mar 20 23:19:22 eragon dnsmasq[27367]: 47 127.0.0.1/52417 forwarded some.long.non-existent.name.sebunger.dnsalias.org to 192.168.5.1 Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply some.long.non-existent.name.sebunger.dnsalias.org is Mar 20 23:19:23 eragon dnsmasq[27367]: 47 127.0.0.1/52417 reply sebunger.dnsalias.org is 203.173.156.30 My /etc/resolv.conf (which is a sym-link to ../run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 search sebunger.dnsalias.org options ndots:1 (I added the options ndots with no effect) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674273 Title: Resolver ignores ndots option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
As a note: I believe this also affects the armhf kernel 4.4.0-1040-raspi2 for the Raspberry Pi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661460] Re: appstream breaks installation as it is incompatible with gnome-software
In addition this problem causes already installed machines to REMOVE some packages on upgrade (when done using apt-get dist-upgrade) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661460 Title: appstream breaks installation as it is incompatible with gnome- software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1661460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661460] [NEW] appstream breaks installation as it is incompatible with gnome-software
Public bug reported: The latest xenial backports version of appstream has a breaks: gnome- software (<< 3.22.5-1) in its control file, but there is no version of gnome-software > 3.22 available in any xenial repos. This causes the installation process to break when backports are enabled. ** Affects: appstream (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/1661460 Title: appstream breaks installation as it is incompatible with gnome- software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1661460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661460] Re: appstream breaks installation as it is incompatible with gnome-software
Example excerpt of a debian installer log: Feb 3 00:31:15 pkgsel: starting tasksel Feb 3 00:31:19 in-target: debconf: unable to initialize frontend: Passthrough Feb 3 00:31:19 in-target: debconf: (Failed to open fd 3: Bad file descriptor at (eval 19) line 3.) Feb 3 00:31:19 in-target: debconf: falling back to frontend: Noninteractive Feb 3 00:31:19 in-target: ^MExtracting templates from packages: 35% Feb 3 00:31:19 in-target: ^MExtracting templates from packages: 70% Feb 3 00:31:19 in-target: ^MExtracting templates from packages: 100% Feb 3 00:32:23 in-target: Reading package lists... Feb 3 00:32:23 in-target: Feb 3 00:32:23 in-target: Building dependency tree... Feb 3 00:32:23 in-target: Feb 3 00:32:23 in-target: Reading state information... Feb 3 00:32:23 in-target: Feb 3 00:32:24 in-target: crda is already the newest version (3.13-1). ... Feb 3 00:32:25 in-target: xz-utils is already the newest version (5.1.1alpha+20120614-2ubuntu2). Feb 3 00:32:25 in-target: xz-utils set to manually installed. Feb 3 00:32:25 in-target: Some packages could not be installed. This may mean that you have Feb 3 00:32:25 in-target: requested an impossible situation or if you are using the unstable Feb 3 00:32:25 in-target: distribution that some required packages have not yet been created Feb 3 00:32:25 in-target: or been moved out of Incoming. Feb 3 00:32:25 in-target: The following information may help to resolve the situation: Feb 3 00:32:25 in-target: Feb 3 00:32:25 in-target: The following packages have unmet dependencies: Feb 3 00:32:25 in-target: appstream : Breaks: gnome-software (< 3.22.5-1) but 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 is to be installed Feb 3 00:32:25 in-target: E Feb 3 00:32:25 in-target: : Feb 3 00:32:25 in-target: Unable to correct problems, you have held broken packages. Feb 3 00:32:25 in-target: Feb 3 00:32:25 in-target: tasksel: apt-get failed (100) Feb 3 00:32:25 main-menu[3385]: WARNING **: Configuring 'pkgsel' failed with error code 1 Feb 3 00:32:25 main-menu[3385]: WARNING **: Menu item 'pkgsel' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661460 Title: appstream breaks installation as it is incompatible with gnome- software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1661460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647298] [NEW] kexec does not appear to work
Public bug reported: I have been using kexec for quite some time on desktop and server Ubuntu installations. Recently I've started using Raspberry Pi 3's for some of the server tasks. Unfortunately I can't seem to get kexec working. I have searched but found no mention of similar problems nor any indication that kexec is simply not supported on the RPI3 (or on ARM in general). My symptoms are that the kexec_load system call appears to return with EINVAL: root@media2:~# kexec /boot/vmlinuz-4.4.0-1029-raspi2 --initrd /boot/initrd.img-4.4.0-1029-raspi2 --command-line "$( LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647298 Title: kexec does not appear to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1647298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server
Honestly? I'm running (or trying to) Ubuntu server off of Raspberry Pis. I don't need or want LXD. At least provide another task (minimal-server) or something that we can use that pulls only in what is truly needed. Right now the only choice I have is to try and figure out for each package that lists itself as belonging on server whether it is needed and then to manually install it and to review this selection every couple of months in case another important one comes along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563026 Title: LXC/LXD installed by default on Ubuntu server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1563026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563026] Re: LXC/LXD installed by default on Ubuntu server
Dustin, this is assigned to you. Are you actually working on this? ** Changed in: ubuntu-meta (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563026 Title: LXC/LXD installed by default on Ubuntu server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1563026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447352] Re: No dpkg trigger on /etc/grub.d
This was marked as a duplicate of #1250109, but it is not. This one is about grub itself registering a trigger on its hook directory. ** This bug is no longer a duplicate of bug 1250109 Please use dpkg-triggers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447352 Title: No dpkg trigger on /etc/grub.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1447352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409280] Re: Graphviz's sfdp is seriuosly crippled without a triangulation library
This is still an issue in xenial. Any chance to get this fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409280 Title: Graphviz's sfdp is seriuosly crippled without a triangulation library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1409280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Still an issue in xenial! I've added package 'linux' since that's the source package that has the problem and I'm not sure how else to show that this is a problem in trusty AND xenial (and probably everything in- between). ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Is there anything else I can do to get this fixed? We have now gone through a couple of kernel versions all of which have this bug. One of them had a problem which meant I couldn't use it and this bug meant I couldn't just reboot into the previous kernel (because it had been auto-removed). I have already attached a patch, could one of the kernel maintainers have a look at it and either include it in the package or let me know why it can't be? Cheers, Seb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
I have attached an (untested) patch to fix this issue hoping that that will prod it along a bit. The patch is against the sources of `linux_3.13.0-67.110` as downloaded by an `apt-get source linux=3.13.0-67.110` on 14.04.3. Cheers, Seb ** Patch added: "Change the image-extra post* maintainer script to run runparts on the appropriate directory in /etc/kernel." https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+attachment/4515267/+files/fix-image-extra-postrm-action.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501345] Re: linux-image-3.13.0-65-generic breaks serial communication
Same here. Could not reproduce the issue on 3.13.0-66.108 any more. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic breaks serial communication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Changed the package name to linux-lts-trusty as that what I've seen used in other bug reports against the kernel for trusty even though the source package for e.g. linux-image-extra-3.13.0-65-generic is listed in apt-cache as linux. Feel free to change back if this is inappropriate. ** Package changed: linux (Ubuntu) => linux-lts-trusty (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500768] Re: python3.4.3 SRU break requests
Am I understanding this right that with the above proposed fix to urllib3, python itself will go back up to version 3.4.3? I.e. the archive revert is reverted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500768 Title: python3.4.3 SRU break requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1500768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500768] Re: python3.4.3 SRU break requests
Please note that not all people are "beached". I manage some 56 machines and they regularly run apt-get update dist-upgrade and are pinned to versions from a local mirror of the archive. Those machines all downgraded python after the revert which broke a large number of apps amongst them apport, unattended-upgrades and others (see attached reports). I believe this may be due to pyc files not being cleaned out? What can I do to get these machines working properly again? ** Attachment added: "_usr_share_apport_apport-gtk.0.crash" https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+attachment/4489178/+files/_usr_share_apport_apport-gtk.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500768 Title: python3.4.3 SRU break requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500768] Re: python3.4.3 SRU break requests
Looks like I can attach only one crash report per comment?! ** Attachment added: "_usr_share_unattended-upgrades_unattended-upgrade-shutdown.0.crash" https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+attachment/4489179/+files/_usr_share_unattended-upgrades_unattended-upgrade-shutdown.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500768 Title: python3.4.3 SRU break requests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] [NEW] linux-image-extra-*-generic postrm script runs install actions
Public bug reported: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb ** Affects: linux (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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Forgot to mention: I noticed it in 14.04.3 trusty kernel version 3.13.0-63. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Brad, what's to diagnose? I've done all the diagnosis for you already. Anyway, here's the relevant snippet from the dpkg log with the problematic line highlighted: (Reading database ... 149768 files and directories currently installed.) Removing linux-headers-3.13.0-63-generic (3.13.0-63.103) ... Removing linux-headers-3.13.0-63 (3.13.0-63.103) ... Removing linux-image-extra-3.13.0-63-generic (3.13.0-63.103) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-63-generic /boot/vmlinuz-3.13.0-63-generic ^ run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-63-generic /boot/vmlinuz-3.13.0-63-generic update-initramfs: Generating /boot/initrd.img-3.13.0-63-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-63-generic /boot/vmlinuz-3.13.0-63-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-63-generic /boot/vmlinuz-3.13.0-63-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.13.0-65-generic Found initrd image: /boot/initrd.img-3.13.0-65-generic Found linux image: /boot/vmlinuz-3.13.0-63-generic Found initrd image: /boot/initrd.img-3.13.0-63-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin done Here is the content of /var/lib/dpkg/info/linux-image-extra-3.13.0-65-generic.postrm, again with highlight: #!/bin/sh set -e case "$0::$1" in *.postinst::configure|*.postrm::remove) depmod -a -F /boot/System.map-3.13.0-65-generic 3.13.0-65-generic || true for dir in "/etc/kernel/postinst.d" "/etc/kernel/postinst.d/3.13.0-65-generic" ^^^ ^^ do if [ -d "$dir" ]; then run-parts --verbose --exit-on-error --arg="3.13.0-65-generic" --arg="/boot/vmlinuz-3.13.0-65-generic" "$dir" fi done ;; esac All those postinst.d should be postrm.d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
Sorry Brad. I didn't notice the 'Automatic Script' bit. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501884 Title: linux-image-extra-*-generic postrm script runs install actions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404783] Re: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core'
Interestingly it only happens the first time I run apt-get dist-upgrade after running apt-get update: seb@ws3559:~$ sudo apt-get update Fetched 1,581 kB in 9s (167 kB/s) seb@ws3559:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. W: Unknown Multi-Arch type 'no' for package 'compiz-core' W: Unknown Multi-Arch type 'no' for package 'compiz-gnome' W: Unknown Multi-Arch type 'no' for package 'compiz-core' W: Unknown Multi-Arch type 'no' for package 'compiz-gnome' W: You may want to run apt-get update to correct these problems seb@ws3559:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. seb@ws3559:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. seb@ws3559:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404783 Title: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core' To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1404783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404783] Re: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core'
This just started happening for me here. I'm on 14.04.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404783 Title: warnings from apt: W: Unknown Multi-Arch type 'no' for package 'compiz-core' To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1404783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471677] Re: package icedtea-netx (not installed) failed to install/upgrade: trying to overwrite shared '/usr/bin/policyeditor', which is different from other instances of package icedtea-netx:am
I had icedtea-netx:i386 installed on my Ubuntu 14.04.2 amd64 system. Trying to install icedtea-plugin failed due to a package conflict between icedtea-netx:amd64 and icedtea-netx:i386 over the file /usr/bin/policyeditor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471677 Title: package icedtea-netx (not installed) failed to install/upgrade: trying to overwrite shared '/usr/bin/policyeditor', which is different from other instances of package icedtea-netx:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1471677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125595] Re: /usr/sbin/dkms: line echo: write error: Broken pipe
I'm seeing this on trusty 14.04: root@ws3264:~# dpkg-reconfigure nvidia-331 Removing all DKMS Modules /usr/sbin/dkms: line 1909: echo: write error: Broken pipe /usr/sbin/dkms: line 1911: echo: write error: Broken pipe Done. update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-3.13.0-52-generic INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-331-331.113 DKMS files... Building for 3.13.0-52-generic and 3.13.0-53-generic Building for architecture x86_64 Building initial module for 3.13.0-52-generic ^[[1;2CDone. nvidia_331: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.13.0-52-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 3.13.0-53-generic Done. nvidia_331: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.13.0-53-generic/updates/dkms/ depmod DKMS: install completed. Processing triggers for initramfs-tools (0.103ubuntu4.2) ... update-initramfs: Generating /boot/initrd.img-3.13.0-53-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125595 Title: /usr/sbin/dkms: line echo: write error: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1125595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447352] [NEW] No dpkg trigger on /etc/grub.d
Public bug reported: This is related to #396381 but probably slightly more specific. Currently if any packages install or update files in /etc/grub.d, they need to arrange for update-grub to be run via their postinst or similar. I think the appropriate way would be for grub to register a trigger for that directory so that install and removal of packages that install files in it automatically run update-grub. I have observed this in 14.04 and 15.04. ** Affects: grub2 (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/1447352 Title: No dpkg trigger on /etc/grub.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1447352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776650] Re: Build qemu-kvm with native VDE support
What's the status on this? I've been wanting this for some time now too and the comments left here are not very clear as to what the actual stumbling block is for why this isn't fixed yet. Connecting n VMs together without connecting them to the host and without being root is possible in only two ways at the moment: - Using UDP MC sockets which are terribly inefficient (A file transfer between two VMs through ssh managed to load my machine up to 2% CPU. The same transfer via the user network between VM and host loads it up to about 50% as it should (4 cores)) - Using VDE which currently requires me to recompile qemu/kvm. Can anybody from the server team or whoever knows about these processes comment on what it would take to get this progressed? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/776650 Title: Build qemu-kvm with native VDE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776650/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 776650] Re: Build qemu-kvm with native VDE support
What's the status on this? I've been wanting this for some time now too and the comments left here are not very clear as to what the actual stumbling block is for why this isn't fixed yet. Connecting n VMs together without connecting them to the host and without being root is possible in only two ways at the moment: - Using UDP MC sockets which are terribly inefficient (A file transfer between two VMs through ssh managed to load my machine up to 2% CPU. The same transfer via the user network between VM and host loads it up to about 50% as it should (4 cores)) - Using VDE which currently requires me to recompile qemu/kvm. Can anybody from the server team or whoever knows about these processes comment on what it would take to get this progressed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776650 Title: Build qemu-kvm with native VDE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313469] [NEW] Power button causes unclean shutdown
Public bug reported: I noticed that with Ubuntu Server 13.10 when I press the power button, it flashes acpid exiting on the console and then does an immediate hard poweroff. Filesystems are not umounted and require recovery on restart. Upon further investigation I found that apparently both acpid and systemd-logind attempt to handle the event with the described result. Disabling either acpid (by deleting /etc/acpi/events/powerbtn) or systemd (by adding HandlePowerKey=ignore to /etc/systemd/logind.conf) fixes the issue. Note: I was reproducing the issue using clean 13.10 server installs in KVMs. http://superuser.com/questions/677331/unsafe-power-off-on-power- button-pressed/746841#746841 indicates that others have observed this with non-VM installs. Also #1219338 and #1245327 may be related. ** Affects: acpid (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/1313469 Title: Power button causes unclean shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1313469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857651] Re: Unable to hide users from login screen / user switcher
Given that there is a patch available for the upstream bug, could Ubuntu pull that into it's version of accountservice? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011342] Re: Converting ogv to asf using avconv fails - decoding failed
Still present in saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011342 Title: Converting ogv to asf using avconv fails - decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1011342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
