[Desktop-packages] [Bug 2042772] Re: [amdgpu] Display corrupted/freeze
Just a note to say that it still occurs with version 5.15.0-89 of the kernel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042772 Title: [amdgpu] Display corrupted/freeze Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 2042772] Re: [amdgpu] Display corrupted/freeze
I asked the askubuntu question here: https://askubuntu.com/questions/1492364/ubuntu-22-04-3-lts-gui-does-not- work-with-5-15-0-88-generic for the same error using 22.04.3 (jammy) on an HP 15-db0598sa laptop, which has a AMD Radeon R4 Graphics Integrated graphics card. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042772 Title: [amdgpu] Display corrupted/freeze Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 1971242] Re: printing PDF appears always grey, no color
There's now CUPS 2.4.4 with a hotfix for a segfault. https://github.com/OpenPrinting/cups/releases/tag/v2.4.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 1971242] Re: printing PDF appears always grey, no color
CUPS 2.4.3 has been released, which should fix this problem. https://github.com/OpenPrinting/cups/releases/tag/v2.4.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 1936769] Re: [Braswell] HDMI monitors don't work when powered off and on again
I think this might be a monitor problem. I swapped the VGA and HDMI monitors and the system now comes back up as it should BUT I have done this before and then it went bad again. I think the next thing is to see if the Lenovo monitor has a software upgrade but their website is down, so wait and see I guess. Regards, Graeme. On Tue, Jul 20, 2021 at 11:05 AM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > The first thing we need to do is check to see if this is a Xorg-specific > bug. Please try logging out (or rebooting) and select 'Ubuntu on > Wayland' on the login screen (button in the bottom right corner). After > you do that, does this bug still occur? > > > ** Summary changed: > > - [Braswell] HDMI not working properly > + [Braswell] HDMI monitors don't work when powered off and on again > > ** Changed in: linux-hwe-5.8 (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI monitors don't work when powered off and on again > > Status in linux-hwe-5.8 package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-x
Re: [Desktop-packages] [Bug 1936769] Re: [Braswell] HDMI monitors don't work when powered off and on again
Thanks again for your reply For some reason I nearly missed your email, Google sent it to Promotions and I only found it because it came up on my phone. Cold reboot does not show the option of Wayland but logging out did but the HDMI still failed to come up. I also tried running both Bionic Beaver and Xubuntu from DVD but the problem still existed. This makes me wonder if somehow it is a computer problem; although HP is said to be maximized for Ubuntu. When it was current BB worked OK. It is only since upgrade the problem has existed. Hope you have some more thoughts on the matter. Thanks again, Graeme On Tue, Jul 20, 2021 at 11:05 AM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > The first thing we need to do is check to see if this is a Xorg-specific > bug. Please try logging out (or rebooting) and select 'Ubuntu on > Wayland' on the login screen (button in the bottom right corner). After > you do that, does this bug still occur? > > > ** Summary changed: > > - [Braswell] HDMI not working properly > + [Braswell] HDMI monitors don't work when powered off and on again > > ** Changed in: linux-hwe-5.8 (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI monitors don't work when powered off and on again > > Status in linux-hwe-5.8 package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl
Re: [Desktop-packages] [Bug 1936769] Re: [Braswell] HDMI not working properly
Thank you so much for your prompt reply; unfortunately it leaves me no further ahead. To clarify I run my system on solar power - battery/inverter, it's much cleaner than the grid around here, and cheaper. The computer is left turned on all the time but the monitors (2) are turned off to save power. When the monitors are turned back on HDMI does not come up. It used to on older versions of Ubuntu but not now. Hope this makes it a bit clearer. On Mon, Jul 19, 2021 at 1:55 PM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > Although I don't fully understand the bug description, I do wonder if > there's a Braswell regression given bug 1935901 also. > > ** Summary changed: > > - HDMI not working properly > + [Braswell] HDMI not working properly > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Also affects: xorg-server (Ubuntu) >Importance: Undecided >Status: New > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI not working properly > > Status in linux-hwe-5.8 package in Ubuntu: > New > Status in mutter package in Ubuntu: > New > Status in xorg-server package in Ubuntu: > New > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1936769/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which i
[Desktop-packages] [Bug 1936769] [NEW] HDMI not working properly
Public bug reported: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] InstallationDate: Installed on 2020-11-05 (255 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP 510-a112a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2018 dmi.bios.release: 5.11 dmi.bios.vendor: AMI dmi.bios.version: F.33 dmi.board.asset.tag: CNV7380P8W dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV7380P8W dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-a112a dmi.product.sku: W2S68AA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1936769 Title: HDMI not working properly Status in xorg package in Ubuntu: New Bug description: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Bug exists in 20.10 too, I just triggered it. It happened after screen lock/unlock cycle. Like other restart got rid of it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1726163] Re: pixma displays generic I/O error when scanner carriage is locked
> Hoping to save the next poor soul some grief :) Thank you! Yes, scanimage -T should certainly display the response from the scanner by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1726163 Title: pixma displays generic I/O error when scanner carriage is locked Status in sane-backends package in Ubuntu: Confirmed Bug description: trying to get a brand new Canon Canoscan 9000F Mark II working on my father-in-law's Ubuntu 16.04.2 system. 'scanimage -L' works 'scanimage -T' returns an I/O error I spent quite a while trying to debug an I/O error, trying different versions of libsane etc. even after I set various SANE_DEBUG env vars I still missed the text in the response XML message, ScannerCarriageLockError. I'm ~16,000km away from this scanner so I didn't notice my father-in-law hadn't unlocked it after setting it up. Without setting SANE_DEBUG env vars there's no way anyone is going to guess this from the output from scanimage. Hoping to save the next poor soul some grief :) # sane-find-scanner | grep ^found found USB scanner (vendor=0x04a9 [Canon], product=0x190d [CanoScan]) at libusb:001:009 # scanimage -L device `pixma:04A9190D' is a CANON Canoscan 9000F Mark II multi-function peripheral $ sane-find-scanner | grep ^found found USB scanner (vendor=0x04a9 [Canon], product=0x190d [CanoScan]) at libusb:001:009 $ scanimage -L device `pixma:04A9190D' is a CANON Canoscan 9000F Mark II multi-function peripheral looks good so far. # scanimage -T FAIL Error: Error during device I/O # export SANE_DEBUG_PIXMA=10 # scanimage -T [sanei_debug] Setting debug level of pixma to 10. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.37 [pixma] pixma_collect_devices() found Canoscan 9000F Mark II at libusb:001:009 [pixma] WARNING:No serial number [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canoscan 9000F Mark II at libusb:001:009 [pixma] WARNING:No serial number [pixma] pixma_open(): Canoscan 9000F Mark II [pixma] Reader task started [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=1678578 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x877 [pixma] gamma_table=0x23580a8 source=0 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] OUT T=10.608 len=288 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] .. [pixma] ... [pixma] [pixma] Reader task id=140421529040640 (threaded) scanimage: scanning image of size 638x877 pixels at 24 bits/pixel scanimage: acquiring RGB frame, 8 bits/sample scanimage: reading one scanline, 1914 bytes... [pixma] IN T=10.611 len=391 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] .. [pixma] ... [pixma] XML message sent to scanner: http://www.canon.com/ns/cmd/2008/07/common/";>StartJob00011 [pixma] XML response back from scanner: http://www.canon.com/ns/cmd/2008/07/common/";> StartJobResponse NG ScannerCarriageLockError [pixma] pixma_scan() failed EPROTO [pixma] Reader task terminated: EPROTO [pixma] read_image():reader task closed the pipe:0 bytes received, 1678578 bytes expected FAIL Error: Error during device I/O [pixma] pixma_close(): Canoscan 9000F Mark II # lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 # apt-cache policy libsane libsane: Installed: 1.0.27-xenial1 Candidate: 1.0.27-xenial1 Version table: *** 1.0.27-xenial1 500 500 http://ppa.launchpad.net/rolfbensch/sane-release/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1.0.25+git20150528-1ubuntu2.16.04.1 500 500 http://au.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 1.0.25+git20150528-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1726163/+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 1757208] Re: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block()
** Information type changed from Private to Private Security ** Information type changed from Private Security to Public ** Information type changed from Public to Private ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757208/+attachment/5085156/+files/JournalErrors.txt ** Attachment added: "JournalErrors.txt (personal info removed)" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757208/+attachment/5086947/+files/JournalErrors.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757208 Title: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block() Status in udisks2 package in Ubuntu: New Bug description: I unmounted a single USB disk, and all others disappeared off the desktop with it. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 16:47:19 2018 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2018-02-13 (35 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Precision Tower 3420 ProcCmdline: /usr/lib/udisks2/udisksd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x55a0cf0fb92a : mov0x18(%rax),%rdi PC (0x55a0cf0fb92a) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: udisks_linux_drive_object_get_block () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in udisks_linux_drive_object_get_block() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 08K0X7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn08K0X7:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757208/+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 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
** Also affects: gnome-session Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup Status in gnome-session: New Status in gnome-session package in Ubuntu: Confirmed Bug description: I submitted this question a week but did not receive an answer or advice to solving them. https://answers.launchpad.net/ubuntu/+source /gnome-session/+question/293479 These failures are still plaguing my syslog every time I activate Nautilus. Appreciate help to resolve these failures. Earlier question After a recent updating, I notice these failures in the systemlogs. May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: (zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed May 9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed The last three failures appears whenever I activate nautilus. Nautilus will appear and work as usual. How can I resolve these failure notices? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1582496/+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 1639180] Re: no login possible after update to nvidia 304.132
Solved for me on Xenial. nvidia-304 upgraded to 304.134-0ubuntu0.16.04.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Triaged Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Fix Released Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1511703] Re: Standby timeout setting ignored after system suspend/resume
1. Yes, if /lib/systemd/system-sleep/ doesn't exist, create it with mkdir. 2. Yes. 3. No, unless for some reason you want to limit the script to suspend only, or something. Here's my script: #!/bin/sh case $1/$2 in pre/*) ;; post/*) hdparm -B 254 -S 120 /dev/sdb ;; esac 4. Yes, with chmod u+x . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1511703 Title: Standby timeout setting ignored after system suspend/resume Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: If a standby timeout setting is applied in Drive Settings, this works fine at first when the setting is made, and after the system is rebooted. However, if the system is suspended and resumed, the timeout setting is ignored and the disk continues to spin. Using Ubuntu 15.10, gnome-disk-utility 3.16.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1511703/+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 1511703] Re: Standby timeout setting ignored after system suspend/resume
See also https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/comments/29 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1511703 Title: Standby timeout setting ignored after system suspend/resume Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: If a standby timeout setting is applied in Drive Settings, this works fine at first when the setting is made, and after the system is rebooted. However, if the system is suspended and resumed, the timeout setting is ignored and the disk continues to spin. Using Ubuntu 15.10, gnome-disk-utility 3.16.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1511703/+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 1511468] Re: udisksctl doesn't accept absolute object-paths
Reported in https://bugs.freedesktop.org/show_bug.cgi?id=92746 ** Bug watch added: freedesktop.org Bugzilla #92746 https://bugs.freedesktop.org/show_bug.cgi?id=92746 ** Also affects: udisks via https://bugs.freedesktop.org/show_bug.cgi?id=92746 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1511468 Title: udisksctl doesn't accept absolute object-paths Status in udisks: Unknown Status in udisks2 package in Ubuntu: New Bug description: If I issue "udisksctl dump" and then issue "udisksctl info" for one of the objects in the dump, I get an error message. For instance: $ udisksctl info --object-path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q (udisksctl info:4995): GLib-GIO-CRITICAL **: g_dbus_object_manager_get_object: assertion 'g_variant_is_object_path (object_path)' failed Error looking up object with path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q This is confusing. It turns out that object paths must be relative to /org/freedesktop/UDisks2. For instance: $ udisksctl info --object-path drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q: org.freedesktop.UDisks2.Drive: [snip] I don't know if this is a bug in the executable or in the man page. In either case, I suggest it would be very helpful to state in udisksctl(1) that relative object paths must/can (whichever it is) be used. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1511468/+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 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?
I've given up on hdparm.conf now. As noted in #27, it seems that systemd
and udev/udisks2 is the way to go, but it's not clear how exactly.
Here's what I've done. This bug report isn't the ideal place to document
it, but I can't find a better place for now. Maybe it'll help someone
who finds it through a search engine.
The Ubuntu Disks utility (not in the Launcher by default) allows
configuration of the spindown/standby time and other settings. (See
below for Kubuntu.) Click on the disk in the left-hand pane, then click
the "hamburger" icon at the top right and select Drive Settings.
Great! Except... what it says in the title of this bug. Also:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1511703
I fixed this by coding a sleep script as shown in
https://wiki.archlinux.org/index.php/Power_management#Hooks_in_.2Fusr.2Flib.2Fsystemd.2Fsystem-sleep
Note the directory in Ubuntu is /lib/systemd/system-sleep/, which is different
from Arch Linux.
In the "post/*" case I simply coded the required hdparm command
directly, e.g.
hdparm -B 254 -S 120 /dev/sdb
I'd earlier tried to make hdparm.conf work by emulating the pmutils
scripts by coding, e.g.,
DEVNAME=/dev/sdb /lib/udev/hdparm
but that didn't work for some reason. I don't think I worked out why.
Kubuntu users (like me) and others who don't have the Ubuntu Disks
utility available need to write a config file (which, of course, is what
hdparm.conf is) to set the post-boot spindown time, etc. See udisks(8)
for the format of the file /etc/udisks2/IDENTIFIER.conf, the file which
the Disks utility writes. For instance:
[ATA]
APMLevel=254
StandbyTimeout=120
What is IDENTIFIER? Run "udisksctl dump" (the output is piped to less) and look
for an object path starting "/org/freedesktop/UDisks2/drives/" with your drive
model and serial number. Within the org.freedesktop.UDisks2.Drive interface
underneath that, the Id property is the required IDENTIFIER part of the
filename. See
http://udisks.freedesktop.org/docs/latest/gdbus-org.freedesktop.UDisks2.Drive.html#gdbus-property-org-freedesktop-UDisks2-Drive.Id
So it seems that in 2015, it's a bit more complicated than writing
/etc/hdparm.conf. It seems (unless there's currently a better way) it's
necessary to specify the hdparm settings for the post-boot and post-
resume conditions in two different ways.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/199094
Title:
hdparm.conf settings (other than apm) are lost on suspend/resume?
Status in hdparm package in Ubuntu:
Confirmed
Status in pm-utils package in Ubuntu:
Confirmed
Bug description:
Update: This is on Intrepid.
Problem:
- Hard disks lose settings (the APM level for example) when they are powered
off.
=> Settings in /etc/hdparm.conf persist only from boot to next suspend.
Expected:
All settings in /etc/hdparm.conf should persist across
{suspend,hibernate}/resume.
Effects:
At least the apm setting in hdparm.conf is lost. This makes
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad -
users are not able to set the apm value without messing with their system
(installing stuff from forums) because of this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/+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 1511703] [NEW] Standby timeout setting ignored after system suspend/resume
Public bug reported: If a standby timeout setting is applied in Drive Settings, this works fine at first when the setting is made, and after the system is rebooted. However, if the system is suspended and resumed, the timeout setting is ignored and the disk continues to spin. Using Ubuntu 15.10, gnome-disk-utility 3.16.2. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1511703 Title: Standby timeout setting ignored after system suspend/resume Status in gnome-disk-utility package in Ubuntu: New Bug description: If a standby timeout setting is applied in Drive Settings, this works fine at first when the setting is made, and after the system is rebooted. However, if the system is suspended and resumed, the timeout setting is ignored and the disk continues to spin. Using Ubuntu 15.10, gnome-disk-utility 3.16.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1511703/+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 1511468] [NEW] udisksctl doesn't accept absolute object-paths
Public bug reported: If I issue "udisksctl dump" and then issue "udisksctl info" for one of the objects in the dump, I get an error message. For instance: $ udisksctl info --object-path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q (udisksctl info:4995): GLib-GIO-CRITICAL **: g_dbus_object_manager_get_object: assertion 'g_variant_is_object_path (object_path)' failed Error looking up object with path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q This is confusing. It turns out that object paths must be relative to /org/freedesktop/UDisks2. For instance: $ udisksctl info --object-path drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q: org.freedesktop.UDisks2.Drive: [snip] I don't know if this is a bug in the executable or in the man page. In either case, I suggest it would be very helpful to state in udisksctl(1) that relative object paths must/can (whichever it is) be used. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1511468 Title: udisksctl doesn't accept absolute object-paths Status in udisks2 package in Ubuntu: New Bug description: If I issue "udisksctl dump" and then issue "udisksctl info" for one of the objects in the dump, I get an error message. For instance: $ udisksctl info --object-path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q (udisksctl info:4995): GLib-GIO-CRITICAL **: g_dbus_object_manager_get_object: assertion 'g_variant_is_object_path (object_path)' failed Error looking up object with path /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q This is confusing. It turns out that object paths must be relative to /org/freedesktop/UDisks2. For instance: $ udisksctl info --object-path drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q /org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S223Q_TSSTcorp_CDDVDW_SH_S223Q: org.freedesktop.UDisks2.Drive: [snip] I don't know if this is a bug in the executable or in the man page. In either case, I suggest it would be very helpful to state in udisksctl(1) that relative object paths must/can (whichever it is) be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1511468/+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 1507003] Re: Too fast "housekeeping" prevents harddrive from sleeping
See also https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1281588/comments/11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1507003 Title: Too fast "housekeeping" prevents harddrive from sleeping Status in udisks2 package in Ubuntu: New Bug description: udisks2 has a function called housekeeping where regular stuff is done. In example refreshing SMART data from attached drives. Currently it has a timeout of ten minutes. The old udisks(1) was more relax and waited thirty minutes. Therefore I have to let my drives sleep after ten minutes at maximum before SMART data is fetched. Usually this is a bit fast. I´m unsure whether desktop drives like these tight cycles as laptop devices do. If anybody thinks like me, patching is easy. Have a look at "udiskslinuxprovider.c" in the src folder. Around line 470 is the "housekeeping timeout" set to 10*60 seconds. Reset to a value you like and recompile the package. I guess it won´t harm, if you update SMART every thirty minutes instead of ten :) Description:Ubuntu 14.04.3 LTS Release:14.04 udisks2: Installiert: 2.1.3-1ubuntu0.1 Installationskandidat: 2.1.3-1ubuntu0.1 Paket-Pinning: 2.1.3-1ubuntu0.1 Versionstabelle: *** 2.1.3-1ubuntu0.1 1001 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.1.3-1 1001 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1507003/+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 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?
Also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412
** Bug watch added: Debian Bug tracker #725284
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284
** Bug watch added: Debian Bug tracker #779412
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/199094
Title:
hdparm.conf settings (other than apm) are lost on suspend/resume?
Status in hdparm package in Ubuntu:
Confirmed
Status in pm-utils package in Ubuntu:
Confirmed
Bug description:
Update: This is on Intrepid.
Problem:
- Hard disks lose settings (the APM level for example) when they are powered
off.
=> Settings in /etc/hdparm.conf persist only from boot to next suspend.
Expected:
All settings in /etc/hdparm.conf should persist across
{suspend,hibernate}/resume.
Effects:
At least the apm setting in hdparm.conf is lost. This makes
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad -
users are not able to set the apm value without messing with their system
(installing stuff from forums) because of this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/+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 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?
I'm experiencing this in 15.04. With the change to systemd, the pm-utils
scripts are no longer run when the system resumes after suspend.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/199094
Title:
hdparm.conf settings (other than apm) are lost on suspend/resume?
Status in hdparm package in Ubuntu:
Confirmed
Status in pm-utils package in Ubuntu:
Confirmed
Bug description:
Update: This is on Intrepid.
Problem:
- Hard disks lose settings (the APM level for example) when they are powered
off.
=> Settings in /etc/hdparm.conf persist only from boot to next suspend.
Expected:
All settings in /etc/hdparm.conf should persist across
{suspend,hibernate}/resume.
Effects:
At least the apm setting in hdparm.conf is lost. This makes
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad -
users are not able to set the apm value without messing with their system
(installing stuff from forums) because of this bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/199094/+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 1409110] Re: nvidia binary driver leaks vram like crazy
Just retested on a fresh install of 15.04 x64 with the nvidia-346 drivers, problem still exists. In between the two nvidia-smi runs shown, I just switched to the text console with ctl-alt-f1, and then switched back to X. graeme@galvatron:~⟫ nvidia-smi Tue Aug 11 15:48:00 2015 +--+ | NVIDIA-SMI 346.59 Driver Version: 346.59 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 960 Off | :01:00.0 N/A | N/A | | 0% 58CP8N/A / N/A | 1148MiB / 2047MiB | N/A Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0C+G Not Supported | +-+ graeme@galvatron:~⟫ nvidia-smi Tue Aug 11 15:48:08 2015 +--+ | NVIDIA-SMI 346.59 Driver Version: 346.59 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 960 Off | :01:00.0 N/A | N/A | | 0% 59CP0N/A / N/A |526MiB / 2047MiB | N/A Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0C+G Not Supported | +-+ ** Also affects: nvidia-graphics-drivers-346 (Ubuntu) Importance: Undecided Status: New -- 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/1409110 Title: nvidia binary driver leaks vram like crazy Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-346 package in Ubuntu: New Bug description: Using the nvidia-smi tool, you can see how much VRAM the binary driver is using for the card. However, with the current latest driver in Ubuntu 14.10, the results aren't good. Just using desktop apps (no OpenGL apart from what Unity and Chrome naturally use), and the driver has consumed over a GB of VRAM: graeme@galvatron:~⟫ sudo nvidia-smi [sudo] password for graeme: Fri Jan 9 11:58:06 2015 +--+ | NVIDIA-SMI 331.38 Driver Version: 331.38 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 570 Off | :01:00.0 N/A | N/A | | 40% 43C N/A N/A / N/A | 1047MiB / 1279MiB | N/A Default | +---+--+--+ +-+ | Compute processes: GPU Memory | | GPU PID Process name Usage | |=| |
[Desktop-packages] [Bug 1307723] Re: Ubuntu 14.04 Freezes completely - Power Button Reset
Hi, I have this same problem, can anyone help please? Im running an ATI Radeon Cedar HD5450 graphics card and using the open source driver, I've tried a fresh install of Unity. The freeze mainly happens when I'm using Video, so I figured it would probably be something to do with the Graphics card. If I need to post logs or any other info, just let me know and thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1307723 Title: Ubuntu 14.04 Freezes completely - Power Button Reset Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: I dont't really know if it is a xorg problem, because my knowledges about tecnical details is short! I'm on Ubuntu 14.04 Gnome Beta2 64 Bits fresh install. This freezes start it out with Ubuntu 11.04! It got worst! I have beeing using Elementary and Manjaro. But I prefer Ubuntu! I don't know if you care about a single user or not, but I do hope so! The freezes in the last 2 to 3 days are very weird! Today it force me to use the Power Button do restart 4 (that's four!) times! For now, I have being using it non stop for 4 hours. But it was the same thing since friday! Before friday, it wasn't so bad, but it still hapended. I doesn't need to many things open! One of the times that frooze today, I only had Firefox open! I done a mem test, and it showed everything OK! I have a Desktop HP dual-core 2,8 GHZ, with 2 GB RAM and a ATI/AMD X1600 with 512 MB using the open source driver. I have seen MANY users complaining about the same problems, either with Nvidia, AMD/ATI or even Intel Graphica cards, so it can't be a driver issue for all those users! Please solve this, or I will have to leave Ubuntu for good! And I don't want to! Thanks... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.14.1-031401-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Apr 14 22:11:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1600/X1650 Series] [1002:7181] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:0400] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:0401] InstallationDate: Installed on 2014-04-04 (10 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140403.1) MachineType: HP Pavilion 061 RJ770AA-AB9 m7660.pt ProcEnviron: LANGUAGE=pt:pt_BR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.1-031401-generic root=UUID=eda039e6-958f-4dac-837a-257149aa91e1 ro quiet splash zswap.enabled=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.19 dmi.board.name: LEUCITE3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.19:bd12/08/2006:svnHPPavilion061:pnRJ770AA-AB9m7660.pt:pvr0nx0114RE101LEUC300:rvnASUSTekComputerINC.:rnLEUCITE3:rvr2.00:cvn:ct3:cvr: dmi.product.name: RJ770AA-AB9 m7660.pt dmi.product.version: 0nx0114RE101LEUC300 dmi.sys.vendor: HP Pavilion 061 version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 14 21:15:27 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputBTC USB Multimedia Cordless Kit KEYBOARD, id 8 inputBTC USB Multimedia Cordless Kit KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu1 xserver.video_driver: radeon To manage no
[Desktop-packages] [Bug 1409110] [NEW] nvidia binary driver leaks vram like crazy
Public bug reported: Using the nvidia-smi tool, you can see how much VRAM the binary driver is using for the card. However, with the current latest driver in Ubuntu 14.10, the results aren't good. Just using desktop apps (no OpenGL apart from what Unity and Chrome naturally use), and the driver has consumed over a GB of VRAM: graeme@galvatron:~⟫ sudo nvidia-smi [sudo] password for graeme: Fri Jan 9 11:58:06 2015 +--+ | NVIDIA-SMI 331.38 Driver Version: 331.38 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 570 Off | :01:00.0 N/A | N/A | | 40% 43C N/A N/A / N/A | 1047MiB / 1279MiB | N/A Default | +---+--+--+ +-+ | Compute processes: GPU Memory | | GPU PID Process name Usage | |=| |0Not Supported | +-+ However, you can tell that this is caused by some sort of driver leak, since if you jump to the fb console with ctl-alt-f1, and then alt-tab back to X, the VRAM usage drops dramatically: graeme@galvatron:~⟫ sudo nvidia-smi Fri Jan 9 11:58:27 2015 +--+ | NVIDIA-SMI 331.38 Driver Version: 331.38 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 570 Off | :01:00.0 N/A | N/A | | 40% 45C N/A N/A / N/A |483MiB / 1279MiB | N/A Default | +---+--+--+ +-+ | Compute processes: GPU Memory | | GPU PID Process name Usage | |=| |0Not Supported | +-+ The upshot of this is that, right now, I have to dump to the fb console and back before using any OpenGL apps, or they often fail with OpenGL memory allocation errors. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 9 12:01:56 2015 SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages 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/1409110 Title: nvidia binary driver leaks vram like crazy Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Using the nvidia-smi tool, you can see how much VRAM the binary driver is using for the card. However, with the current latest driver in Ubuntu 14.10, the results aren't good. Just using desktop apps (no OpenGL apart from what Unity and Chrome naturally use), and the driver has consumed over a GB of VRAM: graeme@galvatron:~⟫ sudo nvidia-smi [sudo] password for graeme: Fri Jan 9 11:58:06 2015 +--+ | NVIDIA-SMI 331.38 Driver Versi
[Desktop-packages] [Bug 1395106] [NEW] Unity fails at all attempts to change the cursor
Public bug reported: I've acquired a high-dpi display recently (ASUS PB287Q), and while the monitor preferences to set GTK scaling works quite well, Unity makes no attempt to similarly scale up the cursor, leaving me with a minuscule cursor that is almost invisible. As well, other tools such as unity-tweak-tool, which claim to be able to set different cursor settings, also fail in unity. Searching the web, it appears that this is a long standing problem, which has been mostly ignored. However, given the very real need to scale up cursor size with monitor DPI along with other UI elements, I'm hoping we can see some investigation and traction on the issue now that 4k displays are starting to become more affordable and prevalent. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,copytex,maximumize,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,unitymtgrabhandles,session,wall,animation,resize,workarounds,snap,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 21 10:19:47 2014 DistUpgraded: 2014-11-05 17:06:23,375 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570 Rev. 2] [10de:1086] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1571] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=30a58b2c-3ad6-4911-a849-31d65294e8e2 ro intel_iommu=on quiet splash SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-06 (15 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3903:bd08/22/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Nov 20 16:52:36 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1395106 Title: Unity fails at all attempts to change the cursor Status in “unity” package in Ubuntu: New Bug description: I've acquired a high-dpi display recently (ASUS PB287Q), and while the monitor preferences to set GTK scaling works quite well, Unity makes no attempt to similarly scale up the cursor, leaving me with a minuscule cursor that is almost invisible. As well, other tools such as unity-tweak-tool, which claim to be able to set different cursor settings, also fail in unity. Searching the web, it appears that this is a long standing problem, which has been mostly ignored. However, given the very real need to scale up cursor size with monitor DPI along with other
[Desktop-packages] [Bug 1351772] [NEW] "disable touchpad while typing" doesn't work
Public bug reported: When selecting "disable while typing" under the touchpad section of the "Mouse & Touchpad" preferences, nothing changes, the touchpad stays active while typing. I can rapidly type multiple characters with my left hand and continue to move the cursor with the touchpad with my right hand. I can see from my processlist that syndaemon is running with the following options: 2185 ?S 1:31 | \_ syndaemon -i 1.0 -t -K -R First, the -t option isn't what's expected with this setting, it should disable the touchpad entirely. Also, it doesn't seem to even do that correctly, as I can definitely click the touchpad while typing as well as moving the cursor. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 Uname: Linux 3.14.0-997-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 17:20:22 2014 InstallationDate: Installed on 2014-04-22 (102 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1351772 Title: "disable touchpad while typing" doesn't work Status in “unity-control-center” package in Ubuntu: New Bug description: When selecting "disable while typing" under the touchpad section of the "Mouse & Touchpad" preferences, nothing changes, the touchpad stays active while typing. I can rapidly type multiple characters with my left hand and continue to move the cursor with the touchpad with my right hand. I can see from my processlist that syndaemon is running with the following options: 2185 ?S 1:31 | \_ syndaemon -i 1.0 -t -K -R First, the -t option isn't what's expected with this setting, it should disable the touchpad entirely. Also, it doesn't seem to even do that correctly, as I can definitely click the touchpad while typing as well as moving the cursor. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 Uname: Linux 3.14.0-997-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 17:20:22 2014 InstallationDate: Installed on 2014-04-22 (102 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1351772/+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 1282649] Re: Unable to make screenshot with key in Unity session in Trusty
I'm seeing this issue on Trusty but not on a laptop, and with a USB keyboard: KeyRelease event, serial 28, synthetic NO, window 0x401, root 0x296, subw 0x0, time 440656382, (72,58), root:(492,110), state 0x10, keycode 107 (keysym 0xff61, Print), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False That's the key event that doesn't trigger a screenshot on my computer. The keyboard shortcuts dialogue registers it as the "Print" key when I try and change the screenshot shortcut to it, so it looks like unity sees the key correctly, it just doesn't trigger a printscreen event. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1282649 Title: Unable to make screenshot with key in Unity session in Trusty Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: In Trusty with all installed updates it is not possible to make ScreenShot with keyboard button. The sound /usr/share/sounds/ubuntu/stereo/dialog-error.ogg is played and desired screenshot is not saved in ~/Pictures. Tested in guest and normal sessions. Please fix this bug. Do not forget about , and . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 20 19:40:24 2014 DistUpgraded: 2013-11-19 13:23:13,179 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:907a] InstallationDate: Installed on 2013-10-20 (123 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Sony Corporation VPCF13Z1R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=1d9289fd-0252-4f52-9d1e-fe6baf51083a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-19 (93 days ago) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:svnSonyCorporation:pnVPCF13Z1R:pvrC607OEHZ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF13Z1R dmi.product.version: C607OEHZ dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 20 19:32:11 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1282649/+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 1313840] [NEW] Screen lock causes texture corruption in 14.04
Public bug reported: In 13.10 and previous releases, locking the screen would go to the login screen, and then blank the screen and put the display to sleep. In 14.04, it goes to the login screen, then fades to black, but after that the screen is replaced with what looks like a corrupted texture buffer of the login screen, with alternating black and corrupted chunks in the framebuffer, and then the screen never goes to sleep, it just stays like that. I can't adequately capture a screenshot since, of course, it's at the login screen. Hopefully this is replicable on other systems using the NVidia 331 binary drivers. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-services 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.117 Tue Nov 26 21:25:36 PST 2013 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,copytex,maximumize,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,unitymtgrabhandles,session,wall,animation,resize,workarounds,snap,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 28 10:23:14 2014 DistUpgraded: 2014-04-21 12:00:15,259 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570 Rev. 2] [10de:1086] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1571] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=b48f669d-8024-48b8-b267-aa9fc0ed9a1b ro intel_iommu=on quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (6 days ago) dmi.bios.date: 08/22/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3903:bd08/22/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 21 12:52:34 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1313840 Title: Screen lock causes texture corruption in 14.04 Status in “unity” package in Ubuntu: New Bug description: In 13.10 and previous releases, locking the screen would go to the login screen, and then blank the screen and put the display to sleep. In 14.04, it goes to the login screen, then fades to black, but after that the screen is replaced with what looks like a corrupted texture buffer of the login screen, with alternating black and corrupted chunks in the framebuffer, and then the screen never goes to sleep, it just stays like that. I can't adequately capture a screenshot since, of course, it's at the login screen. Hopefully this is replicable on other systems using the NVidia 331 binary drivers. ProblemType: Bug DistroRelease:
[Desktop-packages] [Bug 1250979] Re: Nautilus forgets sidebar settings
This is definitely still a problem, so hopefully someone can at least confirm the bug independently with the gnome-ubuntu ISO in a VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1250979 Title: Nautilus forgets sidebar settings Status in “nautilus” package in Ubuntu: Expired Bug description: I've noticed this since maybe precise, but it's still present, so reporting it. Basically, nautilus always forgets if you've opened the sidebar with f9, and next time you open a nautilus window it's closed again. I use the sidebar tons, so while this is a minor cosmetic problem, it's also really annoying. ;) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 13 10:42:08 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'944x664+58+284'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1250979/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Still not working in Kubuntu 13.10 or 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling "poweroff", but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1245979]
I removed my nVidia card and the driver, and Akonadi starts OK now. I didn't experience the problems in the other reports in comment 52 of ^C not working in xterm (or Konsole, either). I have a suspicion that I was mistaken in comment 32 when I said that Akonadi only started 4 out of 5 times after renaming /usr/share/dbus-1/services/org.freedesktop.Akonadi.Control.service. Testing now, I found I wasn't always allowing enough time, so "akonadictl status" might say "stopped", but a moment later it would say "running". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1245979 Title: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable Status in Akonadi - The PIM Storage Service: Unknown Status in “akonadi” package in Ubuntu: Confirmed Bug description: Upon opening Kontact akonadi is supposed to be loaded but fails with the following error: Akonadi fails to register at d-bus session. I safed the self-test protocoll of the akonadi server and attached the report. I already deleted all my akonadi config files but it did not resolve the error. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1245979]
Nvidia 319.60 here! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1245979 Title: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable Status in Akonadi - The PIM Storage Service: Unknown Status in “akonadi” package in Ubuntu: Confirmed Bug description: Upon opening Kontact akonadi is supposed to be loaded but fails with the following error: Akonadi fails to register at d-bus session. I safed the self-test protocoll of the akonadi server and attached the report. I already deleted all my akonadi config files but it did not resolve the error. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1245979]
I'm not using Fedora, but I haven't found it necessary to remove Akonadi's config files to get it working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1245979 Title: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable Status in Akonadi - The PIM Storage Service: Unknown Status in “akonadi” package in Ubuntu: Confirmed Bug description: Upon opening Kontact akonadi is supposed to be loaded but fails with the following error: Akonadi fails to register at d-bus session. I safed the self-test protocoll of the akonadi server and attached the report. I already deleted all my akonadi config files but it did not resolve the error. To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1245979/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Also affects Kubuntu Trusty alpha. ** Tags added: kubuntu trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling "poweroff", but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1263005] [NEW] nvidia-prime breaks gnome-settings-daemon
Public bug reported: I'm seeing the problem described here: http://askubuntu.com/questions/392282/kernel-3-12-with-nvidia-331-and- nvidia-prime-does-not-load-unity-properly-in-ubu However, I'm seeing it on a fresh install of Ubuntu Gnome 13.10, with the stock 3.11.0-14-generic kernel but the nvidia-331 package from xorg- edgers PPA. Prior to installing the nvidia-prime package, everything worked correctly. After, gnome-settings-daemon refuses to run, with the 'BadMatch (invalid parameter attributes)' error noted on the linked page. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4.2~ubuntu13.10.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 23:55:56 2013 InstallationDate: Installed on 2013-12-06 (13 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1263005 Title: nvidia-prime breaks gnome-settings-daemon Status in “nvidia-prime” package in Ubuntu: New Bug description: I'm seeing the problem described here: http://askubuntu.com/questions/392282/kernel-3-12-with-nvidia-331-and- nvidia-prime-does-not-load-unity-properly-in-ubu However, I'm seeing it on a fresh install of Ubuntu Gnome 13.10, with the stock 3.11.0-14-generic kernel but the nvidia-331 package from xorg-edgers PPA. Prior to installing the nvidia-prime package, everything worked correctly. After, gnome-settings-daemon refuses to run, with the 'BadMatch (invalid parameter attributes)' error noted on the linked page. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4.2~ubuntu13.10.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 19 23:55:56 2013 InstallationDate: Installed on 2013-12-06 (13 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1263005/+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 1255558] Re: Can't type my password after cold boot
It went away for me today after applying updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot Status in “lightdm” package in Ubuntu: Confirmed Bug description: Can't type my password after cold boot unless I change my keyboard layout to next (or change and then re-change to same layout) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1 Uname: Linux 3.12.0-4-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Wed Nov 27 16:27:13 2013 InstallationDate: Installed on 2013-11-19 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131119) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/128/+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 1250979] Re: Nautilus forgets sidebar settings
I can generate the inverse behaviour (sidebar is always on, nautilus doesn't keep it off if I turn it off, close a window, open a new one) with the latest ubuntu-gnome 13.10 live CD for amd64 (http://torrent.ubuntu.com:6969/file?info_hash=A%26M%1C%FA%D2%9C%BD%3A%D0%82%FE%9FV%2Bj%5Cr%94%AA). So it may be something with gnome3 just persisting whatever behaviour is set and never remembering your new choices. I am using gnome-shell on the desktop where I'm seeing this behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1250979 Title: Nautilus forgets sidebar settings Status in “nautilus” package in Ubuntu: Incomplete Bug description: I've noticed this since maybe precise, but it's still present, so reporting it. Basically, nautilus always forgets if you've opened the sidebar with f9, and next time you open a nautilus window it's closed again. I use the sidebar tons, so while this is a minor cosmetic problem, it's also really annoying. ;) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 13 10:42:08 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'944x664+58+284'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1250979/+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 1250979] [NEW] Nautilus forgets sidebar settings
Public bug reported: I've noticed this since maybe precise, but it's still present, so reporting it. Basically, nautilus always forgets if you've opened the sidebar with f9, and next time you open a nautilus window it's closed again. I use the sidebar tons, so while this is a minor cosmetic problem, it's also really annoying. ;) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 13 10:42:08 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'944x664+58+284'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-22 (21 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1250979 Title: Nautilus forgets sidebar settings Status in “nautilus” package in Ubuntu: New Bug description: I've noticed this since maybe precise, but it's still present, so reporting it. Basically, nautilus always forgets if you've opened the sidebar with f9, and next time you open a nautilus window it's closed again. I use the sidebar tons, so while this is a minor cosmetic problem, it's also really annoying. ;) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 13 10:42:08 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'944x664+58+284'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false' MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1250979/+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 1173343] Re: avconv not compiled with x264 support
Documentation issue, not package bug. ** Changed in: libav (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1173343 Title: avconv not compiled with x264 support Status in “libav” package in Ubuntu: Invalid Bug description: It appears like the avconv binary in 12.10 x64 isn't compiled with libx264 support, making it much less useful: avconv -i test.mkv -codec:a copy -codec:v libx264 -profile high422 -crf 22 -crf_max 24 test.mp4 avconv version 0.8.6-6:0.8.6-0ubuntu0.12.10.1, Copyright (c) 2000-2013 the Libav developers built on Apr 2 2013 17:02:16 with gcc 4.7.2 [matroska,webm @ 0x8e1960] max_analyze_duration reached [matroska,webm @ 0x8e1960] Estimating duration from bitrate, this may be inaccurate Input #0, matroska,webm, from 'test.mkv': Duration: 01:44:14.12, start: 0.00, bitrate: 1536 kb/s Stream #0.0(eng): Video: h264 (High), yuv420p, 1920x816, PAR 1:1 DAR 40:17, 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default) Metadata: title : test [mkvonly] Stream #0.1(eng): Audio: dca (DTS), 48000 Hz, 5.1, s16, 1536 kb/s (default) Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x (default) Stream #0.3(ara): Subtitle: [0][0][0][0] / 0x Stream #0.4(bul): Subtitle: dvdsub Stream #0.5(hrv): Subtitle: [0][0][0][0] / 0x Stream #0.6(cze): Subtitle: [0][0][0][0] / 0x Stream #0.7(dan): Subtitle: [0][0][0][0] / 0x Stream #0.8(dut): Subtitle: [0][0][0][0] / 0x Stream #0.9(est): Subtitle: [0][0][0][0] / 0x Stream #0.10(fin): Subtitle: [0][0][0][0] / 0x Stream #0.11(fre): Subtitle: [0][0][0][0] / 0x Stream #0.12(ger): Subtitle: [0][0][0][0] / 0x Stream #0.13(gre): Subtitle: dvdsub Stream #0.14(heb): Subtitle: dvdsub Stream #0.15(hun): Subtitle: [0][0][0][0] / 0x Stream #0.16(ice): Subtitle: [0][0][0][0] / 0x Stream #0.17(ind): Subtitle: [0][0][0][0] / 0x Stream #0.18(ita): Subtitle: [0][0][0][0] / 0x Stream #0.19(nor): Subtitle: [0][0][0][0] / 0x Stream #0.20(pol): Subtitle: [0][0][0][0] / 0x Stream #0.21(por): Subtitle: [0][0][0][0] / 0x Metadata: title : Br Stream #0.22(rum): Subtitle: [0][0][0][0] / 0x Stream #0.23(spa): Subtitle: [0][0][0][0] / 0x Stream #0.24(swe): Subtitle: [0][0][0][0] / 0x Stream #0.25(tha): Subtitle: dvdsub Stream #0.26(tur): Subtitle: [0][0][0][0] / 0x Unknown encoder 'libx264' ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libav-tools 6:0.8.6-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Apr 26 11:58:03 2013 MarkForUpload: True SourcePackage: libav UpgradeStatus: Upgraded to quantal on 2012-10-23 (184 days ago) modified.conffile..etc.avserver.conf: [modified] mtime.conffile..etc.avserver.conf: 2011-10-02T08:13:51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1173343/+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 1173343] Re: avconv not compiled with x264 support
Oh yes, that works. Might be worth adding a note to the docs about this. On that note, the docs for this package are broken when installing libavcodec-extra-53, as they symlink to libavcodec53: # ls -l /usr/share/doc/libav-tools/README.Debian.gz lrwxrwxrwx 1 root root 32 Apr 2 10:04 /usr/share/doc/libav-tools/README.Debian.gz -> ../libavcodec53/README.Debian.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1173343 Title: avconv not compiled with x264 support Status in “libav” package in Ubuntu: Invalid Bug description: It appears like the avconv binary in 12.10 x64 isn't compiled with libx264 support, making it much less useful: avconv -i test.mkv -codec:a copy -codec:v libx264 -profile high422 -crf 22 -crf_max 24 test.mp4 avconv version 0.8.6-6:0.8.6-0ubuntu0.12.10.1, Copyright (c) 2000-2013 the Libav developers built on Apr 2 2013 17:02:16 with gcc 4.7.2 [matroska,webm @ 0x8e1960] max_analyze_duration reached [matroska,webm @ 0x8e1960] Estimating duration from bitrate, this may be inaccurate Input #0, matroska,webm, from 'test.mkv': Duration: 01:44:14.12, start: 0.00, bitrate: 1536 kb/s Stream #0.0(eng): Video: h264 (High), yuv420p, 1920x816, PAR 1:1 DAR 40:17, 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default) Metadata: title : test [mkvonly] Stream #0.1(eng): Audio: dca (DTS), 48000 Hz, 5.1, s16, 1536 kb/s (default) Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x (default) Stream #0.3(ara): Subtitle: [0][0][0][0] / 0x Stream #0.4(bul): Subtitle: dvdsub Stream #0.5(hrv): Subtitle: [0][0][0][0] / 0x Stream #0.6(cze): Subtitle: [0][0][0][0] / 0x Stream #0.7(dan): Subtitle: [0][0][0][0] / 0x Stream #0.8(dut): Subtitle: [0][0][0][0] / 0x Stream #0.9(est): Subtitle: [0][0][0][0] / 0x Stream #0.10(fin): Subtitle: [0][0][0][0] / 0x Stream #0.11(fre): Subtitle: [0][0][0][0] / 0x Stream #0.12(ger): Subtitle: [0][0][0][0] / 0x Stream #0.13(gre): Subtitle: dvdsub Stream #0.14(heb): Subtitle: dvdsub Stream #0.15(hun): Subtitle: [0][0][0][0] / 0x Stream #0.16(ice): Subtitle: [0][0][0][0] / 0x Stream #0.17(ind): Subtitle: [0][0][0][0] / 0x Stream #0.18(ita): Subtitle: [0][0][0][0] / 0x Stream #0.19(nor): Subtitle: [0][0][0][0] / 0x Stream #0.20(pol): Subtitle: [0][0][0][0] / 0x Stream #0.21(por): Subtitle: [0][0][0][0] / 0x Metadata: title : Br Stream #0.22(rum): Subtitle: [0][0][0][0] / 0x Stream #0.23(spa): Subtitle: [0][0][0][0] / 0x Stream #0.24(swe): Subtitle: [0][0][0][0] / 0x Stream #0.25(tha): Subtitle: dvdsub Stream #0.26(tur): Subtitle: [0][0][0][0] / 0x Unknown encoder 'libx264' ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libav-tools 6:0.8.6-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Apr 26 11:58:03 2013 MarkForUpload: True SourcePackage: libav UpgradeStatus: Upgraded to quantal on 2012-10-23 (184 days ago) modified.conffile..etc.avserver.conf: [modified] mtime.conffile..etc.avserver.conf: 2011-10-02T08:13:51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1173343/+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 1173343] [NEW] avconv not compiled with x264 support
Public bug reported: It appears like the avconv binary in 12.10 x64 isn't compiled with libx264 support, making it much less useful: avconv -i test.mkv -codec:a copy -codec:v libx264 -profile high422 -crf 22 -crf_max 24 test.mp4 avconv version 0.8.6-6:0.8.6-0ubuntu0.12.10.1, Copyright (c) 2000-2013 the Libav developers built on Apr 2 2013 17:02:16 with gcc 4.7.2 [matroska,webm @ 0x8e1960] max_analyze_duration reached [matroska,webm @ 0x8e1960] Estimating duration from bitrate, this may be inaccurate Input #0, matroska,webm, from 'test.mkv': Duration: 01:44:14.12, start: 0.00, bitrate: 1536 kb/s Stream #0.0(eng): Video: h264 (High), yuv420p, 1920x816, PAR 1:1 DAR 40:17, 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default) Metadata: title : test [mkvonly] Stream #0.1(eng): Audio: dca (DTS), 48000 Hz, 5.1, s16, 1536 kb/s (default) Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x (default) Stream #0.3(ara): Subtitle: [0][0][0][0] / 0x Stream #0.4(bul): Subtitle: dvdsub Stream #0.5(hrv): Subtitle: [0][0][0][0] / 0x Stream #0.6(cze): Subtitle: [0][0][0][0] / 0x Stream #0.7(dan): Subtitle: [0][0][0][0] / 0x Stream #0.8(dut): Subtitle: [0][0][0][0] / 0x Stream #0.9(est): Subtitle: [0][0][0][0] / 0x Stream #0.10(fin): Subtitle: [0][0][0][0] / 0x Stream #0.11(fre): Subtitle: [0][0][0][0] / 0x Stream #0.12(ger): Subtitle: [0][0][0][0] / 0x Stream #0.13(gre): Subtitle: dvdsub Stream #0.14(heb): Subtitle: dvdsub Stream #0.15(hun): Subtitle: [0][0][0][0] / 0x Stream #0.16(ice): Subtitle: [0][0][0][0] / 0x Stream #0.17(ind): Subtitle: [0][0][0][0] / 0x Stream #0.18(ita): Subtitle: [0][0][0][0] / 0x Stream #0.19(nor): Subtitle: [0][0][0][0] / 0x Stream #0.20(pol): Subtitle: [0][0][0][0] / 0x Stream #0.21(por): Subtitle: [0][0][0][0] / 0x Metadata: title : Br Stream #0.22(rum): Subtitle: [0][0][0][0] / 0x Stream #0.23(spa): Subtitle: [0][0][0][0] / 0x Stream #0.24(swe): Subtitle: [0][0][0][0] / 0x Stream #0.25(tha): Subtitle: dvdsub Stream #0.26(tur): Subtitle: [0][0][0][0] / 0x Unknown encoder 'libx264' ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libav-tools 6:0.8.6-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Apr 26 11:58:03 2013 MarkForUpload: True SourcePackage: libav UpgradeStatus: Upgraded to quantal on 2012-10-23 (184 days ago) modified.conffile..etc.avserver.conf: [modified] mtime.conffile..etc.avserver.conf: 2011-10-02T08:13:51 ** Affects: libav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1173343 Title: avconv not compiled with x264 support Status in “libav” package in Ubuntu: New Bug description: It appears like the avconv binary in 12.10 x64 isn't compiled with libx264 support, making it much less useful: avconv -i test.mkv -codec:a copy -codec:v libx264 -profile high422 -crf 22 -crf_max 24 test.mp4 avconv version 0.8.6-6:0.8.6-0ubuntu0.12.10.1, Copyright (c) 2000-2013 the Libav developers built on Apr 2 2013 17:02:16 with gcc 4.7.2 [matroska,webm @ 0x8e1960] max_analyze_duration reached [matroska,webm @ 0x8e1960] Estimating duration from bitrate, this may be inaccurate Input #0, matroska,webm, from 'test.mkv': Duration: 01:44:14.12, start: 0.00, bitrate: 1536 kb/s Stream #0.0(eng): Video: h264 (High), yuv420p, 1920x816, PAR 1:1 DAR 40:17, 23.98 fps, 23.98 tbr, 1k tbn, 180k tbc (default) Metadata: title : test [mkvonly] Stream #0.1(eng): Audio: dca (DTS), 48000 Hz, 5.1, s16, 1536 kb/s (default) Stream #0.2(eng): Subtitle: [0][0][0][0] / 0x (default) Stream #0.3(ara): Subtitle: [0][0][0][0] / 0x Stream #0.4(bul): Subtitle: dvdsub Stream #0.5(hrv): Subtitle: [0][0][0][0] / 0x Stream #0.6(cze): Subtitle: [0][0][0][0] / 0x Stream #0.7(dan): Subtitle: [0][0][0][0] / 0x Stream #0.8(dut): Subtitle: [0][0][0][0] / 0x Stream #0.9(est): Subtitle: [0][0][0][0] / 0x Stream #0.10(fin): Subtitle: [0][0][0][0] / 0x Stream #0.11(fre): Subtitle: [0][0][0][0] / 0x Stream #0.12(ger): Subtitle: [0][0][0][0] / 0x Stream #0.13(gre): Subtitle: dvdsub Stream #0.14(heb): Subtitle: dvdsub Stream #0.15(hun): Subtitle: [0][0][0][0] / 0x Stream #0.16(ice): Subtitle: [0][0][0][0] / 0x Stream #0.17(ind): Subtitle: [0][0][0][0] / 0x Stream #0.18(ita): Subtitle: [0][0][0][0] / 0x Stream #0.19(nor): Subtitl
[Desktop-packages] [Bug 744812] Re: FontConfig/Qt stack choke on Ubuntu Medium font meta-data (No medium in Inkscape and too bold in Qt apps)
Bug 972279 "Konsole displays bold text with normal weight" might be related to this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/744812 Title: FontConfig/Qt stack choke on Ubuntu Medium font meta-data (No medium in Inkscape and too bold in Qt apps) Status in Fontconfig - Font Configuration Library: Confirmed Status in Linux Libertine: Unknown Status in Ubuntu Font Family: Invalid Status in “fontconfig” package in Ubuntu: Confirmed Status in “qt4-x11” package in Ubuntu: Fix Released Status in “ubuntu-font-family-sources” package in Ubuntu: Fix Released Status in “qt4-x11” source package in Natty: Invalid Status in “ubuntu-font-family-sources” source package in Natty: Fix Released Status in “qt4-x11” source package in Oneiric: Invalid Status in “ubuntu-font-family-sources” source package in Oneiric: Fix Released Status in “qt4-x11” source package in Precise: Invalid Status in “ubuntu-font-family-sources” source package in Precise: Fix Released Status in “qt4-x11” source package in Quantal: Fix Released Status in “ubuntu-font-family-sources” source package in Quantal: Fix Released Bug description: [Kubuntu natty up-to-date] Hi, Without any change on my system, I noticed some days ago that my default font (ubuntu) changed. Some odd behaviour appeared : ubuntu medium 10 pt was ok but ubuntu medium 11pt was bold (-> in my taskbar clock or in kpackapgekit). In fact, after some play with kcm kubuntu font manager, the ubuntu medium 10pt was wrong, since kcm module shows the true appearance of ubuntu medium, which is quite bold. I swapped to ubunu light font SO ! I changed font hinting to light (default in kubuntu seems to be medium) and it seems to have solved bugs. Anyway, "ubuntu font" management by KDE seems to be strange, and firefox 4 font rendering is worse (imho) with light hinting (but maybe because of unselected "system default" parameter in fonts kcm). To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/744812/+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 780399] Re: Wizard doesn't run without libreoffice-java-common installed. The user should be notified to install it when running a wizard.
In Kubuntu 12.10, the letter wizard doesn't work, with no indication of why not, until libreoffice-java-common is installed. I agree with earlier comments: tell the user to install the package, or (better) install it by default. The lack of feedback to the user without the package installed is very poor. ** Tags added: quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/780399 Title: Wizard doesn't run without libreoffice-java-common installed. The user should be notified to install it when running a wizard. Status in “libreoffice” package in Ubuntu: In Progress Status in Baltix GNU/Linux: New Bug description: Binary package hint: libreoffice With LibreOffice Writer open I select File-Wizards-Letter and nothing seems to happen. It's the same for letters and agendas. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-core 1:3.3.2-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 10 10:05:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110415) ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/780399/+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 863834] Re: [regression] Suspend on lid close broken on Oneiric
Also affects Perfect as of a recent (not sure exactly when) update. Not the sort of behaviour that should change without a version change IMO. This could lead to some laptops overheating/catching fire etc. so not a good idea at all. -- 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/863834 Title: [regression] Suspend on lid close broken on Oneiric Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “upower” package in Ubuntu: Confirmed Bug description: With Oneiric, I cannot have my laptop go into suspend mode by closing the lid anymore. In the gnome settings, the lid close action is configured to suspend (both on AC and on battery), but closing the lid does nothing. Here is the output of "acpid -d" when I close the lid: No protocol specified xset: unable to open display ":0" And here it what it says when I open the lid: Sessions still open, not unmounting Here is the output of acpi_listen when I close/open the lid: button/lid LID0 0080 0009 button/lid LID0 0080 000a Here is what /proc/acpi says with the lid open and closed: gpothier@tadzim:~$ cat /proc/acpi/button/lid/*/state state: open gpothier@tadzim:~$ cat /proc/acpi/button/lid/*/state state: closed Suspending in itself works fine with the laptop's suspend button. Suspend on lid close worked fine in Natty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/863834/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "text message body copy/paste to writer" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429161/+files/Screenshot-01-writer-20121109T171710.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "text file opened in gedit - not legible" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429166/+files/Screenshot-03-gedit-20121109T174750.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "text message body copy/paste to gedit" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429160/+files/Screenshot-01-gedit-20121109T171235.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "text message body copy/paste to writer" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429164/+files/Screenshot-02-writer-20121109T173402.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "text file icons on desktop" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429165/+files/Screenshot-03-desktop-20121109T174600.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "Another text message in evolution" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429162/+files/Screenshot-02-evolution-20121109T173332.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "Another text message in evolution" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429163/+files/Screenshot-02-evolution-20121109T173332.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Attachment added: "same text (html) file opened in notebook (in wine)" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429167/+files/Screenshot-03-wine-notepad-20121109T174656.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
TodayI performed an in-place update from 10.04 to 12.04. During the course of the install i noted the appearance of several dialogs (presumably errors) as described by the original report. I am still unsure about what to do in a lot of cases, so I clicked on the default (highlighted) button to continue. (I am new with Linux, but my overall computer experience goes back to the dark ages of TRS-DOS, CP/M, and integer BASIC on a teletype machine.) AFTER this installation fully completed I noticed that the issue also affect a number of text-type items. I observed the effect (characters replaced by empty rectangles) in text email messages in Evolution, and in text files on the desktop. I had to try a number of workarounds. the results are illustrated in the attachments. Screenshot-01-: Text email message as viewed in Evolution, gedit and writer. (It is readable only in writer.) Screenshot-02-: Another text email bessage as viewed in Evolution and writer. Screenshot-03-: A text (html) file stored on the desktop as viewed there, in gedit, and with notebook in wine. (It is only readable in notebook.) This is my first time reporting in this system, so any helpful feedback will be appreciated. ** Attachment added: "Text email in evolution - note that the body is trashed but the headers are fine" https://bugs.launchpad.net/pango/+bug/1038573/+attachment/3429159/+files/Screenshot-01-evolution-20121109T170942.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 1038573] Re: Unreadable messages displayed during Lucid -> Precise upgrade
** Also affects: pango Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1038573 Title: Unreadable messages displayed during Lucid -> Precise upgrade Status in Pango - Layout and Text Rendering LIbrary: New Status in “pango1.0” package in Ubuntu: Triaged Status in “pango1.0” source package in Precise: Triaged Bug description: I'm just testing 10.04.4 -> 12.04.1 upgrades and the upgrade did complete successfully but twice during the upgrade I was presented with a dialog box that's totally unreadable, and the upgrade process does not proceed until I click on the unreadable widget in the lower right hand corner of the box. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Sun Aug 19 00:30:02 2012 GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1345345338 InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release i386 (20120214.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to precise on 2012-08-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: [Errno 13] Permission denied: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1038573/+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 849297] Re: ICS - Internet Connection Sharing
Have hit this bug as well. Sep 13 14:16:30 kristopher-LT21 NetworkManager[503]: dnsmasq exited with error: Network access problem (address in use; permissions; etc) (2) Is because Network Manager does not kill dnsmasq when it drops the connection. There is no indication in the logs though why NM decides to keep dropping the connection for no reason. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/849297 Title: ICS - Internet Connection Sharing Status in “network-manager” package in Ubuntu: Incomplete Bug description: OS: Ubuntu 11.10 beta 1 Brief Description: 11.04 worked well. With the 11.10 beta 1 release I encountered issues with ICS via lan eth0 when attempting to share my wifi connection to a desktop. Both use Ubuntu and the issue is only present in 11.10 beta 1. Everything seems to be configured correctly but I encounter the computer in which I share the connection, to be repeatedly connecting and dropping the connection in 5 sec intervals when attempting ICS with Lan from my wireless computer until I receive a bug notice when I attempt to try other settings. Everything else seems to work with Network connections except ICS. Sorry for the lack of info or logs. This was tested in the 64 bit version using Ubuntu 11.10 beta 1 - as said before the computers used were plug and play with 11.04. --- ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 11.10 Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) IpRoute: default via 192.168.1.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-12T17:15:11.395570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/849297/+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 884923] [NEW] "gnome-control-center color" doesn't display monitors for calibration
Public bug reported: When using "gnome-control-center color", it doesn't display either of my monitors for color calibration. I'm on 11.10 x64, using the latest nvidia binary drivers, monitors in TwinView mode. G ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: zfs zcommon znvpair zavl zunicode nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 13:51:10 2011 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-10-25 (7 days ago) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1 krb5-auth-dialog 3.0.1-1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/884923 Title: "gnome-control-center color" doesn't display monitors for calibration Status in “gnome-control-center” package in Ubuntu: New Bug description: When using "gnome-control-center color", it doesn't display either of my monitors for color calibration. I'm on 11.10 x64, using the latest nvidia binary drivers, monitors in TwinView mode. G ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: zfs zcommon znvpair zavl zunicode nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 13:51:10 2011 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-10-25 (7 days ago) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1 krb5-auth-dialog 3.0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/884923/+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 884923] Re: "gnome-control-center color" doesn't display monitors for calibration
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/884923 Title: "gnome-control-center color" doesn't display monitors for calibration Status in “gnome-control-center” package in Ubuntu: New Bug description: When using "gnome-control-center color", it doesn't display either of my monitors for color calibration. I'm on 11.10 x64, using the latest nvidia binary drivers, monitors in TwinView mode. G ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: zfs zcommon znvpair zavl zunicode nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 13:51:10 2011 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-10-25 (7 days ago) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1 krb5-auth-dialog 3.0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/884923/+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
