[Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth
I believe I am experiencing this on 20.04 > (EE) open /dev/dri/card0: No such file or directory The problem seems to be that gdm-wait-for-drm doesn't work for (muxless) dual GPU laptops when using the dGPU. GDM will start when only card1 is available, *both* card0 and card1 need to be available before starting X. (As a quick hack, I am using `ExecStartPre=/bin/sleep 1` to give drm enough time before starting GDM.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925344 Title: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878245] Re: Cannot use PRIME render offloading on AMD CPUs
Proposed fix: https://github.com/tseliot/ubuntu-drivers-common/pull/40 ** Patch added: "prime-offloading-with-amd.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1878245/+attachment/5370444/+files/prime-offloading-with-amd.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878245 Title: Cannot use PRIME render offloading on AMD CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1878245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878245] [NEW] Cannot use PRIME render offloading on AMD CPUs
Public bug reported: Release: Ubuntu 20.04 Package version: 1:0.8.1 gpu-manager will only configure X for PRIME render offloading when using an Intel CPU with integrated graphics. AMD CPUs also have integrated graphics that can support GPU offloading. Upstream report: https://github.com/tseliot/ubuntu-drivers- common/issues/39 ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878245 Title: Cannot use PRIME render offloading on AMD CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1878245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1153626] Re: Multiple Interfaces and IPs not detected in AWS VPC
My initial tests with Gaëtan's patch suggests it disables DHCP for but doesn't set a route or DNS manually. ci-info: ++--++-++---+ ci-info: | Device | Up |Address | Mask | Scope | Hw-Address| ci-info: ++--++-++---+ ci-info: | eth0 | True | 172.16.255.107 | 255.255.254.0 | global | 06:94:b2:8b:c0:3e | ci-info: | eth0 | True | 172.16.254.112 | 255.255.254.0 | global | 06:94:b2:8b:c0:3e | ci-info: | lo | True | 127.0.0.1|255.0.0.0| host | . | ci-info: | lo | True | 172.27.221.33 | 255.255.255.255 | global | . | ci-info: ++--++-++---+ ci-info: ++Route IPv4 info++ ci-info: +---+--+--+---+---+---+ ci-info: | Route | Destination | Gateway|Genmask| Interface | Flags | ci-info: +---+--+--+---+---+---+ ci-info: | 0 | 0.0.0.0| 172.16.254.1 |0.0.0.0|eth0 | UG | ci-info: | 1 | 172.16.254.0 | 0.0.0.0| 255.255.254.0 |eth0 | U | ci-info: +---+--+--+---+---+---+ and network: version: 2 ethernets: eth0: addresses: - 172.16.255.107/23 - 172.16.254.112/23 dhcp6: true match: macaddress: 06:94:b2:8b:c0:3e set-name: eth0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1153626 Title: Multiple Interfaces and IPs not detected in AWS VPC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1153626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU
I am seeing the same sort of bug on my machine. msi X470 motherboard (just tried latest firmware - no change) AMD Ryzen 5 2400G and Ubuntu 18.04 Linux paul-ubuntu 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Sometimes it happens overnight when machine is idle / screen locked, other times when using machine. Oddly enough the most recent one still had the mouse moving but keyboard unresponsive. Also a remote reboot fails - unless I use the watchdog with 'nowayout=1' to for a hard reset 60s after things should have gone down so it seem systemd won't/can't stop the hung graphics system. Typically the error messages look like: [ 2567.463753] amdgpu :27:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vmid:3 pasid:32770) [ 2567.463763] amdgpu :27:00.0: at page 0x00010be01000 from 27 [ 2567.463767] amdgpu :27:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 Often repeated many, many times. Seeing this bug report this has been going on for over a year now it seems and still is not fixed! Also a friend of mine is seeing the same on another AMD-based system. All pretty crap and makes me seriously regret buying an AMD board. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810546 Title: AMDGPU VMC page fault with Athlon 200GE APU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832643] [NEW] Installer crash on RAID system
Public bug reported: Trying to install 18.04.2 on to existing assembled RAID system. Got to the grub installation phase and it then generated an error dialogue window saing it could not install to /dev/sda /dev/sdb (the usual for RAID) but none of the alternatives in the radio button choice actually allowed a continuation. If it could not do the grub step then the alternatives ought to at least work! $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy ubiquity ubiquity: Installed: 18.04.14.12 Candidate: 18.04.14.12 Version table: *** 18.04.14.12 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 18.04.14 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 Date: Wed Jun 12 21:22:17 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832643 Title: Installer crash on RAID system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1832643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750942] Re: stale pid for watchdog service
Dear Arijit, Many thanks for reporting this issue and providing a fix. I have applied your patch to the GIT repository on Sourceforge but I don't know how long it will take (if ever) to get included in the version distributed with 14.04 Regards, Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750942 Title: stale pid for watchdog service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1750942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal
I do not think so, but I may not fully understand what "subtree" implies. The realm was initially created with a command equivalent to: kdb5_ldap_util -D cn=admin,dc=example,dc=com create -subtrees dc=example,dc=com -r TEST.EXAMPLE.COM -s -H ldap://ldapserver.example.com with user entries like: dn: uid=testuser,ou=People,dc=example,dc=com I explicitly added the ou=People,dc=example,dc=com with "kdb5_ldap_util ... modify -subtrees ...", but that did not help. Setting sscope to 2 also did nothing. I can add a principal without specifying dn, but that leads to an entry like: dn: krbPrincipalName=testu...@test.example.com,cn=TEST.EXAMPLE.COM,cn=krb5,dc=example,dc=com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817955 Title: Getting new "DN is out of the realm subtree" error on adding principal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817955] [NEW] Getting new "DN is out of the realm subtree" error on adding principal
Public bug reported: Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg- 2ubuntu5.4), and started getting errors when adding new principals to LDAP. Obfuscated example: kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\" testuser" now gives: Authenticating as principal root/ad...@test.example.com with password. NOTICE: no policy specified for testu...@test.example.com; assigning "default" add_principal: DN is out of the realm subtree while creating "testu...@test.example.com". This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to CVE-2018-5729 or CVE-2018-5730. I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check. ** Affects: krb5 (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/1817955 Title: Getting new "DN is out of the realm subtree" error on adding principal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484027] Re: systemd-tmpfiles-clean warns about duplicate /var/log line
If it was fixed in 8.12.0-1ubuntu3 why am I still seeing this on a 16.04.2 system with: apt-cache policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status It happens one per day it seems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484027 Title: systemd-tmpfiles-clean warns about duplicate /var/log line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1484027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist
Generally me work-around so far has been to avoid systemd! However, where that is not an option you might be able to edit /etc/default/watchdog so the module is loaded on watchdog start-up. It is not ideal as you might have some other reasons for wanting the /dev/watchdog virtual file to be testable without the watchdog having started though (e.g. automated install script that probes harder support, etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535840 Title: systemd ignoring /etc/modules due to blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586570] Re: openvpn chroot does not have a valid resolv.conf
I am seeing this with 64-bit 14.04.5 (even though 'grheard' did not have this problem with 14.04) using OpenVPN via the network manager. Seems to happen independently of DHCP renewals as several were logged before this last bit: Feb 23 19:31:03 paul-ubuntu dhclient: DHCPREQUEST of 192.168.1.100 on eth1 to 192.168.1.1 port 67 (xid=0xacb31f1) Feb 23 19:31:03 paul-ubuntu dhclient: DHCPACK of 192.168.1.100 from 192.168.1.1 Feb 23 19:31:03 paul-ubuntu dhclient: bound to 192.168.1.100 -- renewal in 1379 seconds. Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]: (eth1): DHCPv4 state changed renew -> renew Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:address 192.168.1.100 Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:prefix 24 (255.255.255.0) Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:gateway 192.168.1.1 Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:hostname 'Desktop' Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:nameserver '192.168.1.1' Feb 23 19:31:03 paul-ubuntu dbus[1306]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Feb 23 19:31:03 paul-ubuntu dbus[1306]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Feb 23 19:34:32 paul-ubuntu nm-openvpn[2357]: [server] Inactivity timeout (--ping-restart), restarting Feb 23 19:34:32 paul-ubuntu nm-openvpn[2357]: SIGUSR1[soft,ping-restart] received, process restarting Feb 23 19:34:34 paul-ubuntu nm-openvpn[2357]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Feb 23 19:34:54 paul-ubuntu nm-openvpn[2357]: RESOLVE: Cannot resolve host address: : Temporary failure in name resolution This fault continued through several more DHCP renewals until I manually reset the link: Feb 23 23:04:11 paul-ubuntu nm-openvpn[2357]: message repeated 502 times: [ RESOLVE: Cannot resolve host address: : Temporary failure in name resolution] Feb 23 23:04:26 paul-ubuntu nm-openvpn[2357]: RESOLVE: signal received during DNS resolution attempt Feb 23 23:04:26 paul-ubuntu avahi-daemon[1439]: Withdrawing workstation service for tun0. Feb 23 23:04:26 paul-ubuntu NetworkManager[1577]:SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0) So manually disconnecting and reconnecting the VPN works, but is obviously not a satisfactory solution for machines that are normally unattended or if you wish to maintain privacy! System details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty $ apt-cache policy openvpn openvpn: Installed: 2.3.2-7ubuntu3.1 Candidate: 2.3.2-7ubuntu3.1 Version table: *** 2.3.2-7ubuntu3.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.2-7ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586570 Title: openvpn chroot does not have a valid resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1586570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577433] Re: /usr/sbin/openvpn:*** Error in `/usr/sbin/openvpn': corrupted double-linked list: ADDR ***
I am seeing this occasionally, today when disconnecting from a hung VPN session. I was seeing message such as: nm-openvpn[1832]: RESOLVE: Cannot resolve host address: : Temporary failure in name resolution In syslog which may, or may not, be related to the resulting crash. It might also be related to Bug #1406220 as the apport collected file shows the message also came from the malloc() call, but maybe the error reporting text has changed with libc updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577433 Title: /usr/sbin/openvpn:*** Error in `/usr/sbin/openvpn': corrupted double- linked list: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1577433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406220] Re: openvpn assert failure: *** Error in `/usr/sbin/openvpn': malloc(): smallbin double linked list corrupted: 0x00007fa766e09fb0 ***
It might be appearing now as Bug #1577433 due to some change in malloc() reporting text. I also see this and would like it fixed as memory allocation bugs in OpenVPN are potential security vulnerabilities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406220 Title: openvpn assert failure: *** Error in `/usr/sbin/openvpn': malloc(): smallbin double linked list corrupted: 0x7fa766e09fb0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1406220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1406220] Re: openvpn assert failure: *** Error in `/usr/sbin/openvpn': malloc(): smallbin double linked list corrupted: 0x00007fa766e09fb0 ***
Forgot to add the system details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty $ apt-cache policy openvpn openvpn: Installed: 2.3.2-7ubuntu3.1 Candidate: 2.3.2-7ubuntu3.1 Version table: *** 2.3.2-7ubuntu3.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.2-7ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406220 Title: openvpn assert failure: *** Error in `/usr/sbin/openvpn': malloc(): smallbin double linked list corrupted: 0x7fa766e09fb0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1406220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577433] Re: /usr/sbin/openvpn:*** Error in `/usr/sbin/openvpn': corrupted double-linked list: ADDR ***
Forgot to add the system details: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty $ apt-cache policy openvpn openvpn: Installed: 2.3.2-7ubuntu3.1 Candidate: 2.3.2-7ubuntu3.1 Version table: *** 2.3.2-7ubuntu3.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.2-7ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577433 Title: /usr/sbin/openvpn:*** Error in `/usr/sbin/openvpn': corrupted double- linked list: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1577433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664520] [NEW] Firefox fails to clear local storage
Public bug reported: I noticed that Firefox is keeping site-specific information even after using the 'Clear Recent History' option. For example, with a new firefox profile (e.g. start a guest session) go to www.youtube.com and view some video, then look in the location: ~/.mozilla/firefox//storage/default/ You should see a subdirectory named "https+++www.youtube.com". Now clear all history using the menu option History -> Clear Recent History... by selecting "everything" and ticking all boxes. Result should be no sign of having visited youtube. However the site- specific storage directory still exists which is a significant laps of privacy. It seems not to happen in a private tab, but that is not an excuse for failing to clear on requested. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty $ apt-cache policy firefox firefox: Installed: 51.0.1+build2-0ubuntu0.14.04.2 Candidate: 51.0.1+build2-0ubuntu0.14.04.2 Version table: *** 51.0.1+build2-0ubuntu0.14.04.2 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 28.0+build2-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (Ubuntu) => firefox (Ubuntu) ** Description changed: - I noticed that Fierfox is keeping site-specific information even after + I noticed that Firefox is keeping site-specific information even after using the 'Clear Recent History' option. For example, with a new firefox profile (e.g. start a guest session) go to www.youtube.com and view some video, then look in the location: ~/.mozilla/firefox//storage/default/ You should see a subdirectory named "https+++www.youtube.com". Now clear all history using the menu option History -> Clear Recent History... by selecting "everything" and ticking all boxes. Result should be no sign of having visited youtube. However the site- specific storage directory still exists which is a significant laps of privacy. It seems not to happen in a private tab, but that is not an excuse for failing to clear on requested. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty $ apt-cache policy firefox firefox: - Installed: 51.0.1+build2-0ubuntu0.14.04.2 - Candidate: 51.0.1+build2-0ubuntu0.14.04.2 - Version table: - *** 51.0.1+build2-0ubuntu0.14.04.2 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages - 100 /var/lib/dpkg/status - 28.0+build2-0ubuntu2 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + Installed: 51.0.1+build2-0ubuntu0.14.04.2 + Candidate: 51.0.1+build2-0ubuntu0.14.04.2 + Version table: + *** 51.0.1+build2-0ubuntu0.14.04.2 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages + 100 /var/lib/dpkg/status + 28.0+build2-0ubuntu2 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664520 Title: Firefox fails to clear local storage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1664520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Thanks Tim for the clarification. I will not make any more status changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
I have moved this to "fix committed", can someone verify that this patch will be backported to the Trusty 3.13 series kernel, or do I need to take any additional steps? I am not sure what my responsibility is in moving this forward from here. ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Ok scratch comment #13, must have been half asleep when I read comment #12 , is there a status change I need to make for Trusty to move this along? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Hello Joseph, do you need me to test just kernel-image and headers? or all debs in that dir, thanks for clarification. -Andrew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Between 2017-01-05 and about 2017-01-10 EST we had 17 recorded crashes on the neutron node. After patching as described above, we have had no crashes. Not being particularly familiar with kernel internals, or the details of the skb data structure, I was not able to confirm explicitly the cause by sending the packets that trigger the crash. I am trusting that the choice to drop the packets with the patch doesn't have any significant side effects for the openvswitch module. A clearer explanation with earlier patch(es) may be found here: https://patchwork.ozlabs.org/patch/559944/ https://patchwork.ozlabs.org/patch/712373/ It also may be of note to others that gso and gro offloading to the NIC are turned off on all of our interfaces. I am not sure how timely the application of the corresponding patch in the upstream stable kernel will be, so here is the patch I used. attached is the patch for my test build, using the sources in comment #3 ** Attachment added: "patch_1655683.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4803442/+files/patch_1655683.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
The kernel running in the above apport report is the patched kernel FYI. ** 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/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Sorry, apport-collect is trying to open a browser from a server where none is installed. I generated the report with apport-cli and have attached here instead. ** Attachment added: "apport.linux-image-3.13.0-106-generic.b9qc1535.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802917/+files/apport.linux-image-3.13.0-106-generic.b9qc1535.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
** Attachment added: "dump.201701051502" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802913/+files/dump.201701051502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
** Attachment added: "linux-image-3.13.0-106-generic-201701051502.crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802911/+files/linux-image-3.13.0-106-generic-201701051502.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
** Attachment added: "dmesg.201701051502" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+attachment/4802912/+files/dmesg.201701051502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
I built a new kernel from the ubuntu kernel source package for linux- image-3.13.0-106-generic. I am using the ubuntu shipped .config for linux-image-3.13.0-106-generic. I am testing the patch linked below in production. https://patchwork.ozlabs.org/patch/712373/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655683 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655117] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
*** This bug is a duplicate of bug 1655683 *** https://bugs.launchpad.net/bugs/1655683 ** This bug has been marked a duplicate of bug 1655683 kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655117 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1655117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655683] [NEW] kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Public bug reported:
Since 2016-12-30 EST we have been experiencing repeated crashes of our
OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
line 1486:
1471 /**
1472 * skb_peek - peek at the head of an _buff_head
1473 * @list_: list to peek at
1474 *
1475 * Peek an _buff. Unlike most other operations you _MUST_
1476 * be careful with this one. A peek leaves the buffer on the
1477 * list and someone else may run off with it. You must hold
1478 * the appropriate locks or have a private queue to do this.
1479 *
1480 * Returns %NULL for an empty list or a pointer to the head element.
1481 * The reference count is not incremented and the reference is therefore
1482 * volatile. Use with caution.
1483 */
1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
1485 {
1486 struct sk_buff *skb = list_->next;
1487
1488 if (skb == (struct sk_buff *)list_)
1489 skb = NULL;
1490 return skb;
1491 }
This generally results in a full panic crash of the Neutron node and
connectivity breaking for VMs within the cloud. However, after using
crash-dumptools to collect information on the crashes over the past
three days, the kernel loaded by kexec during the crashdump appears in
about 2 out of 3 crash instances to continue running, and we see a flap
of the neutron services instead of a full panic that brings the Neutron
server down and necessitates a hard reboot.
I believe that this is a manifestation of the openvswitch and issue
described on 2017-01-08 as:
"OVS can only process L2 packets. But OVS GRE receive handler
can accept IP-GRE packets. When such packet is processed by
OVS datapath it can trigger following assert failure due
to insufficient linear data in skb."
https://patchwork.ozlabs.org/patch/712373/
I have not tested the patch provided above yet.
Other information and a few sample dmesg outputs from the crash:
(multiple dumps available)
# lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
# apt-cache policy openvswitch
N: Unable to locate package openvswitch
root@neutron01:/var/crash# apt-cache policy openvswitch-common
openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy openvswitch-switch
openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy neutron-plugin-openvswitch-agent
neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
*** 1:2014.1.5-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:2014.1.3-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1:2014.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
example dmesg:
## dmesg.201701060019
> [33100.131019] [ cut here ]
> [33100.131176] kernel BUG at
> /build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
> [33100.131424] invalid opcode: [#1] SMP
> [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter
> ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth
> openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether
> x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm
> crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
> gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si
> bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca
> i2c_algo_bit ptp pps_core megaraid_sas mdio
> [33100.133560] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.13.0-106-generic
> #153-Ubuntu
> [33100.133800] Hardware name: IBM System x3650 M4 : -[7915AC1]-/00Y8473, BIOS
> -[VVE136AUS-1.60]- 12/12/2013
> [33100.134096] task: 880469da4800 ti: 880469dae000 task.ti:
> 880469dae000
> [33100.134325] RIP: 0010:[] []
> __skb_pull.part.7+0x4/0x6 [openvswitch]
> [33100.134628] RSP: 0018:88046fd03bb0 EFLAGS: 00010297
> [33100.134792] RAX: 880035d73866 RBX: 880461efb600 RCX:
> 880035d73800
> [33100.135011] RDX: 0210 RSI: 0214 RDI:
> 88046fd03c98
> [33100.135231] RBP: 88046fd03bb0 R08:
[Bug 1655117] Re: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Hi all, it looks like the patch I referenced above is indeed aimed at the openvswitch kernel module, should have looked more closely at the outset, so this bug really belongs with ubuntu-kernel, and I believe, specifically the pre-DKMS openvswitch kernel module. Looking into the ubuntu kernel source for /net/openvswitch/vport-gre.c https://github.com/Canonical-kernel/Ubuntu-kernel/blob/master/net/openvswitch/vport-gre.c The patch mentioned above at patchwork is not present. I am not familiar with the upstream kernel process. looking into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655117 Title: kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1655117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655117] [NEW] kernel BUG at skbuff.h:1486 Insufficient linear data in skb __skb_pull.part.7+0x4/0x6 [openvswitch]
Public bug reported:
Since 2016-12-30 EST we have been experiencing repeated crashes of our
OpenStack Icehouse / Trusty Neutron node with a kernel BUG at skbuff.h
line 1486:
1471 /**
1472 * skb_peek - peek at the head of an _buff_head
1473 * @list_: list to peek at
1474 *
1475 * Peek an _buff. Unlike most other operations you _MUST_
1476 * be careful with this one. A peek leaves the buffer on the
1477 * list and someone else may run off with it. You must hold
1478 * the appropriate locks or have a private queue to do this.
1479 *
1480 * Returns %NULL for an empty list or a pointer to the head element.
1481 * The reference count is not incremented and the reference is therefore
1482 * volatile. Use with caution.
1483 */
1484 static inline struct sk_buff *skb_peek(const struct sk_buff_head *list_)
1485 {
1486 struct sk_buff *skb = list_->next;
1487
1488 if (skb == (struct sk_buff *)list_)
1489 skb = NULL;
1490 return skb;
1491 }
This generally results in a full panic crash of the Neutron node and
connectivity breaking for VMs within the cloud. However, after using
crash-dumptools to collect information on the crashes over the past
three days, the kernel loaded by kexec during the crashdump appears in
about 2 out of 3 crash instances to continue running, and we see a flap
of the neutron services instead of a full panic that brings the Neutron
server down and necessitates a hard reboot.
I believe that this is a manifestation of the openvswitch and issue
described on 2017-01-08 as:
"OVS can only process L2 packets. But OVS GRE receive handler
can accept IP-GRE packets. When such packet is processed by
OVS datapath it can trigger following assert failure due
to insufficient linear data in skb."
https://patchwork.ozlabs.org/patch/712373/
I have not tested the patch provided above yet.
Other information and a few sample dmesg outputs from the crash:
(multiple dumps available)
# lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04
# apt-cache policy openvswitch
N: Unable to locate package openvswitch
root@neutron01:/var/crash# apt-cache policy openvswitch-common
openvswitch-common:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy openvswitch-switch
openvswitch-switch:
Installed: 2.0.2-0ubuntu0.14.04.3
Candidate: 2.0.2-0ubuntu0.14.04.3
Version table:
*** 2.0.2-0ubuntu0.14.04.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
2.0.1+git20140120-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
# apt-cache policy neutron-plugin-openvswitch-agent
neutron-plugin-openvswitch-agent:
Installed: 1:2014.1.5-0ubuntu7
Candidate: 1:2014.1.5-0ubuntu7
Version table:
*** 1:2014.1.5-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
1:2014.1.3-0ubuntu1.1 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1:2014.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
example dmesg:
## dmesg.201701060019
> [33100.131019] [ cut here ]
> [33100.131176] kernel BUG at
> /build/linux-mi9H1O/linux-3.13.0/include/linux/skbuff.h:1486!
> [33100.131424] invalid opcode: [#1] SMP
> [33100.131560] Modules linked in: xt_nat xt_conntrack ip6table_filter
> ip6_tables iptable_filter xt_REDIRECT xt_tcpudp iptable_nat nf_conntrack_ipv4
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables veth
> openvswitch gre vxlan ip_tunnel libcrc32c ipmi_devintf gpio_ich cdc_ether
> x86_pkg_temp_thermal intel_powerclamp coretemp usbnet kvm_intel mii kvm
> crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw
> gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich wmi ipmi_si
> bonding shpchp ioatdma lp mac_hid parport ahci libahci sfc igb e1000e mtd dca
> i2c_algo_bit ptp pps_core megaraid_sas mdio
> [33100.133560] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.13.0-106-generic
> #153-Ubuntu
> [33100.133800] Hardware name: IBM System x3650 M4 : -[7915AC1]-/00Y8473, BIOS
> -[VVE136AUS-1.60]- 12/12/2013
> [33100.134096] task: 880469da4800 ti: 880469dae000 task.ti:
> 880469dae000
> [33100.134325] RIP: 0010:[] []
> __skb_pull.part.7+0x4/0x6 [openvswitch]
> [33100.134628] RSP: 0018:88046fd03bb0 EFLAGS: 00010297
> [33100.134792] RAX: 880035d73866 RBX: 880461efb600 RCX:
> 880035d73800
> [33100.135011] RDX: 0210 RSI: 0214 RDI:
> 88046fd03c98
> [33100.135231] RBP: 88046fd03bb0 R08:
[Bug 1594658] Re: diskless setup with nfs mounted home hangs on shutdown/reboot
We were seeing this on a fresh Ubuntu 16.04 64-bit installation using fixed IP addresses and automounter for NFS drives. The suggestion #7 seems to fix it for use, but it would be useful to know just what is happening with the script. Is it trawling through some user's home directory when expanding the '~*' entry in the case statement in /sbin/resolvconf by any chance? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594658 Title: diskless setup with nfs mounted home hangs on shutdown/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1594658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634617] Re: Cisco client fails due to "communcation errors"
4.8.0-25-generic Ubuntu 16.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634617 Title: Cisco client fails due to "communcation errors" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocserv/+bug/1634617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634617] [NEW] Cisco client fails due to "communcation errors"
Public bug reported: ocserv runs, but claims problem in gnuTLS with randomness: Oct 18 14:20:43 pi ocserv[13339]: Setting 'pam' as primary authentication method Oct 18 14:20:43 pi ocserv[13339]: listening on 2 systemd sockets... Oct 18 14:20:43 pi ocserv[13339]: main: initialized ocserv 0.11.1 Oct 18 14:20:43 pi ocserv[13343]: sec-mod: reading supplemental config from files Oct 18 14:20:43 pi ocserv[13343]: sec-mod: sec-mod initialized (socket: /var/run/ocserv-socket.13339) Oct 18 14:21:14 pi ocserv[13344]: GnuTLS error (at worker-vpn.c:474): Error in the system's randomness device. Oct 18 14:21:14 pi ocserv[13339]: main: [:::172.17.115.194]:54053 user disconnected (reason: unspecified, rx: 0, tx: 0) ** Affects: ocserv (Ubuntu) Importance: Undecided Status: New ** Tags: gnutls -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634617 Title: Cisco client fails due to "communcation errors" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocserv/+bug/1634617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names
I just lost 3 days to this issue before I realized what was happening. I realize this is an edge case, and understand the issues with fixing this, but at least some type of better error messages would have helped prevent that waste of time. I was trying to setup a host to run docker with macvlan networks mapped to vlan interfaces on a pair of USB ethernet adapters connected to a BRIX used for testing. Couldn't get a bond on the pair to work, couldn't figure out why, then tried for just VLAN interfaces, and that didn't work either. Thought I was losing it, didn't seem that hard. Not sure how I figured it out, but realized if I switched back to using eth1, eth2 for the USB ethernet devices, using "net.ifnames=0 biosdevname=0" boot options + old-style mac-address rules to map, I could get everything to work. But, wasn't happy with the workaround, as I'd prefer to use the new predictable names. I like the idea of using last 6 digits of Mac address. I thought of doing this: sudo ln -s /dev/null /etc/udev/rules.d/73-usb-net-by-mac.rules to go back to slot names, but if I plug into different ports, names change, so no. Perhaps some different prefix other than enx to avoid confusion, usb123456 anyone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases or bridge names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577596] Re: ntpd not started when using ntpdate
*** This bug is a duplicate of bug 1575572 *** https://bugs.launchpad.net/bugs/1575572 I don't think this is a duplicate of bug #1575572 I am seeing this problem on an Ubuntu 16.04 machine that has the update "This bug was fixed in the package init-system-helpers - 1.29ubuntu2" mentioned as being a fix for that bug but ntpd is still broken on booting. I am seeing this: Jul 12 14:14:43 metop ntpd[1933]: unable to bind to wildcard address :: - another process may be running - EXITING Jul 12 14:14:50 metop ntpdate[1758]: step time server 134.36.22.27 offset 0.264278 sec So basically the systemd dependency arrangement is broken: ntpdate is slow now (as for comment #16 above) and not exiting before ntpd is started, it then it fails due to ntpdate still running. A later manual start of ntpd works fine, but that is not an acceptable situation for machines that are unattended and/or used by people that don't have administrative rights (or knowledge) to manually start ntpd later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574602] Re: VM86 is not enabled in Xenial i386 kernel
As for the previous case (my comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/comments/4) this is an important application for us, and having the VM86 option possible is pretty much essential for the machine to be usable in out real-time case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574602 Title: VM86 is not enabled in Xenial i386 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384303] Re: Cannot scan using Canon Lide 25 with simple-scan on 14.04.
Same problem as Ferdinand, scanner not recognised by xsane when on USB 3 port (but seen by lsusb) but worked when put on USB 2. One USB3: $ lsusb Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 010: ID 22b8:2e82 Motorola PCS Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub On USB2: $ lsusb Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 010: ID 22b8:2e82 Motorola PCS Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 002: ID 04a9:2220 Canon, Inc. CanoScan LIDE 25 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 $ apt-cache policy simple-scan simple-scan: Installed: 3.12.3-0ubuntu1 Candidate: 3.12.3-0ubuntu1 Version table: *** 3.12.3-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.12.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages I expect that USB 2/3 should be transparent to any application, more so when the peripheral is going to operate in USB2 in both cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384303 Title: Cannot scan using Canon Lide 25 with simple-scan on 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1384303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
I will try to look tomorrow or so at the proposed fix. Have you checked if it is still loaded OK following a reboot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093870] Re: A long startup fsck causes cyclic watchdog reboot
I think this problem is down to the IPMI style of watchdog being configured when the machine boots, but the Linux system not starting the refresh action until much later. For example if I try a test on my home PC (Ubuntu 12.04 64-bit desktop) after installing the watchdog and using "touch /forcefsck" to simulate this, my syslog has this relevant part: Jan 19 21:30:28 paul-ubuntu kernel: [9.492544] [drm] Initialized radeon 2.36.0 20080528 for :01:05.0 on minor 0 Jan 19 21:30:28 paul-ubuntu kernel: [9.617760] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [9.917460] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 10.217249] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 10.516992] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 10.816578] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 11.116403] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 11.416101] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 11.715686] HDMI ATI/AMD: no speaker allocation for ELD Jan 19 21:30:28 paul-ubuntu kernel: [ 91.544151] EXT4-fs (md1): re-mounted. Opts: errors=remount-ro Jan 19 21:30:28 paul-ubuntu kernel: [ 91.896020] EXT4-fs (md2): mounted filesystem with ordered data mode. Opts: (null) Jan 19 21:30:28 paul-ubuntu kernel: [ 92.431631] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 19 21:30:28 paul-ubuntu kernel: [ 96.927417] EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null) Jan 19 21:30:28 paul-ubuntu kernel: [ 97.037128] RPC: Registered named UNIX socket transport module. Jan 19 21:30:28 paul-ubuntu kernel: [ 97.037132] RPC: Registered udp transport module. Jan 19 21:30:28 paul-ubuntu kernel: [ 97.037133] RPC: Registered tcp transport module. Jan 19 21:30:28 paul-ubuntu kernel: [ 97.037136] RPC: Registered tcp NFSv4.1 backchannel transport module. Jan 19 21:30:28 paul-ubuntu kernel: [ 97.084401] FS-Cache: Loaded Jan 19 21:30:28 paul-ubuntu kernel: [ 97.274125] FS-Cache: Netfs 'nfs' registered for caching Jan 19 21:30:28 paul-ubuntu kernel: [ 97.316611] init: failsafe main process (1320) killed by TERM signal Jan 19 21:30:28 paul-ubuntu kernel: [ 97.382416] audit_printk_skb: 12 callbacks suppressed Jan 19 21:30:28 paul-ubuntu kernel: [ 97.382419] type=1400 audit(1453239028.288:16): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/rsyslogd" pid=1352 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.442406] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). Jan 19 21:30:28 paul-ubuntu kernel: [ 97.945825] type=1400 audit(1453239028.852:17): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.945833] type=1400 audit(1453239028.852:18): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.945837] type=1400 audit(1453239028.852:19): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.946190] type=1400 audit(1453239028.852:20): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.946194] type=1400 audit(1453239028.852:21): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.946379] type=1400 audit(1453239028.852:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1415 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.984247] type=1400 audit(1453239028.892:23): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/klogd" pid=1416 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 97.984684] type=1400 audit(1453239028.892:24): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/bin/ping" pid=1413 comm="apparmor_parser" Jan 19 21:30:28 paul-ubuntu kernel: [ 98.000167] type=1400 audit(1453239028.908:25): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/syslog-ng" pid=1417 comm="apparmor_parser" Jan 19 21:30:29 paul-ubuntu wd_keepalive[1502]: starting watchdog keepalive daemon (5.14): Jan 19 21:30:29 paul-ubuntu wd_keepalive[1502]: int=1 alive=/dev/watchdog realtime=yes
[Bug 932381] Re: IT87 watchdog timer driver not working
Note the work-around for this bug is not in the GIT repository for the watchdog package as: http://sourceforge.net/p/watchdog/code/ci/0d156df287656d1031389cac99caa9fa94c2d204/ Hopefully a release of version 5.15 soon will make that more widely available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932381 Title: IT87 watchdog timer driver not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/932381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1010855] Re: watchdog/0 100% cpu usage
Note the "watchdog/0" thread you see is not the system monitoring daemon. Rather it has a similar task for kernel scheduling: http://linux-tips.org/t/what-is-kernel-soft-lockup/78 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1010855 Title: watchdog/0 100% cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1010855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535854] Re: watchdog daemon going in to failed state on reboot
I just tested the proposed fix from https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/comments/7 and while it includes the fix for the "unbalanced quoting" it does not fix the system going in to a failed state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535854 Title: watchdog daemon going in to failed state on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1535854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
I tested the proposed fix from comment #7 on bug #1535854 but it did not work for that system (16.04) :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459730] Re: rsyslog doesn't create /dev/xconsole
This is still present in the development branch for 16.04 Jan 19 17:53:23 ubuntu rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.14.0 try http://www.rsyslog.com/e/2039 ] System information: $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 $ apt-cache policy rsyslog rsyslog: Installed: 8.14.0-2ubuntu2 Candidate: 8.14.0-2ubuntu2 Version table: *** 8.14.0-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/459730 Title: rsyslog doesn't create /dev/xconsole To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
This is probably the same problem as bug #1535854 thought there could be a number of related factors, for example bug #1535840 for module loading. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535854] Re: watchdog daemon going in to failed state on reboot
Doh! I meant bug #1448924 (above is this bug) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535854 Title: watchdog daemon going in to failed state on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1535854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535854] Re: watchdog daemon going in to failed state on reboot
This may be a duplicate of bug #1535854 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535854 Title: watchdog daemon going in to failed state on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1535854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378696] Re: --version not supported (error in manpage ?)
This has been fixed from at least 2011 onwards so can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/378696 Title: --version not supported (error in manpage ?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/378696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1225386] Re: watchdog should allow a configurable SIGTERM->SIGKILL delay
This has been added to the current GIT version: http://sourceforge.net/p/watchdog/code/ci/77e777e2fb4cc0723fb51ad5556a427cf345385b/ Hopefully there will soon be a version 5.15 release with this feature included. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225386 Title: watchdog should allow a configurable SIGTERM->SIGKILL delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1225386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 795622] Re: Interface sensor fails
Some updates added this month (Jan 2016) add a timer so you get a less "trigger happy" behaviour if the interface is slow in coming up. Currently in the GIT version, but hopefully this will be in a release version 5.15 some time soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/795622 Title: Interface sensor fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/795622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535854] [NEW] watchdog daemon going in to failed state on reboot
Public bug reported: I was testing the watchdog daemon code on the development version of 16.04 today and found the associated systemd service files for this has some bugs. The first of these was a typo in /lib/systemd/system/watchdog.service where there was a missing ['] character. This lead to an error message "Unbalanced quoting, ignoring" which was easy to fix. The update is now in the source-forge repository for the project as commit http://sourceforge.net/p/watchdog/code/ci/38e6430f80907a84741c760ef48df69a679b294c/ However, I have not found the reason for the second problem where the daemon has some fault at reboot time and goes in to "failed state" and then it will not restart with the machine booting. The typical related syslog entries are: Jan 19 16:46:08 ubuntu watchdog[2066]: stopping daemon (5.14) Jan 19 16:46:08 ubuntu systemd[1]: Stopping watchdog daemon... Jan 19 16:46:09 ubuntu systemd[1]: watchdog.service: Control process exited, code=exited status=1 Jan 19 16:46:09 ubuntu systemd[1]: Stopped watchdog daemon. Jan 19 16:46:09 ubuntu systemd[1]: watchdog.service: Unit entered failed state. Jan 19 16:46:09 ubuntu systemd[1]: watchdog.service: Triggering OnFailure= dependencies. Jan 19 16:46:09 ubuntu systemd[1]: watchdog.service: Failed to enqueue OnFailure= job: Resource deadlock avoided Jan 19 16:46:09 ubuntu systemd[1]: watchdog.service: Failed with result 'exit-code'. I am guessing this is related to the shut-down approach for the watchdog daemon where normally the wd_keepalive daemon is started afterwards (to prevent a reboot if the hardware module is configured for "no way out" so the timer cannot be stopped). $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 $ apt-cache policy watchdog watchdog: Installed: 5.14-3 Candidate: 5.14-3 Version table: *** 5.14-3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status I have contacted the watchdog project maintainer with a view to working out a solution to this. This bug report is more of a marker to let folks know that there is an issue here if you plan on having high-availability servers based on Ubuntu 16.04 (well, any systemd based system really..) where watchdog-based fault recovery is an expectation. ** Affects: watchdog (Ubuntu) Importance: Undecided Status: New ** Package changed: rsyslog (Ubuntu) => watchdog (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535854 Title: watchdog daemon going in to failed state on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1535854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535840] [NEW] systemd ignoring /etc/modules due to blacklist
Public bug reported: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535840 Title: systemd ignoring /etc/modules due to blacklist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535854] Re: watchdog daemon going in to failed state on reboot
Just to add this is only a problem on shut down / reboot, you can manually stop and start the daemon without problems using: service watchdog start service watchdog stop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535854 Title: watchdog daemon going in to failed state on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1535854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093870] Re: A long startup fsck causes cyclic watchdog reboot
Usually the wd_keepalive daemon would be started early for this reason, to keep the hardware from timing out. Once the machine is up it would hand over to the watchdog daemon that runs system tests. I am guessing that the at-boot fsck is run before loading anything (daemons, etc) so all the file systems are free of any open handles, etc, that might cause problems for repair actions. I'm not sure how easy it would be to get round that problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093870 Title: A long startup fsck causes cyclic watchdog reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1093870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 705934] Re: Pidgin seems to crash (or vanish) randomly
If it didn't take you 4 years to acknowledge a bug report things may have been different :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/705934 Title: Pidgin seems to crash (or vanish) randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/705934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
We also run critical software that depends on the vm86 for performance reasons, and we are already using dosemu with root privileges to gain direct hardware access, so we see the potential security risks of this are trivial. The suggestion above to have the patch back-ported to enable vm86 only when vm.mmap_min_addr=0 seems a perfectly good way of satisfying all user cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498069] [NEW] indicator-datetime does not show other location's times in 24-hour time
Public bug reported: Ubuntu 15.04 indicator-datetime 13.10.0+15.04.20150406-0ubuntu1 When the clock is set to 24-hour time, other time zones' times are not in 24-hour time. For example, 24-hour time is on, and local time is 10:32 CDT, but UTC shows 3:32 PM, not 15:32. ** Affects: unity (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/1498069 Title: indicator-datetime does not show other location's times in 24-hour time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1498069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
This is also happening with the latest supported kernel on 14.04 LTS. We are seeing various repeated messages of Request for unknown module key 'Magrathea: Glacier signing key: 6fca287c2573d09ca32c1980c0d763777a63d4f5' err -11 on some, but not all, machines running this. I guess it relates to the instillation option(s)? $uname -a Linux processviirs 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449227] [NEW] package virtualbox 4.3.18-dfsg-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: when trying to run virtual box it will not load up, and when it does load an error message pops up and shuts down virtualbox completely. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: virtualbox 4.3.18-dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 Date: Mon Apr 27 15:24:19 2015 DuplicateSignature: package:virtualbox:4.3.18-dfsg-2ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-14 (195 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: virtualbox Title: package virtualbox 4.3.18-dfsg-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2015-03-31 (26 days ago) VirtualBox.ModInfo: ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449227 Title: package virtualbox 4.3.18-dfsg-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1449227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421044] Re: Too easy to accidentally restart computer when 'restart to complete update' box pop up
I agree with Daniel, having a machine randomly reboot on you because of a fault in GUI design is pretty serious, same as if the kernel occasionally panicked when you happened to be typing. Any ideas of time- scale to the patch being pushed out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421044 Title: Too easy to accidentally restart computer when 'restart to complete update' box pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1421044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320683] Re: Update manager does not show all available updates
Having read the page on phased updates I can see the rational behind that. However, it is still a broken GUI in my view because it is not telling you the whole story. You are told one thing by the GUI and another if you look at the package status vit apt-get or similar. Would it not be better to tell folk in the GUI that updates are being deployed in a phased manner? That way you could see if there was something you really wanted done now, or just leave the machine to deploy them over the phased period? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320683 Title: Update manager does not show all available updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1320683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421044] Re: Too easy to accidentally restart computer when 'restart to complete update' box pop up
Thanks Brian, will look out for that! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421044 Title: Too easy to accidentally restart computer when 'restart to complete update' box pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1421044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217933] Re: update-grub fails to detect other md OS
This is still broken with 14.04 and the same patch seems to work: $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 $ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02~beta2-9ubuntu1 Version table: 2.02~beta2-9ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 2.02~beta2-9 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217933 Title: update-grub fails to detect other md OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1217933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443349] [NEW] update-manager failes to show new updates
Public bug reported: Today I found the update manager pestering me once again to restart the system (stupid, since I already know about certain past updates and do not want to do that just now). However, when I checked for anything new using apt-get upgrade it was telling me about 7 more packages that the GUI failed to detect: $ sudo apt-get upgrade [sudo] password for paul: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: gvfs gvfs-backends gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs 7 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 681 kB of archives. After this operation, 28.7 kB of additional disk space will be used. Do you want to continue? [Y/n] So why did the GUI not inform me of this? Why is it prioritising a restart that I ALREADY SAID NO TO instead of informing me of other, potentially important, updates that the underlying manager has found? It seems to me that the GUI update manager in 14.04 is a serious retrograde step from the one in 12.04 and the behaviour priorities need to be reassessed immediately: 1) If there are new updates, show them before prompting for any other actions (e.g. pending restart). 2) If I cancel a restart, don't pester me with a focus-grabbing menu after a few minutes and whenever something package-related happens (already listed as bug #1293445). That is exactly the sort of thing the notification area was suited to! My system details: $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 $ apt-cache policy update-manager update-manager: Installed: 1:0.196.12 Candidate: 1:0.196.12 Version table: *** 1:0.196.12 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.196.11 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ** Affects: update-manager (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/1443349 Title: update-manager failes to show new updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1443349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441595] [NEW] update-manager defaults to restart
Public bug reported: In Ubuntu 14.04 the update manager will pop up telling you a restart is required for certain types of update (kernel, etc). However, it defaults to restart now which is unsafe, as an accidental return with that pop-up in focus will try to reboot your machine, and that might be quite unwanted at this time. The default should always be safe - in this case the 'later' button. I see this has been fixed in the latests release 15.04.3 but the change has not been back-ported to the 14.04 LTS version. $ apt-cache policy update-manager update-manager: Installed: 1:0.196.12 Candidate: 1:0.196.12 Version table: *** 1:0.196.12 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.196.11 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages It is simple enough to fix, as shown in the diff/patch. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Patch added: The fix back-ported from 15.04 version https://bugs.launchpad.net/bugs/1441595/+attachment/4369342/+files/fix-restart.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441595 Title: update-manager defaults to restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1441595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293445] Re: The computer needs to restart to finish installing updates. notification should have a user defined timer to ask next time
Exactly! This is not Windows - we should not be pestered incessantly by something like this because we might have done some update as part of a larger number that needs a reboot, but we have a good reason for not doing so for some time (running jobs, remote users also logged in, etc). At most, if you say 'later' it should go quiet until there are actually more updates applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293445 Title: The computer needs to restart to finish installing updates. notification should have a user defined timer to ask next time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1293445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
Updated a 12.04 LTS box today with the kernel 3.13.0-39-generic #66~precise1-Ubuntu SMP Wed Oct 29 09:56:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux and problem still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Upgrading from 14.04 to 14.10. Only solution #62 worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376245] Re: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs'
We are seeing the same a dozen or so timers per day, and it happened after we updated from the -36 to the -37 kernel build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376245 Title: remove_proc_entry+0x139/0x1b0() -- name 'fs/nfsfs' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309985] Re: nlpsolver doesnt work with libre office
Similar problem with 12.04 x64 system, shows it with Error: The status of this extension is unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309985 Title: nlpsolver doesnt work with libre office To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nlpsolver/+bug/1309985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237042] Re: ureadahead source needs tracing_enabled changed to tracing_on for 12.04.3
Still broken on 12.04.5 recently updated: $ apt-cache policy ureadahead ureadahead: Installed: 0.100.0-12 Candidate: 0.100.0-12 Version table: *** 0.100.0-12 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status $ uname -a Linux pscpc 3.13.0-34-generic #60~precise1-Ubuntu SMP Wed Aug 13 15:55:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Also finding nothing in /var/lib/ureadahead suggesting it never worked on my system (installed as 12.04.4 I think) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237042 Title: ureadahead source needs tracing_enabled changed to tracing_on for 12.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260321] Re: dpkg-deb unable to install/upgrade oracle-java8-installer
No, the underlying problem is with dpkg not recognising the .xz compression type used in Oracle's .deb file. This is ALREADY fixed in the 12.04 version, so for from there being nothing the Ubuntu developers can do, there is - backport the later version of dpkg that supports the .xz file type! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260321 Title: dpkg-deb unable to install/upgrade oracle-java8-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1260321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350310] Re: update-manager chashes on 12.04.4 HWE update
Attached are my term.log files from before the bug report and afterwards when it seems to have succeded (mostly). I say mostly, as there are missing firmware warnings, and it screwed up the graphics (removed the nvidia driver but did not un-blacklist the nouveau driver, so 640x480 VGA graphics on reboot), but those are not this bug report. ** Attachment added: term.log files https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1350310/+attachment/4173414/+files/term.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350310 Title: update-manager chashes on 12.04.4 HWE update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1350310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192037] Re: rsyslog shuts down too soon with Upstart
I would also like to have shutdown messages logged. Could it be configured to stop on reaching the last of the init-style of run-levels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192037 Title: rsyslog shuts down too soon with Upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1192037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350310] Re: update-manager chashes on 12.04.4 HWE update
Just to say a recent update has fixed this. There are still problems with Nvidia driver post-update, but that is another bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350310 Title: update-manager chashes on 12.04.4 HWE update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1350310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328264] Re: packaging issues with the trusty Xstack in precise xserver-xorg-lts-trusty
A recent update to the update-manager seems to have fixed this for me. Still problems with the Nvidia driver post-update, but that is not the same bug/dependency issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328264 Title: packaging issues with the trusty Xstack in precise xserver-xorg-lts- trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1328264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328264] Re: packaging issues with the trusty Xstack in precise xserver-xorg-lts-trusty
This bug, the ability to get the kernel back on to a supported stream, is still broken a month on, even though there was some update to the update manager today (which still caused a crash report, though that was supposed to be fixed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328264 Title: packaging issues with the trusty Xstack in precise xserver-xorg-lts- trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1328264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328264] Re: packaging issues with the trusty Xstack in precise xserver-xorg-lts-trusty
Running from the command line reports: $ /usr/bin/update-manager Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/defer/__init__.py, line 473, in _inline_callbacks result = gen.throw(result.type, result.value, result.traceback) File /usr/lib/python2.7/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py, line 54, in commit yield self._run_in_dialog(trans, self.INSTALL) File /usr/lib/python2.7/dist-packages/defer/__init__.py, line 473, in _inline_callbacks result = gen.throw(result.type, result.value, result.traceback) File /usr/lib/python2.7/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py, line 75, in _run_in_dialog yield dia.run() aptdaemon.errors.TransactionFailed: Transaction failed: None The following packages have unmet dependencies: libgl1-mesa-glx-lts-trusty: Depends: libglapi-mesa-lts-trusty (= 10.1.3-0ubuntu0.1~precise1) but 10.1.3-0ubuntu0.1~precise1 is to be installed Depends: libx11-6 (= 2:1.4.99.1) but 2:1.4.99.1-0ubuntu2.2 is to be installed Depends: libxdamage1 (= 1:1.1) but 1:1.1.3-2build1 is to be installed xserver-xorg-lts-trusty: Depends: xserver-xorg-core-lts-trusty (= 2:1.11) but 2:1.15.1-0ubuntu2~precise1 is to be installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328264 Title: packaging issues with the trusty Xstack in precise xserver-xorg-lts- trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1328264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350310] [NEW] update-manager chashes on 12.04.4 HWE update
Public bug reported: In spite of apparent fixes for [bug #1342424] I find that the update- manager is still crashing and failing to perform the HWE upgrade to move my 12.04.4 LTS installation. If I run the update-manager from the command line I get the same behaviour as the normal alert when updates are availabe, but also additional information. It proceds correctly until it has asked for the sudoer password, then it prints the error messages and triggers a crash report. $ /usr/bin/update-manager Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/defer/__init__.py, line 473, in _inline_callbacks result = gen.throw(result.type, result.value, result.traceback) File /usr/lib/python2.7/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py, line 54, in commit yield self._run_in_dialog(trans, self.INSTALL) File /usr/lib/python2.7/dist-packages/defer/__init__.py, line 473, in _inline_callbacks result = gen.throw(result.type, result.value, result.traceback) File /usr/lib/python2.7/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py, line 75, in _run_in_dialog yield dia.run() aptdaemon.errors.TransactionFailed: Transaction failed: None The following packages have unmet dependencies: libgl1-mesa-glx-lts-trusty: Depends: libglapi-mesa-lts-trusty (= 10.1.3-0ubuntu0.1~precise1) but 10.1.3-0ubuntu0.1~precise1 is to be installed Depends: libx11-6 (= 2:1.4.99.1) but 2:1.4.99.1-0ubuntu2.2 is to be installed Depends: libxdamage1 (= 1:1.1) but 1:1.1.3-2build1 is to be installed xserver-xorg-lts-trusty: Depends: xserver-xorg-core-lts-trusty (= 2:1.11) but 2:1.15.1-0ubuntu2~precise1 is to be installed What I expect is the system to (A) correctly resolve and install the dependancies to get the HWE update, and (B) if it can't do that to not crash out when reporting the cause. Other systems details are: $ apt-cache policy update-manager update-manager: Installed: 1:0.156.14.16 Candidate: 1:0.156.14.16 Version table: *** 1:0.156.14.16 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.156.14.5 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 1:0.156.14 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ uname -a Linux pscpc 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15 04:01:04 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ** Affects: update-manager (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/1350310 Title: update-manager chashes on 12.04.4 HWE update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1350310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350310] Re: update-manager chashes on 12.04.4 HWE update
Sorry, should have been related to [bug #1341324]. Not sure if this counts a distribution upgrade since it is about continued kernel support for 12.04 LTS and not about moving to 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350310 Title: update-manager chashes on 12.04.4 HWE update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1350310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312814] Re: red5-server has unmet dependencies
I did get it to install after manually installling libtomcat6-java, but To reproduce: ubuntu 14.04 LTS sudo apt-get update sudo apt-get upgrade sudo apt-get install red5-server red5-server: Depends: libtomcat6-java (= 6.0.20-7) but it is not going to be installed then: sudo apt-get install libtomcat6-java This successfully brings in all dependencies for libtomcat6-java and installs. Trying again after manually meeting the libtomcat6-java dependency: sudo apt-get install red5-server Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libred5-java The following NEW packages will be installed: libred5-java red5-server 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/1,023 kB of archives. After this operation, 1,372 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously unselected package libred5-java. (Reading database ... 263596 files and directories currently installed.) Preparing to unpack .../libred5-java_1.0~svn4374-3_all.deb ... Unpacking libred5-java (1.0~svn4374-3) ... Selecting previously unselected package red5-server. Preparing to unpack .../red5-server_1.0~svn4374-3_all.deb ... Unpacking red5-server (1.0~svn4374-3) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up libred5-java (1.0~svn4374-3) ... Setting up red5-server (1.0~svn4374-3) ... Allowing use of questionable username. Adding system user `_red5' (UID 119) ... Adding new user `_red5' (UID 119) with group `nogroup' ... Not creating home directory `/usr/share/red5'. * Starting Flash streaming server red5-server [fail] invoke-rc.d: initscript red5-server, action start failed. dpkg: error processing package red5-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: red5-server E: Sub-process /usr/bin/dpkg returned an error code (1) /var/log/dpkg.log 2014-06-25 14:45:48 install libred5-java:all none 1.0~svn4374-3 2014-06-25 14:45:48 status half-installed libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:48 status unpacked libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:48 status unpacked libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:48 install red5-server:all none 1.0~svn4374-3 2014-06-25 14:45:48 status half-installed red5-server:all 1.0~svn4374-3 2014-06-25 14:45:49 status triggers-pending ureadahead:amd64 0.100.0-16 2014-06-25 14:45:49 status half-installed red5-server:all 1.0~svn4374-3 2014-06-25 14:45:49 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:49 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:49 trigproc ureadahead:amd64 0.100.0-16 0.100.0-16 2014-06-25 14:45:49 status half-configured ureadahead:amd64 0.100.0-16 2014-06-25 14:45:49 status installed ureadahead:amd64 0.100.0-16 2014-06-25 14:45:50 startup packages configure 2014-06-25 14:45:50 configure libred5-java:all 1.0~svn4374-3 none 2014-06-25 14:45:50 status unpacked libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:50 status half-configured libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:50 status installed libred5-java:all 1.0~svn4374-3 2014-06-25 14:45:50 configure red5-server:all 1.0~svn4374-3 none 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:50 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status unpacked red5-server:all 1.0~svn4374-3 2014-06-25 14:45:51 status
[Bug 1332739] [NEW] EXE files and directories confused with cygwin
Public bug reported: This is probably an incompatibility between cygwin and unison that simply should be documented or perhaps have the code produce an error message indicating the likely cause of the problem. Start with a windows machine running cygwin and Unison. (In my case Win7.) Create a tree like the following /mydir/funtask/README.txt /mydir/FUNTASK.EXE Use unison against this directory and sync to a Linux machine You will see it try to create the following on the Linux machine and fail. /mydir/funtask/README.txt /mydir/FUNTASK.EXE /mydir/funtask ; which has the same content as FUNTASK.EXE because obviously /mydir/funtask can't be both a file and a directory at the same time. The error message is Destination updated during synchronization. A .unison file is created as a place holder for the file/directory that was not created. It seems something in unison and the cygwin libraries it uses try to create a funtask file with the same contents as FUNTASK.EXE. If I look back at the PC, neither the ls command in cygwin nor the Windows Explorer shows a funtask file. 'just the directory. If this behavior can't be helped due to the cygwin libraries, then it would be good to document it and/or update the code to at least tell the user what is possibly happening. It would be great to find a way to fix it though because it's such an obscure and unexpected problem, users are unlikely to be able to figure out what's going on without some additional clues. ** Affects: unison (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/1332739 Title: EXE files and directories confused with cygwin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1332739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1201095] Re: gnome-panel crashes after launching steam game (Thomas was alone)
I have the same issues, using Xubuntu 14.04. When ever i launch Steam, the panels freeze. I can still right click, and I have to use the xkill command in the terminal to close the panel, they restart and work fine until i restart steam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201095 Title: gnome-panel crashes after launching steam game (Thomas was alone) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1201095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999191] Re: 10de:0421 X crashes with gnome-session: Fatal IO error 11
Seeing this with a fresh 12.04.4 64-bit installation using ATI graphics. Seems to be triggered by changing user and it frequently breaks VM operations. Typical syslog entry looks like this: Apr 29 14:26:59 john-desktop rtkit-daemon[2183]: Successfully made thread 23506 of process 23506 (n/a) owned by '104' high priority at nice level -11. Apr 29 14:26:59 john-desktop rtkit-daemon[2183]: Supervising 13 threads of 4 processes of 3 users. Apr 29 14:26:59 john-desktop pulseaudio[23506]: [pulseaudio] pid.c: Daemon already running. Apr 29 14:27:10 john-desktop acpid: client 3479[0:0] has disconnected Apr 29 14:27:10 john-desktop acpid: client 23354[0:0] has disconnected Apr 29 14:27:10 john-desktop acpid: client connected from 12940[0:0] Apr 29 14:27:10 john-desktop acpid: 1 client rule loaded Apr 29 14:27:10 john-desktop gnome-session[13151]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 Apr 29 14:27:10 john-desktop acpid: client 12940[0:0] has disconnected Apr 29 14:27:10 john-desktop acpid: client connected from 23546[0:0] Apr 29 14:27:10 john-desktop acpid: 1 client rule loaded Apr 29 14:27:20 john-desktop rtkit-daemon[2183]: Successfully made thread 23810 of process 23810 (n/a) owned by '1001' high priority at nice level -11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999191 Title: 10de:0421 X crashes with gnome-session: Fatal IO error 11 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/999191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217933] Re: update-grub fails to detect other md OS
Seems this bug still is present with the latest grub update, as had to patch /usr/bin/os-prober again to allow dual-boot from MD array. $ apt-cache policy grub2 grub2: Installed: (none) Candidate: 1.99-21ubuntu3.14 Version table: 1.99-21ubuntu3.14 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/universe i386 Packages 1.99-21ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217933 Title: update-grub fails to detect other md OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1217933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-auth-mysql in Ubuntu. https://bugs.launchpad.net/bugs/1243076 Title: libapache2-mod-auth-mysql is missing in 13.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-auth-mysql/+bug/1243076/+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 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243076 Title: libapache2-mod-auth-mysql is missing in 13.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-auth-mysql/+bug/1243076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267620] Re: Ubuntu installer crashes
Memtest fine. Didn't run cd test as not using a CD. Resolved problem in the end. I'd been copying the installer onto USB using dd (as the startup disk creator crashed every time). In the end I removed all partitions from the USB stick, formatted, and then the startup disk creator worked. feel free to close. Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267620 Title: Ubuntu installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267620] [NEW] Ubuntu installer crashes
Public bug reported: Installing onto SSD from live USB. Crashes every time in different ways. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.26 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Date: Thu Jan 9 22:02:06 2014 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubiquity-2.15.26 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267620 Title: Ubuntu installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1267620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64
ok, so in just a few months since I posted my question about this bug, there has now been over 2500 different people viewing it. http://askubuntu.com/questions/365061/ubuntu-13-10-gives-package- libapache2-mod-auth-mysql-has-no-installation-cand This is obviously an issue for a lot of people need this to be fixed. Can we at least have some sort of update to it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243076 Title: libapache2-mod-auth-mysql is missing in 13.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1243076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260321] Re: dpkg-deb unable to install/upgrade oracle-java8-installer
My suggestion is to (ideally) have the later version back-ported to 10.04 so this problem is not an issue for the remaining 1.5 years or so of long term support for such servers, or to make sure Oracle uses the older style of compression so the package is usable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260321 Title: dpkg-deb unable to install/upgrade oracle-java8-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1260321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260321] [NEW] dpkg-deb unable to install/upgrade oracle-java8-installer
Public bug reported: Running a 10.04 LTS machine (32-bit) and it seem that the oracle- java8-installer now uses the more recent compression option that is not supported by the version of dpkg that is currently used by 10.04 Indirectly this is a security risk as java is well known for vulnerabilities and being unable to update a package when it has come through the official repository is a problem! Upon running 'apt-get upgrade' this was the error message: Preparing to replace oracle-java8-installer 8b115-0~webupd8~0 (using .../oracle-java8-installer_8b119-0~webupd8~0_all.deb) ... oracle-license-v1-1 license has already been accepted Unpacking replacement oracle-java8-installer ... dpkg-deb: file `/var/cache/apt/archives/oracle-java8-installer_8b119-0~webupd8~0_all.deb' contains ununderstood data member data.tar.xz , giving up dpkg: error processing /var/cache/apt/archives/oracle-java8-installer_8b119-0~webupd8~0_all.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 System information: $ lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 $ apt-cache policy dpkg dpkg: Installed: 1.15.5.6ubuntu4.6 Candidate: 1.15.5.6ubuntu4.6 Version table: *** 1.15.5.6ubuntu4.6 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 1.15.5.6ubuntu4.5 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 1.15.5.6ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages ** Affects: dpkg (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/1260321 Title: dpkg-deb unable to install/upgrade oracle-java8-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1260321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242678] Re: evince cannot render some EPS files
I've also experienced this bug. Rotation ±90° makes visible, and 0° is always invisible, with the following stderr: (evince:19353): Gtk-WARNING **: drawing failure for widget `EvView': invalid matrix (not invertible) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242678 Title: evince cannot render some EPS files To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1242678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64
I see that there is still no update to this. I do find it puzzling that with so many people using a LAMP environment this is still not fixed on the latest issue of Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243076 Title: libapache2-mod-auth-mysql is missing in 13.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1243076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64
Has there been an update on this? As can been seen here: http://askubuntu.com/questions/365061/ubuntu-13-10-gives-package- libapache2-mod-auth-mysql-has-no-installation-cand in just 3 days, over 100 people have looked at this issue... as such it is impacting a lot of people that are trying to set up a LAMP environment using Ubuntu 13.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243076 Title: libapache2-mod-auth-mysql is missing in 13.10 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1243076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576602] Re: Fancontrol relies on the module load order
Thanks Thomas, that is a much better work-around method! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576602 Title: Fancontrol relies on the module load order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/576602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20915] Re: os-prober doesn't support software RAID
This appears related to Bug #1217933 and I have a basic patch that enables it for mdadm RAID. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/20915 Title: os-prober doesn't support software RAID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/20915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217933] Re: update-grub fails to detect other md OS
I think this applies to the following versions since I first tested the 1.61 version of os-prober to see if it was already fixed (was not) and my patach should work for all of them, though I have only tested on 1.51 1.61: Saucy (1.61ubuntu1) Raring (1.57ubuntu1) Quantal (1.56ubuntu1) Precise (1.51ubuntu3) The patch is not ideal, for example, it has not fixed the on_sataraid() function to avoid probing components of a mdadm array (as it does for dmraid arrays), though later they are skipped if found in /proc/mdstat It also presumes the md arrays are up to be probed. This last point is not unreasonable as activating potential arrays for probing may be hazardous if they had been stopped for other maintenance reasons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217933 Title: update-grub fails to detect other md OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1217933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
