[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Your SSH support bad crypto: arcfour arcfour128 arcfour256 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
You're SSH also appears exposed to Internet and vulnerable to Logjam, which is exploitable by NSA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Your SSH support bad CBC mode: 3des-cbc aes128-cbc aes192-cbc aes256-cbc blowfish-cbc cast128-cbc rijndael-...@lysator.liu.se -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Your SSH support weak MAC: hmac-md5 hmac-md5-96 hmac-md5-96-...@openssh.com hmac-md5-...@openssh.com hmac-sha1-96 hmac-sha1-96-...@openssh.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
You're leaked inode number: 2261065 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
So, also, ummm yeah, you're also running and end-of-life and insecure version of ubuntu there too dude. ubuntu 13.04 (saucy) is NOT getting any security updates. Should someone exploit it remotely to make that point? ;) Ubuntu 13.10 EOL was July 2014. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Exactly. Say I am the NSA and you are connected to Tor. I know your EMAIL user agent like Thunderbird is leaking data in your mail header, like Time Zone data. I know you are connected to Tor and that I want to associate your IP to your email. I fiddle your Time Zone response data to something esoteric, check all the emails that came in over all Tor connections, and associate you with that connection. Yes. There are even more things you can do as well, like forcing an ETAG or Last-Modified header in order to track the client as it switched from one network to another, eg laptop moved from one insecure network to another. Further, there are surely unknown parsing vulnerabilities in the response data that you will only find out later. HTTPS , especially with HSTS and HPKP makes abusing such issues much harder. Let's Encrypt Everything with HTTPS. Unencrypted HTTP is dead. """ $ curl -s 'http://geoip.ubuntu.com' -D - | egrep '^(Last|ETag)' Last-Modified: Wed, 07 Sep 2011 05:58:25 GMT ETag: "228049-4-4ac53a1e14240" """ References: https://trac.torproject.org/projects/tor/ticket/6314 https://www.chromium.org/Home/chromium-security/client-identification- mechanisms#TOC-Cache-metadata:-ETag-and-Last-Modified https://mortoray.com/2015/05/11/how-http-cache-headers-betray-your- privacy/ https://letsencrypt.org/ ** Bug watch added: trac.torproject.org/projects/tor/ #6314 https://trac.torproject.org/projects/tor/ticket/6314 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Incomplete Bug description: geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+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
Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Surely this is an NSA backdoor :) On Wed, Sep 16, 2015 at 1:26 PM Mateusz Stachowski <49...@bugs.launchpad.net> wrote: > Yes screen gets locked when menus are open since a couple of Unity > releases. > > But right click context menus are a different story. For example when I > have right click menu opened in Nautilus the screen goes blank but when > I move the cursor I see the whole screen and then only after clicking > somwhere screen gets locked. So you can't interact with programs but you > can see everything. > > Also with right click menu in Opera the screen never gets locked. But > right click menu opened in FireFox, Spotify, Ubuntu Web Browser gets > screen locked at the same time it blanks. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1226854). > https://bugs.launchpad.net/bugs/49579 > > Title: > screen doesn't lock when some menu is open > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > -- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in gnome-screensaver package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Status in gnome-screensaver source package in Precise: Confirmed Status in unity source package in Precise: Confirmed Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
OSX is the way to go for sure...sorry for the annoying email alert On Fri, Jun 19, 2015 at 4:32 AM Camil Staps wrote: > Zewbie, what is wrong with you? Did you not read #29 and #35? Do you > have any idea how many people are getting an email when you comment on > this bug? Have a little responsibility. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1405694). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Can't fix binaries without patching On Thu, Jun 18, 2015 at 4:35 PM Pablo wrote: > Could you fix it? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1405694). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Just use Debian. No one considers Ubuntu secure any more after the privacy violations embedded by Canonical. On Thu, Jun 18, 2015 at 12:41 PM rbscy...@yahoo.ca wrote: > That may be so. However, I care. I use Linux as my everyday computer > at home for everything. I use the "LTS" version because I expect less > problems, and don't really know a hell-of-a-lot about the "underneath" > workings of Linux. If this means I have to go to another distribution, > so be it. > > > On 15-06-18 03:09 PM, Kristian Erik Hermansen wrote: > > No vendor cares about linux > > On Thu, Jun 18, 2015 at 11:46 AM Heath wrote: > > > >> This seems to me like a trivial bug fix, is this just nVidia not wanting > >> to devote time to a fix? > >> > >> -- > >> You received this bug notification because you are subscribed to a > >> duplicate bug report (1405694). > >> https://bugs.launchpad.net/bugs/1431753 > >> > >> Title: > >>Nvidia binary driver FTBS due to DKMS layer violation > >> > >> To manage notifications about this bug go to: > >> > >> > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > >> > > -- > > > ** Attachment added: "ronnie6.png" > > https://bugs.launchpad.net/bugs/1431753/+attachment/4416893/+files/ronnie6.png > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1405694). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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
Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
No vendor cares about linux On Thu, Jun 18, 2015 at 11:46 AM Heath wrote: > This seems to me like a trivial bug fix, is this just nVidia not wanting > to devote time to a fix? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1405694). > https://bugs.launchpad.net/bugs/1431753 > > Title: > Nvidia binary driver FTBS due to DKMS layer violation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
This issue appeared for me when I was running an older kernel that was no longer in the latest repositories. Once I installed and rebooted into the most recent kernel the driver installed fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" Status in nvidia-graphics-drivers-331 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Triaged Bug description: Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257/+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 1405694] [NEW] nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build
Public bug reported: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Thu Dec 25 14:48:10 2014 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-11-08 (47 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1405694 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-uvm 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Thu Dec 25 14:48:10 2014 PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331-uvm 331.113-0ubuntu0.1: nvidia-331-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-11-08 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405694/+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 936712] Re: NetworkManager should put IPv6 DNS servers before IPv4 DNS servers in dnsmasq configuration (and possibly resolv.conf)
I also confirm the bug again in Trusty and Utopic -- 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/936712 Title: NetworkManager should put IPv6 DNS servers before IPv4 DNS servers in dnsmasq configuration (and possibly resolv.conf) Status in “network-manager” package in Ubuntu: Fix Released Bug description: In cases where you are indeed on a dual-stack network and received DNS information from either SLAAC or DHCPv6, these should be used before any equivalent IPv4 data (usually a fallback/compatibility layer in such environment). As an example, here's my generated /run/nm-dns-dnsmasq.conf on an up to date 12.04 system: server=172.17.20.30 server=172.17.25.30 server=172.16.20.32 server=2001:470:c364:1020:e084:d1ff:fe38:c4f5 server=2001:470:c364:1025:8837:98ff:fe43:90e6 server=2001:470:b4e9:1020:218:51ff:fe5a:9949 The result is that dnsmasq will only use the IPv6 dns servers if all 3 IPv4 dns servers are marked as failed. As dnsmasq is perfectly able to detect and avoid broken DNS servers, favoritizing IPv6 servers shouldn't cause any damage even in environment where the information received by NM is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/936712/+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
Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Gael -- Correct. Makes you wonder if this is ever going to be fixed since it is well known for many years... On Sun, Nov 9, 2014, 7:30 PM Gael Lafond <49...@bugs.launchpad.net> wrote: > This bug also occur with contextual menu. Right click anywhere and wait. > The screen goes black after a while. Move the mouse to activate the > screen. The screen is NOT lock. Strangely, the screen lock immediately > after the menu disappear (left click anywhere outside the menu). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1226854). > https://bugs.launchpad.net/bugs/49579 > > Title: > screen doesn't lock when some menu is open > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Confirmed Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Status in “gnome-screensaver” source package in Precise: Confirmed Status in “unity” source package in Precise: Confirmed Status in “xorg-server” package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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
Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Yes. Remove it since it is a decade long bug. -- Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://profiles.google.com/kristian.hermansen On Nov 4, 2013 9:20 PM, "encompass" wrote: > So are you proposing we get rid of the autolock functionality because we > can't solve this bug? Or is there some other solution your providing here? > > > On Tue, Nov 5, 2013 at 6:58 AM, Kristian Erik Hermansen < > kristian.herman...@gmail.com> wrote: > > > Yes but that idle lock feature doesn't work and cannot be trusted. It > would > > be like saying trust SSL but its using a NULL cipher... > > > > -- > > Kristian Erik Hermansen > > https://www.linkedin.com/in/kristianhermansen > > https://profiles.google.com/kristian.hermansen > > On Nov 4, 2013 8:55 PM, "encompass" wrote: > > > > > I totally disagree. > > > The computer should lock automatically when idle. Instead of solving > the > > > problem you want to get rid of the feature. > > > There are times when people are distracted and walk away from the > > > computer. If someone wanted to be malicious this would be their > > > opportunity. Just do a little "Kevin Mitnik" and your in. > > > > > > > > > On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen < > > > kristian.herman...@gmail.com> wrote: > > > > > > > Tony -- exactly! Perfect analysis. Its a false sense of security > which > > > > should be abolished or rectified. > > > > > > > > -- > > > > Kristian Erik Hermansen > > > > https://www.linkedin.com/in/kristianhermansen > > > > https://profiles.google.com/kristian.hermansen > > > > On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote: > > > > > > > > > I don't have a problem with manually locking the screen, especially > > as > > > I > > > > > have worked in secure Defence facilities where that is standard > > > > > pracrtice. > > > > > > > > > > But I do have a problem with a software interface that falsely > claims > > > to > > > > > provide a facility which in fact doesn't work correctly if at all. > > > > > > > > > > To eliminate the immediate problem, distros could get rid of the > > broken > > > > > "Lock" setting from the settings menu, and instead just add a > notice > > > > > that CTRL-ALT-L (or whatever) will lock the screen. > > > > > > > > > > The security issue is not that there isn't an effective automatic > > lock, > > > > > but that the software creates a false and misleading impression > that > > > > > such a facility exists. That part of the problem could surely be > > fixed > > > > > easily by changing the setting dialog box as suggested. > > > > > > > > > > My programming days are long over (anyone remember assembly > > language?), > > > > > and I don't know what is involved in removing the "Lock" setting > from > > > > > the Screensaver/Lock dialog box. If I did know, I'd do it myself. > > > > > > > > > > -- > > > > > You received this bug notification because you are subscribed to a > > > > > duplicate bug report (1226854). > > > > > https://bugs.launchpad.net/bugs/49579 > > > > > > > > > > Title: > > > > > screen doesn't lock when some menu is open > > > > > > > > > > To manage notifications about this bug go to: > > > > > > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > > > > > > > > > > > > > -- > > > > You received this bug notification because you are subscribed to a > > > > duplicate bug report (139405). > > > > https://bugs.launchpad.net/bugs/49579 > > > > > > > > Title: > > > > screen doesn't lock when some menu is open > > > > > > > > To manage notifications about this bug go to: > > > > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > > > > > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (1226854). > > > https://bugs.launchpad.net/bugs/49579 &g
Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Yes but that idle lock feature doesn't work and cannot be trusted. It would be like saying trust SSL but its using a NULL cipher... -- Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://profiles.google.com/kristian.hermansen On Nov 4, 2013 8:55 PM, "encompass" wrote: > I totally disagree. > The computer should lock automatically when idle. Instead of solving the > problem you want to get rid of the feature. > There are times when people are distracted and walk away from the > computer. If someone wanted to be malicious this would be their > opportunity. Just do a little "Kevin Mitnik" and your in. > > > On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen < > kristian.herman...@gmail.com> wrote: > > > Tony -- exactly! Perfect analysis. Its a false sense of security which > > should be abolished or rectified. > > > > -- > > Kristian Erik Hermansen > > https://www.linkedin.com/in/kristianhermansen > > https://profiles.google.com/kristian.hermansen > > On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote: > > > > > I don't have a problem with manually locking the screen, especially as > I > > > have worked in secure Defence facilities where that is standard > > > pracrtice. > > > > > > But I do have a problem with a software interface that falsely claims > to > > > provide a facility which in fact doesn't work correctly if at all. > > > > > > To eliminate the immediate problem, distros could get rid of the broken > > > "Lock" setting from the settings menu, and instead just add a notice > > > that CTRL-ALT-L (or whatever) will lock the screen. > > > > > > The security issue is not that there isn't an effective automatic lock, > > > but that the software creates a false and misleading impression that > > > such a facility exists. That part of the problem could surely be fixed > > > easily by changing the setting dialog box as suggested. > > > > > > My programming days are long over (anyone remember assembly language?), > > > and I don't know what is involved in removing the "Lock" setting from > > > the Screensaver/Lock dialog box. If I did know, I'd do it myself. > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (1226854). > > > https://bugs.launchpad.net/bugs/49579 > > > > > > Title: > > > screen doesn't lock when some menu is open > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > > > > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (139405). > > https://bugs.launchpad.net/bugs/49579 > > > > Title: > > screen doesn't lock when some menu is open > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1226854). > https://bugs.launchpad.net/bugs/49579 > > Title: > screen doesn't lock when some menu is open > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Confirmed Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in X.Org X server: Confirmed Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “gnome-screensaver” source package in Precise: Confirmed Status in “xorg-server” package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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
Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
Tony -- exactly! Perfect analysis. Its a false sense of security which should be abolished or rectified. -- Kristian Erik Hermansen https://www.linkedin.com/in/kristianhermansen https://profiles.google.com/kristian.hermansen On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote: > I don't have a problem with manually locking the screen, especially as I > have worked in secure Defence facilities where that is standard > pracrtice. > > But I do have a problem with a software interface that falsely claims to > provide a facility which in fact doesn't work correctly if at all. > > To eliminate the immediate problem, distros could get rid of the broken > "Lock" setting from the settings menu, and instead just add a notice > that CTRL-ALT-L (or whatever) will lock the screen. > > The security issue is not that there isn't an effective automatic lock, > but that the software creates a false and misleading impression that > such a facility exists. That part of the problem could surely be fixed > easily by changing the setting dialog box as suggested. > > My programming days are long over (anyone remember assembly language?), > and I don't know what is involved in removing the "Lock" setting from > the Screensaver/Lock dialog box. If I did know, I'd do it myself. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1226854). > https://bugs.launchpad.net/bugs/49579 > > Title: > screen doesn't lock when some menu is open > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Confirmed Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in X.Org X server: Confirmed Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “gnome-screensaver” source package in Precise: Confirmed Status in “xorg-server” package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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
Re: [Desktop-packages] [Bug 330310] Re: no logs or log files in vino
This bug appears to be a huge security problem that allows remote clipboard access. Vino should be considered insecure and untrustworthy. References: http://www.ubuntu.com/usn/usn-1701-1 On Apr 19, 2012 5:30 PM, "JeffV" wrote: > Exactly the same as everyone else: forgot about PnP, forgot that vino > was enabled. Had an intrusion I spotted, but there's no log. > > It's quite unbelievable that vino does not have a log, and I wouldn't > call this a wishlist item. I'd call it a critical security issue. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/330310 > > Title: > no logs or log files in vino > > To manage notifications about this bug go to: > https://bugs.launchpad.net/vino/+bug/330310/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/330310 Title: no logs or log files in vino Status in GNOME Remote Desktop: In Progress Status in “vino” package in Ubuntu: Confirmed Bug description: Hello, This is on a fully updated Ubuntu Hardy. It appears that Vino does not save any logs anywhere in /var/log directory. I was not able find any logs in ~/ directory either. Logs files are extremely useful in debugging if something went wrong or to audit a system to examine a security breach. It would be great idea if logging feature is enable in Vino and logs are obtained either in /var/log or ~/.vino directories somewhere. Regards. ->HS To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/330310/+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 794782] Re: Sound stops working after a while on 12.04
Seems to be affecting 12.10 as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/794782
Title:
Sound stops working after a while on 12.04
Status in “pulseaudio” package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
After some random amount of time, sound is lost completely in Natty.
The applications outputting sounds continue to run as normal.
Forcing suspend/resume brings audio back.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: pulseaudio 1:0.9.22+stable-queue-24-g67d18-0ubuntu3.1
Uname: Linux 2.6.39-02063901-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marc 2352 F pulseaudio
/dev/snd/pcmC0D0p: marc 2352 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 44'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:14f15069,17aa2156,00100302
HDA:80862804,17aa21b5,0010'
Controls : 12
Simple ctrls : 6
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
6QHT30WW-1.11'
Mixer name : 'ThinkPad EC 6QHT30WW-1.11'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Wed Jun 8 20:41:45 2011
EcryptfsInUse: Yes
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET52WW (1.22 )
dmi.board.name: 5129CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 5129CTO
dmi.product.version: ThinkPad X201s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/794782/+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
