[Desktop-packages] [Bug 1673253] Re: "Screen Display" icon is missing from System Settings
I can confirm that downgrading from 15.04.0+17.04.20170314-0ubuntu1 to 15.04.0+17.04.20170213-0ubuntu1 makes the Display Icon return. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1673253 Title: "Screen Display" icon is missing from System Settings Status in unity-control-center package in Ubuntu: Fix Committed Bug description: After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary drivers out), the Screen Display icon is completely missing from the Systems Settings on my machine. I'd kinda like it back. :/ Please let me know what other info you may need. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 14:35:38 2017 InstallationDate: Installed on 2014-09-22 (905 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1673253] [NEW] "Screen Display" icon is missing from System Settings
Public bug reported: After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary drivers out), the Screen Display icon is completely missing from the Systems Settings on my machine. I'd kinda like it back. :/ Please let me know what other info you may need. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 14:35:38 2017 InstallationDate: Installed on 2014-09-22 (905 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1673253 Title: "Screen Display" icon is missing from System Settings Status in unity-control-center package in Ubuntu: New Bug description: After shoving in a new Nvidia GeForce 8400GS (and trying the proprietary drivers out), the Screen Display icon is completely missing from the Systems Settings on my machine. I'd kinda like it back. :/ Please let me know what other info you may need. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170314-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30~lp1543683LatestXenialWithRevert-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 14:35:38 2017 InstallationDate: Installed on 2014-09-22 (905 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2014-11-14 (852 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1673253/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
After further checking, comcast is sending them, my machine is just not seeing them... Will file a separate bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
I have confirmed that the machine is accepting router advertisements, and that comcast is not sending them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
With this fix, my IPv6 service from Comcast broke. Specifically, they hand out an IP on the /64 via dhcpv6, with the default gateway being an IP on the same /64, along with an IA /56 for the customer to use locally. Adding the default route fails because there is no route to said gateway (since we have decided that we have a /128). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1519518] Re: gsettings-schema-convert has syntax errors
I forget exactly what the error message was, but I think it was the difference between whatever output is, and that write wanted a bytestring. -- it's possibl;e that should be fout.write(unicode(output))... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1519518 Title: gsettings-schema-convert has syntax errors Status in gconf package in Ubuntu: In Progress Bug description: gconf 3.2.6-3ubuntu5 (xenial) has gsettings-schema-convert requiring python3, but without correct syntax: gsettings-schema-convert --force --gconf --xml --schema-id "org.freedesktop.ibus" --output lamont.in ../../data/ibus.schemas.in File "/usr/bin/gsettings-schema-convert", line 606 except GSettingsSchemaConvertException, e: ^ SyntaxError: invalid syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1519518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303835] [NEW] VPN configuration poorly integrated
Public bug reported: NM currently believes that a VPN is a subset of a particular SSID on wireless. That is, that I want different VPNs to come up based on what SSID I have connected to. What this means is that if I have a VPN that I always want to bring up, regardless of where I'm connected, then I have to add that to the configuration of EVERY SINGLE SSID, which guarantees yet one more manual step when I connect at a new coffee shop. Additionally, it only allows one VPN to be brought up. Fortunately, the other two openvpn connections that I spin up are running completely outside of NM, so that bug doesn't actually break things for me. It does, however highlight the fact that I cannot seem to get the openvpn connection inside of NM to seamlessly recover from me switching the underlying network. (as it sits, the vpn to my house quite happily survives me moving from wired-at-one-shop, to wireless-at-another, to wireless-somewhere-else. No existing tcp (ssh) connections fail, despite the 20 minute lag between suspending the laptop at one location and bringing it back up at another. All of which is to say, this is probably 3 separate bugs, at least one of which is an enhancement request. (I would have considered doing the vpn that forced me to NM outside of NM if it weren't for NM overwriting the complete dnsmasq configuration for non-standard TLDs forwarding over the tunnel... But that bug is probably a joint effort by dnsmasq and network manager.) lamont ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1303835 Title: VPN configuration poorly integrated Status in “network-manager-openvpn” package in Ubuntu: New Bug description: NM currently believes that a VPN is a subset of a particular SSID on wireless. That is, that I want different VPNs to come up based on what SSID I have connected to. What this means is that if I have a VPN that I always want to bring up, regardless of where I'm connected, then I have to add that to the configuration of EVERY SINGLE SSID, which guarantees yet one more manual step when I connect at a new coffee shop. Additionally, it only allows one VPN to be brought up. Fortunately, the other two openvpn connections that I spin up are running completely outside of NM, so that bug doesn't actually break things for me. It does, however highlight the fact that I cannot seem to get the openvpn connection inside of NM to seamlessly recover from me switching the underlying network. (as it sits, the vpn to my house quite happily survives me moving from wired-at-one-shop, to wireless- at-another, to wireless-somewhere-else. No existing tcp (ssh) connections fail, despite the 20 minute lag between suspending the laptop at one location and bringing it back up at another. All of which is to say, this is probably 3 separate bugs, at least one of which is an enhancement request. (I would have considered doing the vpn that forced me to NM outside of NM if it weren't for NM overwriting the complete dnsmasq configuration for non-standard TLDs forwarding over the tunnel... But that bug is probably a joint effort by dnsmasq and network manager.) lamont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1303835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303835] Re: VPN configuration poorly integrated
This is network-manager-openvpn 0.9.8.2-1ubuntu4 on trusty. ** Package changed: network-manager (Ubuntu) = network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1303835 Title: VPN configuration poorly integrated Status in “network-manager-openvpn” package in Ubuntu: New Bug description: NM currently believes that a VPN is a subset of a particular SSID on wireless. That is, that I want different VPNs to come up based on what SSID I have connected to. What this means is that if I have a VPN that I always want to bring up, regardless of where I'm connected, then I have to add that to the configuration of EVERY SINGLE SSID, which guarantees yet one more manual step when I connect at a new coffee shop. Additionally, it only allows one VPN to be brought up. Fortunately, the other two openvpn connections that I spin up are running completely outside of NM, so that bug doesn't actually break things for me. It does, however highlight the fact that I cannot seem to get the openvpn connection inside of NM to seamlessly recover from me switching the underlying network. (as it sits, the vpn to my house quite happily survives me moving from wired-at-one-shop, to wireless- at-another, to wireless-somewhere-else. No existing tcp (ssh) connections fail, despite the 20 minute lag between suspending the laptop at one location and bringing it back up at another. All of which is to say, this is probably 3 separate bugs, at least one of which is an enhancement request. (I would have considered doing the vpn that forced me to NM outside of NM if it weren't for NM overwriting the complete dnsmasq configuration for non-standard TLDs forwarding over the tunnel... But that bug is probably a joint effort by dnsmasq and network manager.) lamont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1303835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1229257] [NEW] assertion failure warnings output
Public bug reported: When I run various nova commands, stderr gets assertion failure warnings spewed on it. Unsure if this is a gobject issue, or a nova client issue, so marking it as both. lamot % nova list /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed import gobject._gobject +--+---+++-++ ... (command functions normally other than the extraneous lines.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: python-gobject 3.9.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Mon Sep 23 09:44:37 2013 InstallationDate: Installed on 2013-04-22 (153 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True PackageArchitecture: all SourcePackage: pygobject UpgradeStatus: Upgraded to saucy on 2013-09-17 (5 days ago) ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Affects: python-novaclient (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Also affects: python-novaclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1229257 Title: assertion failure warnings output Status in “pygobject” package in Ubuntu: New Status in “python-novaclient” package in Ubuntu: New Bug description: When I run various nova commands, stderr gets assertion failure warnings spewed on it. Unsure if this is a gobject issue, or a nova client issue, so marking it as both. lamot % nova list /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed import gobject._gobject +--+---+++-++ ... (command functions normally other than the extraneous lines.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: python-gobject 3.9.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Mon Sep 23 09:44:37 2013 InstallationDate: Installed on 2013-04-22 (153 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True PackageArchitecture: all SourcePackage: pygobject UpgradeStatus: Upgraded to saucy on 2013-09-17 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1229257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226141] Re: evince reports apparmor denials
In response to ctl-P: ** (evince:26301): WARNING **: Couldn't connect to D-Bus system bus, GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) ** (evince:26301): WARNING **: failed to contact colord: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1226141 Title: evince reports apparmor denials Status in “evince” package in Ubuntu: Triaged Bug description: % evince foo.pdf ** (evince:26162): WARNING **: Couldn't register with accessibility bus: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) (evince:26162): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed % more errors occur if I print the document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1226141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226141] [NEW] evince reports apparmor denials
Public bug reported: % evince foo.pdf ** (evince:26162): WARNING **: Couldn't register with accessibility bus: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) (evince:26162): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed % more errors occur if I print the document. ** Affects: evince (Ubuntu) Importance: High Assignee: Tyler Hicks (tyhicks) Status: Triaged ** Tags: apparmor ** Changed in: evince (Ubuntu) Assignee: (unassigned) = Tyler Hicks (tyhicks) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1226141 Title: evince reports apparmor denials Status in “evince” package in Ubuntu: Triaged Bug description: % evince foo.pdf ** (evince:26162): WARNING **: Couldn't register with accessibility bus: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call, sender=(null) (inactive) interface=org.freedesktop.DBus member=Hello error name=(unset) requested_reply=0 destination=org.freedesktop.DBus (bus) (evince:26162): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed % more errors occur if I print the document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1226141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171992] Re: raring install does not detect builtin speakers
apport information ** Tags added: apport-collected ** Description changed: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.9.2-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 13.04 + InstallationDate: Installed on 2013-04-22 (7 days ago) + InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) + MarkForUpload: True + Package: alsa-driver (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 + Tags: raring + Uname: Linux 3.8.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm adm cdrom cdrom dip libvirtd lpadmin plugdev sambashare sudo + dmi.bios.date: 09/13/2010 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: 0WXY9J + dmi.board.vendor: Dell Inc. + dmi.board.version: A08 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: A08 + dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/13/2010:svnDellInc.:pnInspironN5010:pvrA08:rvnDellInc.:rn0WXY9J:rvrA08:cvnDellInc.:ct8:cvrA08: + dmi.product.name: Inspiron N5010 + dmi.product.version: A08 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1171992/+attachment/3660321/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-driver” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set
[Desktop-packages] [Bug 1171992] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1171992/+attachment/3660322/+files/BootDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-driver” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True Package: alsa-driver (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 09/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/13/2010:svnDellInc.:pnInspironN5010:pvrA08:rvnDellInc.:rn0WXY9J:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron N5010 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1171992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171992] HookError_cloud_archive.txt
apport information ** Attachment added: HookError_cloud_archive.txt https://bugs.launchpad.net/bugs/1171992/+attachment/3660324/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-driver” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True Package: alsa-driver (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 09/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/13/2010:svnDellInc.:pnInspironN5010:pvrA08:rvnDellInc.:rn0WXY9J:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron N5010 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1171992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171992] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1171992/+attachment/3660323/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-driver” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True Package: alsa-driver (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 09/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/13/2010:svnDellInc.:pnInspironN5010:pvrA08:rvnDellInc.:rn0WXY9J:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron N5010 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1171992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171992] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1171992/+attachment/3660325/+files/PulseList.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-driver” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-04-22 (7 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True Package: alsa-driver (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 09/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WXY9J dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/13/2010:svnDellInc.:pnInspironN5010:pvrA08:rvnDellInc.:rn0WXY9J:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron N5010 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1171992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171992] [NEW] raring install does not detect builtin speakers
Public bug reported: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1171992 Title: raring install does not detect builtin speakers Status in “alsa-utils” package in Ubuntu: New Bug description: lspci -v output: 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Dell Device 0447 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at fbd0 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: snd_hda_intel And yet (from /etc/init/alsa-restore.conf): /usr/sbin/alsactl restore alsactl: load_state:1686: No soundcards found... The machine was originally installed some time ago (oneiric??), and was recently reinstalled for other reasons. if I boot from the old root (raring), then sound works. booting from the freshly installed root does not (sound settings lists only Dummy Output. lamont ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-utils 1.0.25-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 23 13:25:39 2013 InstallationDate: Installed on 2013-04-22 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130422) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1171992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057642] [NEW] missing entries in apparmor profile
Public bug reported: firefox 15.0.1+build1-0ubuntu2 gets apparmor denial messages, and seems to want the following in its apparmor config: /etc/vdpau_wrapper.cfg r, /var/lib/xine/gxine.desktop r, ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1057642 Title: missing entries in apparmor profile Status in “firefox” package in Ubuntu: New Bug description: firefox 15.0.1+build1-0ubuntu2 gets apparmor denial messages, and seems to want the following in its apparmor config: /etc/vdpau_wrapper.cfg r, /var/lib/xine/gxine.desktop r, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1057642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 930367] [NEW] do not run resolvconf when dnsmasq fails to start
Public bug reported: If dnsmasq fails to launch (becuase the binary is missing, say, due to an overly agressive admin), then network manager should not run resolvconf to point at the non-running dnsmasq, since that results in not being able to resolve names. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/930367 Title: do not run resolvconf when dnsmasq fails to start Status in “network-manager” package in Ubuntu: New Bug description: If dnsmasq fails to launch (becuase the binary is missing, say, due to an overly agressive admin), then network manager should not run resolvconf to point at the non-running dnsmasq, since that results in not being able to resolve names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/930367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885211] [NEW] firefox generates apparmor violations
Public bug reported:
Running along minding my own business in firefox, the following errors occur:
Nov 2 09:22:21 host kernel: [50808.599850] type=1400 audit(1320240141.763:51):
apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/sys_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.599873] type=1400 audit(1320240141.763:52):
apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/board_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.599887] type=1400 audit(1320240141.763:53):
apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/bios_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.600112] type=1400 audit(1320240141.763:54):
apparmor=DENIED operation=capable parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]} pid=13092
comm=pulseaudio capability=19 capname=sys_ptrace
Nov 2 09:22:21 host kernel: [50808.600118] type=1400 audit(1320240141.763:55):
apparmor=DENIED operation=ptrace parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]} pid=13092
comm=pulseaudio target=5002
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/885211
Title:
firefox generates apparmor violations
Status in “firefox” package in Ubuntu:
New
Bug description:
Running along minding my own business in firefox, the following errors occur:
Nov 2 09:22:21 host kernel: [50808.599850] type=1400
audit(1320240141.763:51): apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/sys_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.599873] type=1400
audit(1320240141.763:52): apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/board_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.599887] type=1400
audit(1320240141.763:53): apparmor=DENIED operation=open parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]}
name=/sys/devices/virtual/dmi/id/bios_vendor pid=13092 comm=pulseaudio
requested_mask=r denied_mask=r fsuid=2501 ouid=0
Nov 2 09:22:21 host kernel: [50808.600112] type=1400
audit(1320240141.763:54): apparmor=DENIED operation=capable parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]} pid=13092
comm=pulseaudio capability=19 capname=sys_ptrace
Nov 2 09:22:21 host kernel: [50808.600118] type=1400
audit(1320240141.763:55): apparmor=DENIED operation=ptrace parent=13091
profile=/usr/lib/firefox-7.0.1/firefox{,*[^s][^h]} pid=13092
comm=pulseaudio target=5002
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/885211/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 120258] Re: Laptop Battery Time Remaining Outrageously Inaccurate
This is especially annoying since unplugging the laptop from power results in battery critically low, hibernating now!. with the 9 cell battery, OTOH, it just says things like Laptop battery low. Approximately 7 minutes remaining (92%) followed instants later by the indicator claiming 3+ hours remaining. perhaps not being so quick to believe itself would be in order. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/120258 Title: Laptop Battery Time Remaining Outrageously Inaccurate Status in Gnome Powermanager: New Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Ubuntu 7.04 Feisty Fawn Hardware is HP Pavilion DV1000 series (specific DV1588EA) Battery monitor when running on battery reports percentage of battery remaining correctly, but the corresponding remaining time is often fabulously wrong (and can swing between e.g a few minutes to tens of hours in the blink of an eye). /* What I wouldn't give for batteries that can last 14 hours between charges... */ It looks for all the world like the underlying values are being held in storage classes which are too small or where value-wrapping is not being handled quite right... BTW UBUNTU is fantastic; I'm a convert! Keep up the good work! To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/120258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 120258] Re: Laptop Battery Time Remaining Outrageously Inaccurate
The above is on oneiric, with unity (not that it should affect things). ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/120258 Title: Laptop Battery Time Remaining Outrageously Inaccurate Status in Gnome Powermanager: New Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Ubuntu 7.04 Feisty Fawn Hardware is HP Pavilion DV1000 series (specific DV1588EA) Battery monitor when running on battery reports percentage of battery remaining correctly, but the corresponding remaining time is often fabulously wrong (and can swing between e.g a few minutes to tens of hours in the blink of an eye). /* What I wouldn't give for batteries that can last 14 hours between charges... */ It looks for all the world like the underlying values are being held in storage classes which are too small or where value-wrapping is not being handled quite right... BTW UBUNTU is fantastic; I'm a convert! Keep up the good work! To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/120258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
