[Desktop-packages] [Bug 1932328]
Hi, sorry I am not using PopOS anymore I believe Pop team have halted Gnome updates as they are working on a new "Cosmic" desktop environment, I will actually try Cosmic after its released and can check if the bug is there or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Fix Released Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 2023763] [NEW] Wron directory items list after removal operation
Public bug reported: Let assume that we have 4 items in directory - ABCD. When deleting the D, the D is actually removed but the list may be ABD. After reentering into directory the list is correct and is ABC. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 12:28:23 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-08-26 (291 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "nautilus-bug.pdf" https://bugs.launchpad.net/bugs/2023763/+attachment/5679643/+files/nautilus-bug.pdf -- 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/2023763 Title: Wron directory items list after removal operation Status in nautilus package in Ubuntu: New Bug description: Let assume that we have 4 items in directory - ABCD. When deleting the D, the D is actually removed but the list may be ABD. After reentering into directory the list is correct and is ABC. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 12:28:23 2023 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2022-08-26 (291 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023763/+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 2017984] [NEW] "Save as" window from browser is not in dark mode
Public bug reported: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20X4S1GH08 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrR1JET60W(1.60):bd11/22/2022:br1.60:efr1.48:svnLENOVO:pn20X4S1GH08:pvrThinkPadL15Gen2:rvnLENOVO:rn20X4S1GH08:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20X4_BU_Think_FM_ThinkPadL15Gen2: dmi.product.family: ThinkPad L15 Gen 2 dmi.product.name: 20X4S1GH08 dmi.product.sku: LENOVO_MT_20X4_BU_Think_FM_ThinkPad L15 Gen 2 dmi.product.version: ThinkPad L15 Gen 2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session ** Attachment added: "Screenshot from 2023-04-28 12-31-38.png" https://bugs.launchpad.net/bugs/2017984/+attachment/5669369/+files/Screenshot%20from%202023-04-28%2012-31-38.png -- 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/2017984 Title: "Save as" window from browser is not in dark mode Status in xorg package in Ubuntu: New Bug description: After update to 23.04 I'm having the following issue. In dark mode of Yaru-dark theme, when downloading the file and choosing the "Save as" option - popup window for folder selection is not in dark mode. When using Xorg session problem is not reproduced. The same applies for upload logic. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 28 12:31:55 2023 DistUpgraded: 2023-04-25 21:06:12,927 DEBUG icon theme changed, re-reading DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:508f] InstallationDate: Installed on 2022-08-26 (244 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20X4S1GH08 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro usbcore.autosuspend=-1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-25 (2 days ago) dmi.bios.date: 11/22/2022 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: R1JET60W (1.60 ) dmi.board.a
[Desktop-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Same issue on HP Envy 17 Alder Lake-P and Realtek ALC245. Tried all LTS kernels, 6.0 & 6.1. Tried on Ubuntu 23.01, 22.04, PopOS 22.04, Manjaro and speakers won't work on any of them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1932328]
(In reply to ddl-github from comment #17) > Confirming this bug persists in TB 91 under Pop!_OS 21.10. A fix for this > was apparently > [committed](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2027) > several months ago, but (per [this > comment](https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/comments/64)) > users will not see it until updating to gnome 40.6. Are you saying this is fixed via Gnome update? I've only seen the bug in Thunderbird -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1932328]
Hi guys, added the Mozilla PPA and (seamlessly) upgraded from 78->91.3.2. This bug still exists, I guess the next test will be in a few weeks when Pop_OS moves to gnome 40 in their 21.10 release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1912472] Re: Display freezes randomly - high CPU usage
Thanks for your kind help Daniel. Six weeks ago, I migrated to Debian 10, default install with Gnome and Wayland. Since then, I didn't encounter any problem working with the same programs. This bug can be closed, as I won't be able to help finding what the exact issue was. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+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 1912472] Re: Display freezes randomly - high CPU usage
Problem happened again, this time using Firefox (last time was while using FreeCAD). I waited a minute before rebooting (as each time, so as to be sure the system is really frozen). I have no file under /var/crash, sorry. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+attachment/5457076/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+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 1912472] Re: Display freezes randomly - high CPU usage
Problem happened again. Here enclosed, you will find the result of a journalctl for last boot ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+attachment/5456315/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+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 1912472] Re: Display freezes randomly - high CPU usage
I have those manually installed extensions : - hibernate-status@dromi - update-extensi...@franglais125.gmail.com I disabled them as required, so as to test if problem persists. In case it does, I will tell you here in a new comment. In case it solves the issue, I can't tell after how much time we can consider the problem fixed, as it has happened three times some days, and in december it only happened one time in total, it's totally random. I can just tell that it didn't happen with the two previous LTS releases. And that it persists after a complete OS re-install. How should we process in case the problem doesn't happen for weeks ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+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 1912472] Re: Display freezes randomly - high CPU usage
I never use fullscreen function under Firefox, so the problem is not related to the mentioned bug. Do you mean Firefox, or gnome-shell extensions ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1912472 Title: Display freezes randomly - high CPU usage Status in mutter package in Ubuntu: Incomplete Bug description: Randomly, system freezes with high CPU usage (cooling fan goes high when the problem happens) since update to Ubuntu 20.04.1 LTS. Same problem with X11 and Wayland. Display freezes and keyboard or mouse inputs won't change anything. Caps and num lock won't react either. Ctrl+alt+anything doesn't solve the issue. Only possibility is then to force reboot using power button. After reboot, I could find in logs : gnome-shell libinput error: client bug: timer event6 debounce short: scheduled expiry is in the past (-15ms), your system is too slow Problem happens in any situation, for example while videoconferencing with any software, or using LibreOffice Writer, sometimes with Firefox. The only common fact seems to be that Firefox is always opened. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 10:27:48 2021 InstallationDate: Installed on 2020-11-15 (65 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912472/+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 1874020] Re: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic
Apparently a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315 -- 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/1874020 Title: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic Status in lightdm package in Ubuntu: New Bug description: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874020/+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 1874020] [NEW] Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic
Public bug reported: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1874020 Title: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic Status in lightdm package in Ubuntu: New Bug description: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874020/+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 1702927] Re: lirc_serial module no longer in the kernel extra package
/lib/modules$ ls 4.10.0-22-generic 4.10.0-26-generic 4.8.0-53-generic $ find . -name 'lirc_serial.ko' ./4.8.0-53-generic/kernel/drivers/staging/media/lirc/lirc_serial.ko $ dpkg -S /lib/modules/4.8.0-53-generic/kernel/drivers/staging/media/lirc/lirc_serial.k linux-image-extra-4.8.0-53-generic: /lib/modules/4.8.0-53-generic/kernel/drivers/staging/media/lirc/lirc_serial.ko as you can see, linux-image-extra 4.8.0 contains the module, but 4.10.x does not -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1702927 Title: lirc_serial module no longer in the kernel extra package Status in lirc package in Ubuntu: Incomplete Bug description: Up to Ubuntu 16.10 the kernel extras contained the lirc_serial, but since 17.04 it is no longer part of the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1702927/+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 1702927] [NEW] lirc_serial module no longer in the kernel extra package
Public bug reported: Up to Ubuntu 16.10 the kernel extras contained the lirc_serial, but since 17.04 it is no longer part of the package. ** Affects: lirc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1702927 Title: lirc_serial module no longer in the kernel extra package Status in lirc package in Ubuntu: New Bug description: Up to Ubuntu 16.10 the kernel extras contained the lirc_serial, but since 17.04 it is no longer part of the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1702927/+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 1607924] [NEW] fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
Public bug reported: I installed AMD fglrx through AMD's website and upon reboot could not get to my desktop or TTY anymore. I tried to blindly uninstall everything and went back to X.Org open-source drivers. The bug was encountered. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-core (not installed) ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.2.0-42-generic Date: Fri Jul 29 15:13:46 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:174b] InstallationDate: Installed on 2016-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: MSI MS-7926 PackageVersion: 2:15.201-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=8488b034-23ac-42b5-84fd-860013f162e4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: fglrx-installer Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 9 AC (MS-7926) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd02/16/2016:svnMSI:pnMS-7926:pvr1.0:rvnMSI:rnZ97GAMING9AC(MS-7926):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7926 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jul 29 15:31:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1607924 Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: I installed AMD fglrx through AMD's website and upon reboot could not get to my desktop or TTY anymore. I tried to blindly uninstall everything and went back to X.Org open-source drivers. The bug was encountered. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fglrx-core (not installed) ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.2.0-42-generic Date: Fri Jul 29 15:13:46 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:174b] InstallationDate: Installed on 2016-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: MSI MS-7926 PackageVersion: 2:15.201-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=8488b034-23ac-42b5-84fd-860013f162e4 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage
[Desktop-packages] [Bug 1434986] Re: Not working network connection after boot
I too am affected by this bug, on Ubuntu 16.04 LTS. The bug has been present for me, in a way or another, since 15.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 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.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1566717] [NEW] No option to set up Gnome Terminal Notifications "Job done"
Public bug reported: Hi, Ubuntu Gnome 16.04 - 64 bits - Nvidia driver ON expected to happen : Could set up notification for Gnome Terminal to show thumbnail in notification area "job done" What happened : Nothing, there is no such option in gnome settings. Haven't seen in dconf-editor or kind of setting editor - so there is no gnome terminal notification wich this not my mistake, anyway Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 6 10:22:12 2016 InstallationDate: Installed on 2016-04-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1566717 Title: No option to set up Gnome Terminal Notifications "Job done" Status in gnome-terminal package in Ubuntu: New Bug description: Hi, Ubuntu Gnome 16.04 - 64 bits - Nvidia driver ON expected to happen : Could set up notification for Gnome Terminal to show thumbnail in notification area "job done" What happened : Nothing, there is no such option in gnome settings. Haven't seen in dconf-editor or kind of setting editor - so there is no gnome terminal notification wich this not my mistake, anyway Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 6 10:22:12 2016 InstallationDate: Installed on 2016-04-05 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1566717/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Andrea, a DNS Leak is defined as any DNS traffic going outside your VPN's assigned servers. Even if 8.8.8.8 goes through the VPN, it's still leaking your traffic. https://www.dnsleaktest.com/what-is-a-dns- leak.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@Andrea, I tried that, but then my VPN connection uses the static servers. And unless Google DNS connections are encrypted, it's still a DNS leak. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Same issue for me on 15.10, but it didn't happen on 15.04. Using the script-security 2 option in the configuration file, everything works correctly when run from command line: "sudo openvpn --config file.ovpn" For me, this problem only happens when connecting through Network Manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1475876] [NEW] PCI/internal sound card not detected
Public bug reported: Pulse Audio will not load, only dummy audio is available. I have tried purging and reinstalling pulse audio to no avail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jul 18 15:05:07 2015 InstallationDate: Installed on 2015-07-18 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0G261D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1475876 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Pulse Audio will not load, only dummy audio is available. I have tried purging and reinstalling pulse audio to no avail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jul 18 15:05:07 2015 InstallationDate: Installed on 2015-07-18 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0G261D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0G261D:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1475876/+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 1473777] Re: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build
*** This bug is a duplicate of bug 1409190 *** https://bugs.launchpad.net/bugs/1409190 And now that I can see the build log, I can see that this is a dupe too. :) ** This bug has been marked a duplicate of bug 1409190 nvidia kernel module failed to build [error: ‘struct file’ has no member named ‘f_dentry’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1473777 Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: I was trying to upgrade from nvidia-304 to nvidia-331-updates on Trusty. Along the way I hit various build failures. Initially I tried to install it for the Vivid HWE kernel, but then I gave up on that kernel and uninstalled it when I encountered bug 1409190. Then I tried to install it for just the latest Trusty kernel, where I hit bug 1268257. Eventually I got it working with the workaround in that bug. Apport generated problem reports for every build failure and deduped all of them except this one. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-22-generic Date: Sun Jul 12 15:35:07 2015 DuplicateSignature: dkms:nvidia-331-updates:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-12-24 (200 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1473777/+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 1473777] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build
*** This bug is a duplicate of bug 1409190 *** https://bugs.launchpad.net/bugs/1409190 Public bug reported: I was trying to upgrade from nvidia-304 to nvidia-331-updates on Trusty. Along the way I hit various build failures. Initially I tried to install it for the Vivid HWE kernel, but then I gave up on that kernel and uninstalled it when I encountered bug 1409190. Then I tried to install it for just the latest Trusty kernel, where I hit bug 1268257. Eventually I got it working with the workaround in that bug. Apport generated problem reports for every build failure and deduped all of them except this one. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-22-generic Date: Sun Jul 12 15:35:07 2015 DuplicateSignature: dkms:nvidia-331-updates:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-12-24 (200 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1473777 Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: I was trying to upgrade from nvidia-304 to nvidia-331-updates on Trusty. Along the way I hit various build failures. Initially I tried to install it for the Vivid HWE kernel, but then I gave up on that kernel and uninstalled it when I encountered bug 1409190. Then I tried to install it for just the latest Trusty kernel, where I hit bug 1268257. Eventually I got it working with the workaround in that bug. Apport generated problem reports for every build failure and deduped all of them except this one. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 DKMSKernelVersion: 3.19.0-22-generic Date: Sun Jul 12 15:35:07 2015 DuplicateSignature: dkms:nvidia-331-updates:331.113-0ubuntu0.0.4:/var/lib/dkms/nvidia-331-updates/331.113/build/nv.c:2027:29: error: ‘struct file’ has no member named ‘f_dentry’ PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2014-12-24 (200 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1473777/+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 1422373] [NEW] evince japanese pdf form writeable but don't render right
Public bug reported: poppler-data is installed, and the file in general renders ok with the japanese. Only the fields to be filled out - allow to input japanese, but then render into weird boxes. evince maintains there is a not embedded 'ZapfDingbats' font in the file, and instead choses Dingbats. this is evince 3.10.3 on an Ubuntu 14.04 I expected: to have the fields render as japanese text Instead: When jumping out of the field, the text turns into strange boxes Here is an example file, though taiwanese, a similar thing happens http://www.koryu.or.jp/kaohsiung-tw/ez3_contents.nsf/15aef977a6d6761f49256de4002084ae/a03c3583dc32699349256ffc00329fea/$FILE/sinseisyo%28tiawan%29.pdf ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: evince japanese ** Tags added: evince japanese ** Description changed: poppler-data is installed, and the file in general renders ok with the japanese. - Only the fields to be filled out - allow to input japanese, but then render into weird boxes. + Only the fields to be filled out - allow to input japanese, but then render into weird boxes. evince maintains there is a not embedded 'ZapfDingbats' font in the file, and instead choses Dingbats. this is evince 3.10.3 on an Ubuntu 14.04 I expected: to have the fields render as japanese text Instead: When jumping out of the field, the text turns into strange boxes + + + Here is an example file, though taiwanese, a similar thing happens + http://www.koryu.or.jp/kaohsiung-tw/ez3_contents.nsf/15aef977a6d6761f49256de4002084ae/a03c3583dc32699349256ffc00329fea/$FILE/sinseisyo%28tiawan%29.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1422373 Title: evince japanese pdf form writeable but don't render right Status in evince package in Ubuntu: New Bug description: poppler-data is installed, and the file in general renders ok with the japanese. Only the fields to be filled out - allow to input japanese, but then render into weird boxes. evince maintains there is a not embedded 'ZapfDingbats' font in the file, and instead choses Dingbats. this is evince 3.10.3 on an Ubuntu 14.04 I expected: to have the fields render as japanese text Instead: When jumping out of the field, the text turns into strange boxes Here is an example file, though taiwanese, a similar thing happens http://www.koryu.or.jp/kaohsiung-tw/ez3_contents.nsf/15aef977a6d6761f49256de4002084ae/a03c3583dc32699349256ffc00329fea/$FILE/sinseisyo%28tiawan%29.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1422373/+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 944040] Re: Cannot connect to RDP if host fingerprint changes
I have resolved this a number of times on my machine but each time the solution has been different (Alway one of the above). I'm not a programmer so this is pretty arduous to be honest. If there was something I could do to help identify I would be pleased to assist. It is a very random issue and it can go for months without a problem but when it does crop up its a real pain in the ***. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/944040 Title: Cannot connect to RDP if host fingerprint changes Status in remmina package in Ubuntu: Confirmed Bug description: After upgrading to Precise, all my existing connections for RDP are no longer functional. I get the following message: Unable to connect to RDP server XX All connections are in a windows domain. Have tried various O/S's; Win 7, XP, 2008 R2. Same result. Have tried RDP, TLS, NLA and Negoitate. All systems are set to allow all types of RDP traffic. Have verified that the systems are up and function from a Win7 Vbox. Tried creating a new connection, same result. Anything else that would be of help? Debug info attached. (Hopefully) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: remmina 1.0.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Thu Mar 1 09:39:27 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: Upgraded to precise on 2012-02-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/944040/+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 1361189] [NEW] [regression] Cannot easily switch between QWERTY and Dvorak keyboard layouts while using Japanese Anthy input method
Public bug reported: In Precise, it was possible in the System Settings program to separately configure switchable keyboard layouts (e.g., QWERTY, Dvorak) and switchable input methods (e.g., Anthy). That made it possible to use the Anthy input method with a Dvorak keyboard layout and switch between QWERTY and Dvorak for different Japanese typists using one keyboard shortcut for the layout switch and a different keyboard shortcut for the input method switch. In Trusty, the merged Text Entry menu does not support this. The "Japanese (Anthy)" input source always uses whatever keyboard layout was in use last. Thus, switching keyboard layouts while staying with the Anthy input method is very cumbersome. For example, if the user's text entry sources are: English (Dvorak) English (US) Japanese (Anthy) Then to switch from "English (Dvorak)" to "Japanese (Anthy)" with a Dvorak layout, the user must press Shift+Super+Space. If the user instead presses Super+Space twice, they get "Japanese (Anthy)" with a QWERTY layout. Similarly, once "Japanese (Anthy)" is in use with a Dvorak layout, switching to a QWERTY layout with the same input method requires pressing Shift+Super+Space followed by Super+Space. Switching back to Dvorak requires the reverse: Super+Space followed by Shift+Super+Space. Furthermore, this workaround is only possible if the user only wants to switch between two keyboard layouts. If the user wants a third keyboard layout then it is impossible to order them in such a way as to make all of them usable with the user's input method(s). Another user has encountered this problem and posted about it on the forums. http://ubuntuforums.org/showthread.php?t=2223071 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 25 08:13:12 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2012-12-07 (625 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-08-24 (0 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56.1 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-release 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/1361189 Title: [regression] Cannot easily switch between QWERTY and Dvorak keyboard layouts while using Japanese Anthy input method Status in “unity-control-center” package in Ubuntu: New Bug description: In Precise, it was possible in the System Settings program to separately configure switchable keyboard layouts (e.g., QWERTY, Dvorak) and switchable input methods (e.g., Anthy). That made it possible to use the Anthy input method with a Dvorak keyboard layout and switch between QWERTY and Dvorak for different Japanese typists using one keyboard shortcut for the layout switch and a different keyboard shortcut for the input method switch. In Trusty, the merged Text Entry menu does not support this. The "Japanese (Anthy)" input source always uses whatever keyboard layout was in use last. Thus, switching keyboard layouts while staying with the Anthy input method is very cumbersome. For example, if the user's text entry sources are: English (Dvorak) English (US) Japanese (Anthy) Then to switch from "English (Dvorak)" to "Japanese (Anthy)" with a Dvorak layout, the user must press Shift+Super+Space. If the user instead presses Super+Space twice, they get "Japanese (Anthy)" with a QWERTY layout. Similarly, once "Japanese (Anthy)" is in use with a Dvorak layout, switching to a QWERTY layout with the same input method requires pressing Shift+Super+Space followed by Super+Space. Switching back to Dvorak requires the reverse: Super+Space followed by Shift+Super+Space. Furthermore, this workaround is only possible if the user only wants to switch between two keyboard layouts. If the user wants a third keyboard layout then it is impossible to order them in such a way as to make all of them usable with the user's input method(s). Another user has encountered this problem and posted about it on the forums. http://ubuntuforums.org/showth
[Desktop-packages] [Bug 1247736] Re: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd
Also, even with the fix to 331, wine is still not co-installable with nvidia-libopencl1-331-updates for the reason in comment #33. Since that is a problem in the wine dependencies rather than the nividia/opencl dependencies, I am unduping bug 1320217 to cover the wine issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1247736 Title: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd Status in “nvidia-cuda-toolkit” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Status in “ocl-icd” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” source package in Trusty: Invalid Status in “nvidia-graphics-drivers-304” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-304-updates” source package in Trusty: Confirmed Status in “nvidia-graphics-drivers-331” source package in Trusty: Fix Released Status in “nvidia-graphics-drivers-331-updates” source package in Trusty: Fix Released Status in “nvidia-graphics-drivers-340” source package in Trusty: Invalid Status in “ocl-icd” source package in Trusty: Invalid Bug description: [Impact] Users with proprietary Nvidia graphics drivers are unable to co-install CUDA and OpenCL applications. The patches in comment #21 and #22 backport the fix from Utopic and resolve this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader). [SRU Verification Test Case #1] sudo apt-get remove nvidia-opencl-icd-* nvidia-libopencl1-* ocl-icd-ibopencl1 sudo apt-get install nvidia-opencl-icd-331 With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be installed without any dependencies. With the 331.38-0ubuntu7.1 drivers, ocl-icd-libopencl1 will be installed as a dependency: The following extra packages will be installed: ocl-icd-libopencl1 Suggested packages: opencl-icd The following NEW packages will be installed: nvidia-opencl-icd-331 ocl-icd-libopencl1 Repeat the above for nvidia-opencl-icd-331-updates. [SRU Verification Test Case #2] sudo apt-get install nvidia-opencl-icd-331 OR sudo apt-get install nvidia-opencl-icd-331-updates (does not require an Nvidia graphics card) sudo apt-get install beignet (an alternate OpenCL ICD) With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be removed: The following packages will be REMOVED: nvidia-opencl-icd-331 The following NEW packages will be installed: beignet 0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. With the 331.38-0ubuntu7.1 drivers, beignet and nvidia-opencl-icd-331 (or nvidia-opencl-icd-331-updates) can be co-installed. [Test Case] sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install python-pycuda sudo apt-get install python-pyopencl This will result in the error message below. The following packages have unmet dependencies: python-pyopencl : Depends: libopencl-1.1-1 Depends: libopencl-1.2-1 Depends: ocl-icd-libopencl1 but it is not going to be installed E: Unable to correct problems, you have held broken packages. A similar conflict exists between wine and nvidia-cuda-toolkit. sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates (does not require an Nvidia graphics card) sudo apt-get install wine sudo apt-get install nvidia-cuda-toolkit This will result in a warning similar to the one below. The following extra packages will be installed: nvidia-libopencl1-331 nvidia-opencl-dev The following packages will be REMOVED: ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64 wine1.6-i386:i386 The following NEW packages will be installed: nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev [Regression Potential] This fix only affects the relationships between packages and should not introduce any new bugs. However, since packages that were previously difficult to install together will now be co-installable, new bugs in those packages may be exposed. [Other Info] It is possible to work around this issue by first installing the CUDA application, then installing ocl-icd-opencl-dev, and finally installing the OpenCL application. (See comment #7) --- Don't know. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: ocl-icd-libopenc
[Desktop-packages] [Bug 1322925] Re: copy paste not working in Ubuntu 14.04 nautilus
Happens to me too -- 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/1322925 Title: copy paste not working in Ubuntu 14.04 nautilus Status in “nautilus” package in Ubuntu: New Bug description: The title says it. Since upgrade to 14.04, copy / cut / paste of files among various folders I have write rights on does not work most of the times. Using the terminal to copy / move does work normally. nautilus: Installed: 1:3.10.1-0ubuntu9.1 Candidate: 1:3.10.1-0ubuntu9.1 Version table: *** 1:3.10.1-0ubuntu9.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.10.1-0ubuntu8 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1322925/+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 1101919] Re: Display brightness is stuck at lowest setting on GeForce Go 7900 GS
I sold this machine so I cannot provide any more information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1101919 Title: Display brightness is stuck at lowest setting on GeForce Go 7900 GS Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Status in “xserver-xorg-video-nouveau” package in Fedora: Unknown Bug description: I have a Dell XPS M1710 with a GeForce Go 7900 GS and freshly- installed, fully up-to-date Ubuntu 12.10 amd64. When using Nouveau (the default), it is impossible to adjust the display brightness. Moving the slider in Brightness and Lock has no effect on the actual display brightness. The Fn keys for brightness also have no effect (except to move the slider). Worse, even though the default slider position is the max, the actual brightness is the lowest-possible setting, making the machine effectively unusable with Nouveau. The proprietary NVIDIA drivers do work (and are active at the time of reporting this). I am happy to provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-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.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 19 13:57:09 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.5.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G71 [GeForce Go 7900 GS] [10de:0298] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:019b] InstallationDate: Installed on 2013-01-19 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. MXG061 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic root=UUID=a7b8984f-27a9-4805-aee8-60ec72b15c45 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0CF456 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/27/2007:svnDellInc.:pnMXG061:pvr:rvnDellInc.:rn0CF456:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXG061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1101919/+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 172416] Re: eog determines image type from filename
Scanning old print photos at my local Walgreens results in a CD with PNG files named with a .jpg extension, which triggers this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/172416 Title: eog determines image type from filename Status in Eye of GNOME: Confirmed Status in “eog” package in Ubuntu: Triaged Bug description: Binary package hint: eog take any image file, e.g. of type image/jpeg, name it 'image.gif' or 'image.tif' -- eog will assume that image type is gif or tiff. then it will complain, that image is not gif/tiff. but correct behavior is possible: name file 'image' and open it -- eog will determine correct image type. ProblemType: Bug Architecture: i386 Date: Tue Nov 27 23:28:28 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/eog NonfreeKernelModules: nvidia Package: eog 2.20.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: eog file:///home/dmig/Amiga%20Collection/PHOTO/A4000T/a4000t_1.gif ProcCwd: /home/dmig ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: eog Uname: Linux dmig-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/172416/+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 1209315] Re: external screen flickering
update: A workaround for me is: log in, set screen to external only, get flickering. Then, while staying logged in, switch to guest session, and back to own user session -> No flickering appears. When you cycle through display modes, flickering reappears, but you can redo the same workaround. -- 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/1209315 Title: external screen flickering Status in “xorg” package in Ubuntu: New Bug description: Hi, on ubuntu 13.04, 64-bit, my external screen flickers, but only when activated without the laptop screen at full resolution of 1920x1080 px reducing to 1027x768 solves the problem. When having extended desktop over laptop and external screen, no flickering appears. In Windows, I have no flickering, so its neither the cable nor the monitor ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 .tmp.unity.support.test.0: Error: [Errno 13] Permission denied: '/tmp/unity_support_test.0' ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Aug 7 18:43:15 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2104] InstallationDate: Installed on 2013-05-23 (76 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 2733W4W MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=57ad53f8-e7cb-4930-acc1-162034a860a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET79WW (3.09 ) dmi.board.name: 2733W4W dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET79WW(3.09):bd11/19/2009:svnLENOVO:pn2733W4W:pvrThinkPadR500:rvnLENOVO:rn2733W4W:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2733W4W dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed Aug 7 18:39:21 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1209315/+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 1209315] [NEW] external screen flickering
Public bug reported: Hi, on ubuntu 13.04, 64-bit, my external screen flickers, but only when activated without the laptop screen at full resolution of 1920x1080 px reducing to 1027x768 solves the problem. When having extended desktop over laptop and external screen, no flickering appears. In Windows, I have no flickering, so its neither the cable nor the monitor ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 .tmp.unity.support.test.0: Error: [Errno 13] Permission denied: '/tmp/unity_support_test.0' ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Aug 7 18:43:15 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2104] InstallationDate: Installed on 2013-05-23 (76 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 2733W4W MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=57ad53f8-e7cb-4930-acc1-162034a860a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET79WW (3.09 ) dmi.board.name: 2733W4W dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET79WW(3.09):bd11/19/2009:svnLENOVO:pn2733W4W:pvrThinkPadR500:rvnLENOVO:rn2733W4W:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2733W4W dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed Aug 7 18:39:21 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption raring 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/1209315 Title: external screen flickering Status in “xorg” package in Ubuntu: New Bug description: Hi, on ubuntu 13.04, 64-bit, my external screen flickers, but only when activated without the laptop screen at full resolution of 1920x1080 px reducing to 1027x768 solves the problem. When having extended desktop over laptop and external screen, no flickering appears. In Windows, I have no flickering, so its neither the cable nor the monitor ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 .tmp.unity.support.test.0: Error: [Errno 13] Permission denied: '/tmp/unity_support_test.0' ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Aug 7 18:43:15 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Ad
[Desktop-packages] [Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume
I experience the same bug. If I want empathy to connect to my google talk account I must delete it from my account list and suppress the authorization for ubuntu in my google account settings then I have to add again my google account in ubuntu. One thing strange is that when I add again my google account, chromium (which is not my default browser) is launched to a blank page (about:blank) twice: for the login page and for the authorization page. This does not stop the authorization process. I am runnig a 13.04 ubuntu version uptodate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk "Requires Authorization" after suspend/resume Status in “empathy” package in Ubuntu: Confirmed Bug description: Fresh install of raring with all updates. After suspend/resuming my laptop, the google talk account refuses to reconnect, and emparthy says it requires authorization, if I click the button next to requires authorzation it just brings me to UOA and nothing happens. toggling the gtalk account on and off doesn't help, it just requires authorization again. only way to get it back is to reboot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 12 20:14:00 2013 InstallationDate: Installed on 2013-04-12 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+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 1153654] Re: Menus entries are not hilighted anymore
*** This bug is a duplicate of bug 1153350 *** https://bugs.launchpad.net/bugs/1153350 same in 4.0.2-0ubuntu1 -- 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/1153654 Title: Menus entries are not hilighted anymore Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Since latest upgrade, menus entries in LibreOffice are not highlighted any more. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2 Uname: Linux 3.8.0-11-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Mon Mar 11 16:45:54 2013 InstallationDate: Installed on 2013-02-16 (22 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130216) MarkForUpload: True 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/1153654/+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 782005] Re: Cannot click Apply on "Existing Settings" screen of "Change Driver" wizard in printer properties
Here's the PPD as requested. ** Attachment added: "MFC7220.ppd" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/782005/+attachment/3580566/+files/MFC7220.ppd ** Changed in: system-config-printer (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/782005 Title: Cannot click Apply on "Existing Settings" screen of "Change Driver" wizard in printer properties Status in “system-config-printer” package in Ubuntu: New Bug description: Binary package hint: system-config-printer I had a Brother MFC-7220 printer set up with the MFC-7225 driver that ships with Ubuntu, and I needed to change it to the correct MFC-7220 driver from the brother-cups-wrapper-laser package. After installing the package I went to Printing, opened my printer's properties, clicked "Change..." beside "Make and Model", and went through the wizard. But when I got to the "Existing Settings" screen, the Apply button was not selectable, not matter what option I chose! See screenshot. I ended up deleting the printer and re-adding it. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Thu May 12 21:40:31 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lpstat: device for Brother-MFC-7220: ipp://tinygod4:631/printers/Brother-MFC-7220 MachineType: Sony Corporation VGN-CR220E PackageArchitecture: all Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: Brother-MFC-7220: Brother MFC7220 for CUPS ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=f0280dd1-b3ff-4fae-984f-ca2c13d31cb0 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to natty on 2011-04-30 (12 days ago) dmi.bios.date: 06/02/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1121Q0 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:bvnPhoenixTechnologiesLTD:bvrR1121Q0:bd06/02/2008:svnSonyCorporation:pnVGN-CR220E:pvrC101G1S1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CR220E dmi.product.version: C101G1S1 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/782005/+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 782005] Re: Cannot click Apply on "Existing Settings" screen of "Change Driver" wizard in printer properties
This happened again, but on a different computer running Ubuntu 12.04. I was having printer trouble and I noticed that the make and model showed up as simply "Local Raw Printer". I attempted to change it to the MFC-7220 but I was unable to click apply on the "Existing Settings" page. I tried the flow a second time and the same thing happened. Then I tried it from "system-config-printer --debug" to get the information you wanted, but that time the Apply button _was_ enabled. I then cancelled and went back to do it normally (i.e., not running it from the terminal with --debug) and Apply was still enabled. So somehow the --debug run magically fixed things without actually "applying" any change. :/ I've attached the --debug output from the run that magically fixed things. The "No installable options" line is the last one that appeared before cancelling. ** Attachment added: "debug.log" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/782005/+attachment/3580565/+files/debug.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/782005 Title: Cannot click Apply on "Existing Settings" screen of "Change Driver" wizard in printer properties Status in “system-config-printer” package in Ubuntu: New Bug description: Binary package hint: system-config-printer I had a Brother MFC-7220 printer set up with the MFC-7225 driver that ships with Ubuntu, and I needed to change it to the correct MFC-7220 driver from the brother-cups-wrapper-laser package. After installing the package I went to Printing, opened my printer's properties, clicked "Change..." beside "Make and Model", and went through the wizard. But when I got to the "Existing Settings" screen, the Apply button was not selectable, not matter what option I chose! See screenshot. I ended up deleting the printer and re-adding it. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Thu May 12 21:40:31 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lpstat: device for Brother-MFC-7220: ipp://tinygod4:631/printers/Brother-MFC-7220 MachineType: Sony Corporation VGN-CR220E PackageArchitecture: all Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: Brother-MFC-7220: Brother MFC7220 for CUPS ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=f0280dd1-b3ff-4fae-984f-ca2c13d31cb0 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to natty on 2011-04-30 (12 days ago) dmi.bios.date: 06/02/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R1121Q0 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:bvnPhoenixTechnologiesLTD:bvrR1121Q0:bd06/02/2008:svnSonyCorporation:pnVGN-CR220E:pvrC101G1S1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CR220E dmi.product.version: C101G1S1 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/782005/+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 1155900] [NEW] Drivers
Public bug reported: I cannot access additional drivers on my laptop, but my computer's graphics card won't allow for hibernation or suspension. I've read that using proprietary drivers will enable this, but I can't seem to get it done. Thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Mar 16 01:27:34 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:363f] InstallationDate: Installed on 2013-03-08 (8 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard Presario CQ61 Notebook PC MarkForUpload: True ProcEnviron: TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=fc5acb1c-e94f-4fda-bfc9-0f62c58873d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.name: 363F dmi.board.vendor: Hewlett-Packard dmi.board.version: 42.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd05/17/2010:svnHewlett-Packard:pnPresarioCQ61NotebookPC:pvr048E110003200D102:rvnHewlett-Packard:rn363F:rvr42.15:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: Presario CQ61 Notebook PC dmi.product.version: 048E110003200D102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal 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/1155900 Title: Drivers Status in “xorg” package in Ubuntu: New Bug description: I cannot access additional drivers on my laptop, but my computer's graphics card won't allow for hibernation or suspension. I've read that using proprietary drivers will enable this, but I can't seem to get it done. Thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Mar 16 01:27:34 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880M [Mobility Radeon HD 4200 Series] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:363f] InstallationDate: Installed on 2013-03-08 (8 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard Presario CQ61 Notebook PC MarkForUpload: True ProcEnviron: TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=fc5acb1c-e94f-4fda-bfc9-0f62c58873d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.15 dmi.board.name: 363F dmi.board.vendor: Hewlett-Packard dmi.board.version: 42.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd05/17/2010:svnHewlett-Packard:pnPresarioCQ61NotebookPC:pvr048E110003200D102:rvnHewlett-Packar
[Desktop-packages] [Bug 1132030] Re: Facebook account setup opens in external browser, unusable
Same bug here, but now it opens a HTML page hosted on my computer. uname : 3.5.0-25-generic #38-Ubuntu SMP Mon Feb 18 23:27:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1132030 Title: Facebook account setup opens in external browser, unusable Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: When I click on "Facebook" in online accounts, it starts to load the page inside the System Settings window. Then, no matter if my default browser is set to Chromium or Firefox, it opens in an external browser window. I log in, it says "success" but the System Settings window does not recognize this and I am unable to complete the account setup. This works for other online accounts, but not Facebook. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-online-accounts 3.6.2-1 Uname: Linux 3.8.0-030800-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Feb 22 23:43:51 2013 MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1132030/+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 1131192] Re: Can't authorise facebook account in "Online Accounts"
*** This bug is a duplicate of bug 1132030 *** https://bugs.launchpad.net/bugs/1132030 Same bug here, but now it opens a HTML page hosted on my computer. uname : 3.5.0-25-generic #38-Ubuntu SMP Mon Feb 18 23:27:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- 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/1131192 Title: Can't authorise facebook account in "Online Accounts" Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I'm trying to authorise my facebook account in Online Accounts this app opens new window in which I normally enter email and password, but now this window stays blank and firefox starts and opens blank facebook tab with text: "Success!" Example: http://i.imgur.com/lI2PM7C.png ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Feb 21 13:34:25 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-02-21 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-control-center:3162): account-plugin-CRITICAL **: Error removing identity: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/com/google/code/AccountsSSO/SingleSignOn/Identity_3' (firefox:2537): Gtk-CRITICAL **: IA__gtk_clipboard_set_with_data: assertion `targets != NULL' failed (firefox:2537): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: assertion `!display->closed' failed (firefox:2537): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: assertion `!display->closed' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4.2 deja-dup24.0-0ubuntu2 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1131192/+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 615892] Re: Madcatz Cyborg R.A.T. 7 focus issues
** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: Peter Badurek (p-badurek) => NORMAND Tristan (tetris-01) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/615892 Title: Madcatz Cyborg R.A.T. 7 focus issues Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Released Status in “xorg” package in Fedora: Invalid Bug description: Binary package hint: xorg When using the Madcatz Cyborg R.A.T. 7 mouse, Xorg will lock the focus to a single window. The mouse continues to work but all events continue to go to the active window, even when the action is outside the active window. This affects all mice on the system until you unhook the R.A.T. 7. Sometimes clicking the mouse's "Mode" button while over another application will also fix the issue. I've seen this bug using TWM,Metacity and Compiz This also seems to be an issue on Fedora 13, but is fixed in Xorg git as of 2010.08.09. I've replicated the bug in 10.04 and 10.10 alpha 3. I've attached evtest-capture and Xorg.log logs (from fedora 13) --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) Package: xorg 1:7.5+5ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash Tags: lucid Uname: Linux 2.6.35 i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/615892/+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 1113821] Re: libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade
What about putting the conffile in a different directory, symlinking it in the postinst, and deleting the link in the perm? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1113821 Title: libvirt-bin deletes /etc/dnsmasq.d/libvirt-bin on upgrade Status in “libvirt” package in Ubuntu: Triaged Status in “lxc” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Triaged Status in “libvirt” source package in Precise: Triaged Status in “lxc” source package in Precise: Triaged Status in “network-manager” source package in Precise: Triaged Status in “libvirt” source package in Quantal: Triaged Status in “lxc” source package in Quantal: Triaged Status in “network-manager” source package in Quantal: Triaged Status in “libvirt” source package in Raring: Triaged Status in “lxc” source package in Raring: Triaged Status in “network-manager” source package in Raring: Triaged Bug description: libvirt-bin deletes its own NON-obsolete conffile /etc/dnsmasq.d /libvirt-bin in its postrm with "rm", but postrm runs on upgrade, so this causes libvirt-bin to delete its own conffile on upgrade. Hence, anything that relies on /etc/dnsmasq.d/libvirt-bin will break whenever upgrading libvirt-bin to a newer version. libvirt-bin probably should use dpkg-maintscript-helper rm_conffile. Repro steps: 1) Install latest version of libvirt-bin. Observe that /etc/dnsmasq.d/libvirt-bin is present. 2) Purge libvirt-bin and install an old version. Observe that /etc/dnsmasq.d/libvirt-bin is present. 3) Upgrade libvirt-bit to latest version. Observe that /etc/dnsmasq.d/libvirt-bin is gone. Expected: /etc/dnsmasq.d/libvirt-bin should be present on disk after each step, since it is shipped in both versions of the package. Actual: /etc/dnsmasq.d/libvirt-bin is gone after step 3. $ sudo apt-get install libvirt-bin Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: augeas-lenses bridge-utils cgroup-lite ebtables gawk libaugeas0 libnetcf1 libsigsegv2 libvirt0 libxenstore3.0 Suggested packages: augeas-doc gawk-doc augeas-tools qemu-kvm qemu radvd lvm2 The following NEW packages will be installed: augeas-lenses bridge-utils cgroup-lite ebtables gawk libaugeas0 libnetcf1 libsigsegv2 libvirt-bin libvirt0 libxenstore3.0 0 upgraded, 11 newly installed, 0 to remove and 65 not upgraded. Need to get 5,061 kB of archives. After this operation, 17.2 MB of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://us.archive.ubuntu.com/ubuntu/ quantal/main augeas-lenses all 0.10.0-1fakesync1ubuntu1 [179 kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ quantal/main bridge-utils amd64 1.5-4ubuntu2 [32.5 kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ quantal/main ebtables amd64 2.0.9.2-2ubuntu3 [90.3 kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ quantal/main libsigsegv2 amd64 2.9-4ubuntu3 [14.7 kB] Get:5 http://us.archive.ubuntu.com/ubuntu/ quantal/main gawk amd64 1:4.0.1+dfsg-2 [778 kB] Get:6 http://us.archive.ubuntu.com/ubuntu/ quantal/main libaugeas0 amd64 0.10.0-1fakesync1ubuntu1 [176 kB] Get:7 http://us.archive.ubuntu.com/ubuntu/ quantal/main libnetcf1 amd64 0.2.0-1ubuntu1 [51.6 kB] Get:8 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main libvirt0 amd64 0.9.13-0ubuntu12.2 [880 kB] Get:9 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main libxenstore3.0 amd64 4.1.3-3ubuntu1.2 [19.8 kB] Get:10 http://us.archive.ubuntu.com/ubuntu/ quantal/main cgroup-lite all 1.5 [3,944 B] Get:11 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main libvirt-bin amd64 0.9.13-0ubuntu12.2 [2,836 kB] Fetched 5,061 kB in 4s (1,029 kB/s) Selecting previously unselected package augeas-lenses. (Reading database ... 399268 files and directories currently installed.) Unpacking augeas-lenses (from .../augeas-lenses_0.10.0-1fakesync1ubuntu1_all.deb) ... Selecting previously unselected package bridge-utils. Unpacking bridge-utils (from .../bridge-utils_1.5-4ubuntu2_amd64.deb) ... Selecting previously unselected package ebtables. Unpacking ebtables (from .../ebtables_2.0.9.2-2ubuntu3_amd64.deb) ... Selecting previously unselected package libsigsegv2. Unpacking libsigsegv2 (from .../libsigsegv2_2.9-4ubuntu3_amd64.deb) ... Selecting previously unselected package gawk. Unpacking gawk (from .../gawk_1%3a4.0.1+dfsg-2_amd64.deb) ... Selecting previously unselected package libaugeas0. Unpacking libaugeas0 (from .../libaugeas0_0.10.0-1fakesync1ubuntu1_amd64.deb) ... Selecting previously unselected package libnetcf1. Unpacking libnetcf1 (from .../libnetcf1_0.2.0-1ubuntu1_amd64.deb) ... Selecting previously unselected package libvirt0. Unpacking li
[Desktop-packages] [Bug 1101912] Re: nvidia-current does not install prereqs for building kernel module, resulting in broken graphics [Module build for the currently running kernel was skipped since t
IMO it broke more than slightly. Perhaps dkms could depend on linux-generic to prevent this? Even if the installer is fixed, anyone who installs from the original ISO and updates will hit this bug. ** Also affects: dkms (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 in Ubuntu. https://bugs.launchpad.net/bugs/1101912 Title: nvidia-current does not install prereqs for building kernel module, resulting in broken graphics [Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed.] Status in “dkms” package in Ubuntu: New Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I have a freshly-installed, up-to-date Ubuntu 12.10 amd64 machine (Dell XPS M1710 with GeForce Go 7900 GS). I installed nvidia-current from the Additional Drivers tab of Software Sources and it said it succeeded, but upon reboot graphics were busted. The display was low- resolution and Unity failed to start. It appears that nvidia-current did not pull in the prerequisites for building the nvidia kernel module: $ sudo apt-get install --reinstall nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/67.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 147351 files and directories currently installed.) Preparing to replace nvidia-current 304.51.really.304.43-0ubuntu1 (using .../nvidia-current_304.51.really.304.43-0ubuntu1_amd64.deb) ... Removing all DKMS Modules Done. Unpacking replacement nvidia-current ... Processing triggers for man-db ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for gnome-menus ... Setting up nvidia-current (304.51.really.304.43-0ubuntu1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-current DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Processing quirk ThinkPad T420s DEBUG:Failure to match Dell Inc. with LENOVO DEBUG:Quirk doesn't match DEBUG:Processing quirk Latitude E6530 DEBUG:Failure to match MXG061 with Latitude E6530 DEBUG:Quirk doesn't match Loading new nvidia-current-304.43 DKMS files... Building only for 3.5.0-22-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.5.0-22-generic $ ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nvidia-current 304.51.really.304.43-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 19 13:39:45 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43: added GraphicsCard: NVIDIA Corporation G71 [GeForce Go 7900 GS] [10de:0298] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:019b] InstallationDate: Installed on 2013-01-19 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. MXG061 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic root=UUID=a7b8984f-27a9-4805-aee8-60ec72b15c45 ro quiet splash SourcePackage: nvidia-graphics-drivers UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Xlib: extension "GLX" missing on display ":0.0". Error: GLX is not available on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0CF456 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/27/2007:svnDellInc.:pnMXG061:pvr:rvnDellInc.:rn0CF456:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXG061 dmi.sys.vendor: Dell Inc. version.compiz: com
[Desktop-packages] [Bug 1008284] Re: Font size of shutdown dialog in Unity greeter is tiny and unreadable
How can one take a screenshot in the greeter? ** Changed in: unity-greeter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1008284 Title: Font size of shutdown dialog in Unity greeter is tiny and unreadable Status in “unity-greeter” package in Ubuntu: New Bug description: On my desktop computer (System76 Leopard Extreme, model leo1), the font size of the shutdown dialog in the Unity greeter is so tiny that the text is unreadable. This includes the text on the dialog title and buttons too. This is very frustrating when shutting down or restarting the computer from the greeter because I have to remember the order of the buttons to know which one to click. The problem only affects logging in on the physical display, which is using a Sony XBR4 television as its monitor (connected via HDMI). If I bring up the greeter remotely with Xvnc/XDMCP, the font size in that dialog is sensible. I once had a similar problem on this computer with the GDM greeter in an earlier version of Ubuntu (bug 36251, I believe), so this may not be specific to the Unity greeter or LightDM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-greeter 0.2.8-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jun 3 17:55:34 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-greeter UpgradeStatus: Upgraded to precise on 2012-05-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1008284/+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 1101919] [NEW] Display brightness is stuck at lowest setting on GeForce Go 7900 GS
Public bug reported: I have a Dell XPS M1710 with a GeForce Go 7900 GS and freshly-installed, fully up-to-date Ubuntu 12.10 amd64. When using Nouveau (the default), it is impossible to adjust the display brightness. Moving the slider in Brightness and Lock has no effect on the actual display brightness. The Fn keys for brightness also have no effect (except to move the slider). Worse, even though the default slider position is the max, the actual brightness is the lowest-possible setting, making the machine effectively unusable with Nouveau. The proprietary NVIDIA drivers do work (and are active at the time of reporting this). I am happy to provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-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.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 19 13:57:09 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.5.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G71 [GeForce Go 7900 GS] [10de:0298] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:019b] InstallationDate: Installed on 2013-01-19 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. MXG061 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic root=UUID=a7b8984f-27a9-4805-aee8-60ec72b15c45 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0CF456 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/27/2007:svnDellInc.:pnMXG061:pvr:rvnDellInc.:rn0CF456:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXG061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1101919 Title: Display brightness is stuck at lowest setting on GeForce Go 7900 GS Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: I have a Dell XPS M1710 with a GeForce Go 7900 GS and freshly- installed, fully up-to-date Ubuntu 12.10 amd64. When using Nouveau (the default), it is impossible to adjust the display brightness. Moving the slider in Brightness and Lock has no effect on the actual display brightness. The Fn keys for brightness also have no effect (except to move the slider). Worse, even though the default slider position is the max, the actual brightness is the lowest-possible setting, making the machine effectively unusable with Nouveau. The proprietary NVIDIA drivers do work (and are active at the time of reporting this). I am happy to provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-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.n
[Desktop-packages] [Bug 1101912] Re: nvidia-current does not install prereqs for building kernel module, resulting in broken graphics
Workaround: manually install headers for the running kernel and then reinstall nvidia-current. $ sudo apt-get install linux-headers-3.5.0-22-generic Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-headers-3.5.0-22 The following NEW packages will be installed: linux-headers-3.5.0-22 linux-headers-3.5.0-22-generic 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 13.1 MB of archives. After this operation, 69.9 MB of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main linux-headers-3.5.0-22 all 3.5.0-22.34 [12.1 MB] Get:2 http://us.archive.ubuntu.com/ubuntu/ quantal-updates/main linux-headers-3.5.0-22-generic amd64 3.5.0-22.34 [965 kB] Fetched 13.1 MB in 10s (1,208 kB/s) Selecting previously unselected package linux-headers-3.5.0-22. (Reading database ... 147351 files and directories currently installed.) Unpacking linux-headers-3.5.0-22 (from .../linux-headers-3.5.0-22_3.5.0-22.34_all.deb) ... Selecting previously unselected package linux-headers-3.5.0-22-generic. Unpacking linux-headers-3.5.0-22-generic (from .../linux-headers-3.5.0-22-generic_3.5.0-22.34_amd64.deb) ... Setting up linux-headers-3.5.0-22 (3.5.0-22.34) ... Setting up linux-headers-3.5.0-22-generic (3.5.0-22.34) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.5.0-22-generic /boot/vmlinuz-3.5.0-22-generic $ sudo apt-get install --reinstall nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/67.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 170097 files and directories currently installed.) Preparing to replace nvidia-current 304.51.really.304.43-0ubuntu1 (using .../nvidia-current_304.51.really.304.43-0ubuntu1_amd64.deb) ... Removing all DKMS Modules Done. Unpacking replacement nvidia-current ... Processing triggers for man-db ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for gnome-menus ... Setting up nvidia-current (304.51.really.304.43-0ubuntu1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-current DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Processing quirk ThinkPad T420s DEBUG:Failure to match Dell Inc. with LENOVO DEBUG:Quirk doesn't match DEBUG:Processing quirk Latitude E6530 DEBUG:Failure to match MXG061 with Latitude E6530 DEBUG:Quirk doesn't match Loading new nvidia-current-304.43 DKMS files... Building only for 3.5.0-22-generic Building for architecture x86_64 Building initial module for 3.5.0-22-generic Done. nvidia_current: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.5.0-22-generic/updates/dkms/ depmod DKMS: install completed. Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.5.0-22-generic $ sudo modprobe nvidia-current $ echo $? 0 $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1101912 Title: nvidia-current does not install prereqs for building kernel module, resulting in broken graphics Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I have a freshly-installed, up-to-date Ubuntu 12.10 amd64 machine (Dell XPS M1710 with GeForce Go 7900 GS). I installed nvidia-current from the Additional Drivers tab of Software Sources and it said it succeeded, but upon reboot graphics were busted. The display was low- resolution and Unity failed to start. It appears that nvidia-current did not pull in the prerequisites for building the nvidia kernel module: $ sudo apt-get install --reinstall nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/67.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 147351 files and directories currently installed.) Preparing to replace nvidia-current 304.51.really.304.43-0ubuntu1 (using .../nvidia-current_304.51.really.304.43-0ubuntu1_amd6
[Desktop-packages] [Bug 1101912] [NEW] nvidia-current does not install prereqs for building kernel module, resulting in broken graphics
Public bug reported: I have a freshly-installed, up-to-date Ubuntu 12.10 amd64 machine (Dell XPS M1710 with GeForce Go 7900 GS). I installed nvidia-current from the Additional Drivers tab of Software Sources and it said it succeeded, but upon reboot graphics were busted. The display was low-resolution and Unity failed to start. It appears that nvidia-current did not pull in the prerequisites for building the nvidia kernel module: $ sudo apt-get install --reinstall nvidia-current Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/67.7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 147351 files and directories currently installed.) Preparing to replace nvidia-current 304.51.really.304.43-0ubuntu1 (using .../nvidia-current_304.51.really.304.43-0ubuntu1_amd64.deb) ... Removing all DKMS Modules Done. Unpacking replacement nvidia-current ... Processing triggers for man-db ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for gnome-menus ... Setting up nvidia-current (304.51.really.304.43-0ubuntu1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-current DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Processing quirk ThinkPad T420s DEBUG:Failure to match Dell Inc. with LENOVO DEBUG:Quirk doesn't match DEBUG:Processing quirk Latitude E6530 DEBUG:Failure to match MXG061 with Latitude E6530 DEBUG:Quirk doesn't match Loading new nvidia-current-304.43 DKMS files... Building only for 3.5.0-22-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.5.0-22-generic $ ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nvidia-current 304.51.really.304.43-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 19 13:39:45 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43: added GraphicsCard: NVIDIA Corporation G71 [GeForce Go 7900 GS] [10de:0298] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:019b] InstallationDate: Installed on 2013-01-19 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. MXG061 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic root=UUID=a7b8984f-27a9-4805-aee8-60ec72b15c45 ro quiet splash SourcePackage: nvidia-graphics-drivers UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 5: Xlib: extension "GLX" missing on display ":0.0". Error: GLX is not available on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0CF456 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/27/2007:svnDellInc.:pnMXG061:pvr:rvnDellInc.:rn0CF456:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MXG061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad
[Desktop-packages] [Bug 825897] Re: network-manager becomes unresponsive, requiring a service restart
Still repros in 12.10. Also repros in a LiveCD environment, so it's not something with my install. My computer is a System76 Leopard Extreme. I opened a System76 service request but their technicians cannot reproduce the problem with their hardware. My girlfriend recently got a Dell XPS 13 Developer Edition and it also experiences the problem. Interestingly, it has a similar wireless adapter model (Centrino Advanced-N 6235 rev 24). I am thinking that there may be a compatibility problem between Ubuntu, the Centrino Advanced-N 6230/6235, and something in my environment. Perhaps it doesn't like my wireless router (WNDR3700v2) or the fact that there are about three dozen wireless networks in range. As another test, I disabled my wireless router itself while the problem was reproing. Much like when I tested unplugging a wired cable, nm- applet showed that it had been disconnected from the wireless and that it was trying to reconnect, but the applet was still unresponsive to user input. As before, killing and restarting nm-applet made it work properly again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 1096661] Re: Folder Sharing dialog does not install libpam-smbpass if samba is already installed
I don't think it's valid to assume that any user that has installed the samba package manually knows enough to install libpam-smbpass or manage the passwords themselves. In this day and age, the web abounds with many "tutorials" about all aspects of Ubuntu, most of which are grossly out of date or woefully inaccurate. It is entirely possible that the user has manually installed samba but knows next to nothing about its operation. In my case, I installed samba in advance because I knew that the folder sharing function in Nautilus requires it, but I didn't know that libpam- smbpass is also required. After several reboots and /etc/init.d/smbd restarts, I started hunting on the web for solutions and discovered that I needed libpam-smbpass. If an experienced user can use pam-auth-update to avoid the use of libpam-smbpass, then I think installing it all the time is the safest approach. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1096661 Title: Folder Sharing dialog does not install libpam-smbpass if samba is already installed Status in “nautilus-share” package in Ubuntu: New Bug description: If you open the Folder Sharing dialog in Nautilus and click "Share this folder" while neither the samba nor libpam-smbpass packages are installed, then Nautilus automatically prompts you to install samba and then libpam-smbpass. However, if samba is already installed and libpam-smbpass is not, Nautilus does NOT prompt you to install libpam- smbpass. Rather, it happily allows you to enable sharing on the folder, which results in a broken configuration because it is impossible for any user to authenticate to access the folder without libpam-smbpass installed. Expected behaviour: If either samba or libpam-smbpass are not installed, Nautilus should prompt you to install the missing ones. Actual behaviour: If samba is installed and libpam-smbpass is not, Nautilus does not prompt you to install libpam-smbpass and users are unable to authenticate to the shared folder. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus-share 0.7.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Sun Jan 6 10:57:57 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1096661/+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 1096661] [NEW] Folder Sharing dialog does not install libpam-smbpass if samba is already installed
Public bug reported: If you open the Folder Sharing dialog in Nautilus and click "Share this folder" while neither the samba nor libpam-smbpass packages are installed, then Nautilus automatically prompts you to install samba and then libpam-smbpass. However, if samba is already installed and libpam- smbpass is not, Nautilus does NOT prompt you to install libpam-smbpass. Rather, it happily allows you to enable sharing on the folder, which results in a broken configuration because it is impossible for any user to authenticate to access the folder without libpam-smbpass installed. Expected behaviour: If either samba or libpam-smbpass are not installed, Nautilus should prompt you to install the missing ones. Actual behaviour: If samba is installed and libpam-smbpass is not, Nautilus does not prompt you to install libpam-smbpass and users are unable to authenticate to the shared folder. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus-share 0.7.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Sun Jan 6 10:57:57 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus-share UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus-share (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1096661 Title: Folder Sharing dialog does not install libpam-smbpass if samba is already installed Status in “nautilus-share” package in Ubuntu: New Bug description: If you open the Folder Sharing dialog in Nautilus and click "Share this folder" while neither the samba nor libpam-smbpass packages are installed, then Nautilus automatically prompts you to install samba and then libpam-smbpass. However, if samba is already installed and libpam-smbpass is not, Nautilus does NOT prompt you to install libpam- smbpass. Rather, it happily allows you to enable sharing on the folder, which results in a broken configuration because it is impossible for any user to authenticate to access the folder without libpam-smbpass installed. Expected behaviour: If either samba or libpam-smbpass are not installed, Nautilus should prompt you to install the missing ones. Actual behaviour: If samba is installed and libpam-smbpass is not, Nautilus does not prompt you to install libpam-smbpass and users are unable to authenticate to the shared folder. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus-share 0.7.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Sun Jan 6 10:57:57 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1096661/+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 1025087] Re: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again)
** Bug watch added: GNOME Bug Tracker #690930 https://bugzilla.gnome.org/show_bug.cgi?id=690930 ** Also affects: evolution via https://bugzilla.gnome.org/show_bug.cgi?id=690930 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1025087 Title: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again) Status in The Evolution Mail & Calendaring Tool: Unknown Status in “evolution” package in Ubuntu: Confirmed Bug description: This bug is back again. In Precise, double-clicking a date in the calendar applet consistently opens the previous day in Evolution for me. Looking in "ps", the calendar applet is launching Evolution with this command-line for July 25: evolution calendar:///?startdate=20120725T08Z I am in the America/Los_Angeles timezone which is GMT -8 or GMT -7 during DST, so that seems to be a valid date string for July 25 (8 AM GMT is 1 AM PDT or 12 AM PST, either of which should mean July 25), but Evolution interprets it as meaning July 24. By trial and error, I found that the threshold where it will start opening July 25 is 20120725T14Z, i.e. July 25 at 2 PM. For December 1, the threshold is 20121201T16Z, i.e. December 1 at 4 PM. The significance to this is that the offset of 14 in the summer is 7 * 2 and the offset of 16 in the winter is 8 * 2, so it appears that Evolution is incorrectly applying the time zone subtraction twice. This is actually an improvement from Oneiric where it was even more broken (bug 919157), but it is a regression from earlier where everything was working. I can't say for sure which was the last release where this worked, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 15 17:50:29 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-28 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1025087/+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 1025087] Re: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again)
Still present in 12.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1025087 Title: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again) Status in “evolution” package in Ubuntu: Confirmed Bug description: This bug is back again. In Precise, double-clicking a date in the calendar applet consistently opens the previous day in Evolution for me. Looking in "ps", the calendar applet is launching Evolution with this command-line for July 25: evolution calendar:///?startdate=20120725T08Z I am in the America/Los_Angeles timezone which is GMT -8 or GMT -7 during DST, so that seems to be a valid date string for July 25 (8 AM GMT is 1 AM PDT or 12 AM PST, either of which should mean July 25), but Evolution interprets it as meaning July 24. By trial and error, I found that the threshold where it will start opening July 25 is 20120725T14Z, i.e. July 25 at 2 PM. For December 1, the threshold is 20121201T16Z, i.e. December 1 at 4 PM. The significance to this is that the offset of 14 in the summer is 7 * 2 and the offset of 16 in the winter is 8 * 2, so it appears that Evolution is incorrectly applying the time zone subtraction twice. This is actually an improvement from Oneiric where it was even more broken (bug 919157), but it is a regression from earlier where everything was working. I can't say for sure which was the last release where this worked, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 15 17:50:29 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-28 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1025087/+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 1046118] Re: screen powers down after 10 minutes regardless of what Brightness and Lock settings used.
I am experiencing a similar issue in 12.10 using Unity, filed as bug 1072531. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1046118 Title: screen powers down after 10 minutes regardless of what Brightness and Lock settings used. Status in GNOME Shell: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-shell” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Quantal: Triaged Status in “gnome-shell” source package in Quantal: Triaged Bug description: [IMPACT] * Regardless of settings in the "Brightness and Lock" Panel, screen will power off after 10mins. As part of the new lock-screen in gnome-shell 3.6 (when running on gdm), a watchdog timer, that disables the builtin X screensaver was moved into gnome-settings-daemon 3.6. Previously this was in gnome- screensaver however that is no longer used with gnome-shell/gdm combination. Since Quantal is still using gnome-settings-daemon 3.4, currently we are missing the watchdog timer for gnome-shell session on gdm. This is an upstream git patch take from gnome-settings-daemon 3.6. [Test case] 1. Run gnome-shell from gdm. 2. Set "Turn screen Off" in Brightness/lock panel to Never 3. Wait 10mins and the screen will turn off. [Workaround] Install gnome-settings-daemon 3.6 from gnome3-team ppa. [Regression Potential] The code in this patch was copied from gnome-screensaver into gnome-settings-daemon, so should not cause any problems. However when running a session that uses gnome-screensaver (Unity, gnome-shell on Lightdm), this watchdog timer will be duplicated. This is probably harmless but it might be best to patch it out gnome-screensaver. === Original Bug report === Just updated to the latest quantal today and then tried to watch a movie in Totem. Screen powered off every 10 minutes, reliably. Tried setting the power save to 'never', or to '1 hour', tried it with auto screen lock on or off, screen always powers off after 10 minutes exactly. $ lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.4.2-0ubuntu13 Candidate: 1:3.4.2-0ubuntu13 Version table: *** 1:3.4.2-0ubuntu13 0 500 http://ca.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy totem totem: Installed: 3.4.3-0ubuntu2 Candidate: 3.4.3-0ubuntu2 Version table: *** 3.4.3-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-screensaver gnome-screensaver: Installed: 3.5.5-0ubuntu1 Candidate: 3.5.5-0ubuntu1 Version table: *** 3.5.5-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status Let me know what other information is needed to troubleshoot this and I'll gladly help, thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1046118/+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 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
I am using only lightdm and Unity. My lightdm.conf is attached above. Also, in my case the screen does _not_ power down after 10 minutes, it just displays black. i.e., the HDMI display connected to it shows that it is still receiving a signal. By comparison, the "Turn off screen when inactive" setting truly turns off the display and the display reports no signal. But possibly the reporter of bug 1046118 used the term "power down" loosely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in X.Org X server: Won't Fix Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use)
[Desktop-packages] [Bug 1072531]
Thanks Alan. To my knowledge, Ubuntu actually has _never_ had a UI to control this--screen blanking has always been disabled before. The UI only allows the user to configure the time period for powering off the display. Now it seems that screen blanking is mysteriously enabled on some machines in 12.10. Other than with xorg.conf or xset, how might the distro be disabling this? I wasn't able to find any override anywhere. I am guessing that the override is not working in some corner case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in X.Org X server: Won't Fix Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VD
[Desktop-packages] [Bug 1082777] [NEW] Driver suggested by Jockey for BCM4311 on Dell Inspiron E1505 doesn't work
Public bug reported: On this Dell Inspiron E1505, Jockey suggests to use the driver in bcmwl- kernel-source for the BCM4311 wireless card. However, this driver doesn't work. No wireless options show up in nm-applet. For wireless to work, I have to remove bcmwl-kernel-source and install firmware-b43-installer. Based on my web searches, this problem might be due to the fact that this laptop model also has a BCM4401 for wired Ethernet. The b44 kernel module uses the ssb kernel module, which locks the BCM43xx device, preventing the wl kernel module from using it. (I got this info from http://askubuntu.com/questions/139168/dell-1390-wireless- bcm4311-ubuntu-12-04-no-wireless-icon-in-unity.) If this is accurate, then on systems with both a BCM43xx and a BCM44xx Jockey should suggest firmware-b43-installer instead of bcmwl-kernel-source. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.4 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Uname: Linux 3.2.0-32-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Sat Nov 24 17:34:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. MM061 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=ca238997-75f8-480b-bb92-ecc9a9dfd571 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1082777 Title: Driver suggested by Jockey for BCM4311 on Dell Inspiron E1505 doesn't work Status in “jockey” package in Ubuntu: New Bug description: On this Dell Inspiron E1505, Jockey suggests to use the driver in bcmwl-kernel-source for the BCM4311 wireless card. However, this driver doesn't work. No wireless options show up in nm-applet. For wireless to work, I have to remove bcmwl-kernel-source and install firmware-b43-installer. Based on my web searches, this problem might be due to the fact that this laptop model also has a BCM4401 for wired Ethernet. The b44 kernel module uses the ssb kernel module, which locks the BCM43xx device, preventing the wl kernel module from using it. (I got this info from http://askubuntu.com/questions/139168/dell-1390-wireless- bcm4311-ubuntu-12-04-no-wireless-icon-in-unity.) If this is accurate, then on systems with both a BCM43xx and a BCM44xx Jockey should suggest firmware-b43-installer instead of bcmwl-kernel-source. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.4 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Uname: Linux 3.2.0-32-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Sat Nov 24 17:34:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MachineType: Dell Inc. MM061 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=ca238997-75f8-480b-bb92-ecc9a9dfd571 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1082777/+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 1048059] Re: Adding ACLs to /media/$user does not work
ext3 root fs: $ sudo dumpe2fs -h /dev/sda1 | grep -E 'mount options|created' dumpe2fs 1.42.5 (29-Jul-2012) Default mount options:(none) Filesystem created: Thu Sep 17 21:56:42 2009 ext4 homedir: $ sudo dumpe2fs -h /dev/md0 | grep -E 'mount options|created' dumpe2fs 1.42.5 (29-Jul-2012) Default mount options:(none) Filesystem created: Mon Jan 3 14:13:17 2011 ACLs are broken on ext3 root fs: $ touch /tmp/test.txt $ getfacl /tmp/test.txt getfacl: Removing leading '/' from absolute path names # file: tmp/test.txt # owner: tristan # group: tristan user::rw- group::rw- other::r-- $ setfacl -m u:tristan:r /tmp/test.txt setfacl: /tmp/test.txt: Operation not supported $ But working on ext4 homedir: $ touch ~/test.txt $ getfacl ~/test.txt getfacl: Removing leading '/' from absolute path names # file: home/tristan/test.txt # owner: tristan # group: tristan user::rw- group::rw- other::r-- $ setfacl -m u:tristan:r ~/test.txt $ echo $? 0 $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1048059 Title: Adding ACLs to /media/$user does not work Status in The Linux Kernel: New Status in “gnome-settings-daemon” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “udisks2” package in Ubuntu: Confirmed Bug description: Hewlett-Packard HP Envy 14 1095la https://wiki.ubuntu.com/druellan/hpenvy1095la I get an error message -Adding read ACL for uid 999 to `/media/ubuntu' failed: Operation not supported- every time I try to insert a mountable media (CD/DVD/SD card/Pendrive/USB drive). What I expect: Media mounted and visible on Nautilus What I get: An error message, sometimes twice. Note: I'm using a live USB created with UNETBOOTIN, using 700mb of session space. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-13-generic 3.5.0-13.14 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4457 F pulseaudio /dev/snd/controlC0: ubuntu 4457 F pulseaudio CasperVersion: 1.321 CheckboxCommand: removable_storage_watcher insert usb CheckboxTest: usb/insert Date: Sat Sep 8 23:54:40 2012 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2) MachineType: Hewlett-Packard HP ENVY 14 Notebook PC ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern RelatedPackageVersions: linux-restricted-modules-3.5.0-13-generic N/A linux-backports-modules-3.5.0-13-generic N/A linux-firmware1.91 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1436 dmi.board.vendor: Hewlett-Packard dmi.board.version: 59.24 dmi.chassis.asset.tag: CNU0250TQZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 14 Notebook PC dmi.product.version: 0492102419162 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1048059/+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 1048059] Re: Adding ACLs to /media/$user does not work
My fstab doesn't have the acl option set, and I don't recall the acl option ever being there before. I installed this machine years ago from 9.04. Would the 9.04 installer have set that option? If not, perhaps that explains the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1048059 Title: Adding ACLs to /media/$user does not work Status in “gnome-settings-daemon” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “udisks2” package in Ubuntu: Confirmed Bug description: Hewlett-Packard HP Envy 14 1095la https://wiki.ubuntu.com/druellan/hpenvy1095la I get an error message -Adding read ACL for uid 999 to `/media/ubuntu' failed: Operation not supported- every time I try to insert a mountable media (CD/DVD/SD card/Pendrive/USB drive). What I expect: Media mounted and visible on Nautilus What I get: An error message, sometimes twice. Note: I'm using a live USB created with UNETBOOTIN, using 700mb of session space. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-13-generic 3.5.0-13.14 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4457 F pulseaudio /dev/snd/controlC0: ubuntu 4457 F pulseaudio CasperVersion: 1.321 CheckboxCommand: removable_storage_watcher insert usb CheckboxTest: usb/insert Date: Sat Sep 8 23:54:40 2012 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2) MachineType: Hewlett-Packard HP ENVY 14 Notebook PC ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern RelatedPackageVersions: linux-restricted-modules-3.5.0-13-generic N/A linux-backports-modules-3.5.0-13-generic N/A linux-firmware1.91 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1436 dmi.board.vendor: Hewlett-Packard dmi.board.version: 59.24 dmi.chassis.asset.tag: CNU0250TQZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 14 Notebook PC dmi.product.version: 0492102419162 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1048059/+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 1048059] Re: Adding ACLs to /media/$user does not work
ext3 root fs for me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1048059 Title: Adding ACLs to /media/$user does not work Status in “gnome-settings-daemon” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Invalid Status in “udisks2” package in Ubuntu: Confirmed Bug description: Hewlett-Packard HP Envy 14 1095la https://wiki.ubuntu.com/druellan/hpenvy1095la I get an error message -Adding read ACL for uid 999 to `/media/ubuntu' failed: Operation not supported- every time I try to insert a mountable media (CD/DVD/SD card/Pendrive/USB drive). What I expect: Media mounted and visible on Nautilus What I get: An error message, sometimes twice. Note: I'm using a live USB created with UNETBOOTIN, using 700mb of session space. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-13-generic 3.5.0-13.14 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 AcpiTables: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing /usr/share/apport/dump_acpi_tables.py: Permission denied ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4457 F pulseaudio /dev/snd/controlC0: ubuntu 4457 F pulseaudio CasperVersion: 1.321 CheckboxCommand: removable_storage_watcher insert usb CheckboxTest: usb/insert Date: Sat Sep 8 23:54:40 2012 LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2) MachineType: Hewlett-Packard HP ENVY 14 Notebook PC ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 ProcFB: 0 radeondrmfb 1 inteldrmfb ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern RelatedPackageVersions: linux-restricted-modules-3.5.0-13-generic N/A linux-backports-modules-3.5.0-13-generic N/A linux-firmware1.91 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1436 dmi.board.vendor: Hewlett-Packard dmi.board.version: 59.24 dmi.chassis.asset.tag: CNU0250TQZ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd12/01/2011:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr0492102419162:rvnHewlett-Packard:rn1436:rvr59.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 14 Notebook PC dmi.product.version: 0492102419162 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1048059/+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 1038781] Re: -dev packages are missing alternate depends on -extra packages
It's already done for all those dev packages. It's not done for the
libav-dbg package though. Would it make sense to have:
Package: libav-dbg
Section: debug
Priority: extra
Architecture: any
Depends:
libav-tools (= ${binary:Version}),
libavcodec53 (= {binary:Version}) | libavcodec-exttra-53 (>=
${source:Upstream-Version})
...
At the moment, -extra options are not in the "Depends" section.
--
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/1038781
Title:
-dev packages are missing alternate depends on -extra packages
Status in “libav” package in Ubuntu:
Triaged
Bug description:
Since 6:0.8.3-6ubuntu1 you cannot have the libav -dev and -extra
packages installed at the same time. It seems like debian merged the
-extra libs into the regular ones which isn't possible in ubuntu as
those are built from universe.
Package: libavutil-dev
Version: 4:0.8.3-0ubuntu3
Depends: libavutil51 (<= 4:0.8.3-99) | libavutil-extra-51 (<= 4:0.8.3.99),
libavutil51 (>= 4:0.8.3-0ubuntu3) | libavutil-extra-51 (>= 4:0.8.3)
vs.
Package: libavutil-dev
Version: 6:0.8.3-6ubuntu1
Depends: libavutil51 (= 6:0.8.3-6ubuntu1)
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libavutil-dev 4:0.8.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Sun Aug 19 23:56:19 2012
Dependencies:
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007)
ProcEnviron:
SHELL=/bin/bash
TERM=screen-bce
PATH=(custom, user)
LANG=en_US.UTF-8
LANGUAGE=en_US.UTF-8
SourcePackage: libav
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1038781/+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 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
I have now upgraded two other computers to 12.10 and neither of them experience this issue ... To the other people experiencing this bug: are you also using multi-head /multi-seat? (If you've never heard those terms before, the answer is probably no.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabl
[Desktop-packages] [Bug 1038781] Re: -dev packages are missing alternate depends on -extra packages
In Quantal (12.10), libavutil-dev can only be installed if libavutil51 is installed, there's no option for it to depend on libavutil-extra-51. Since libavcodec-dev depends on libavutil-dev, both packages will be uninstalled if we try to install libavcodec-extra-53. The attached patch uses the Depends fields that were in the control file for 12.04, this way libavcodec-dev and libavutil-dev can be installed in parallel with libavcodec-extra-53 and libavutil-extra-51 ** Patch added: "Changed Depends for libavutil-dev" https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1038781/+attachment/3425794/+files/control.patch -- 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/1038781 Title: -dev packages are missing alternate depends on -extra packages Status in “libav” package in Ubuntu: Confirmed Bug description: Since 6:0.8.3-6ubuntu1 you cannot have the libav -dev and -extra packages installed at the same time. It seems like debian merged the -extra libs into the regular ones which isn't possible in ubuntu as those are built from universe. Package: libavutil-dev Version: 4:0.8.3-0ubuntu3 Depends: libavutil51 (<= 4:0.8.3-99) | libavutil-extra-51 (<= 4:0.8.3.99), libavutil51 (>= 4:0.8.3-0ubuntu3) | libavutil-extra-51 (>= 4:0.8.3) vs. Package: libavutil-dev Version: 6:0.8.3-6ubuntu1 Depends: libavutil51 (= 6:0.8.3-6ubuntu1) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libavutil-dev 4:0.8.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Sun Aug 19 23:56:19 2012 Dependencies: InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111007) ProcEnviron: SHELL=/bin/bash TERM=screen-bce PATH=(custom, user) LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1038781/+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 1069954] Re: Packaging issue : add alternative dependency libavutil-extra-51 to libavutil-dev
*** This bug is a duplicate of bug 1038781 *** https://bugs.launchpad.net/bugs/1038781 ** This bug has been marked a duplicate of bug 1038781 -dev packages are missing alternate depends on -extra packages -- 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/1069954 Title: Packaging issue : add alternative dependency libavutil-extra-51 to libavutil-dev Status in “libav” package in Ubuntu: New Bug description: I am trying to install both libavcodec-extra-53 and libavcodec-dev but it doesn't work in quantal because of the conflict between libavutil- extras-53 and libavutil-dev (and possibly other packages, didn't check). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1069954/+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 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
I think the default value of 10 minutes is coming from DEFAULT_SCREEN_SAVER_TIME in include/site.h. I don't understand why it only affects one of my computers though ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprieta
[Desktop-packages] [Bug 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
** Attachment added: "lightdm.conf" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1072531/+attachment/3416979/+files/lightdm.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in “xorg-server” package in Ubuntu: New Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) M
[Desktop-packages] [Bug 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
Workaround: add this to xorg.conf (in my case, to both of them): Section "ServerFlags" Option "BlankTime" "0" EndSection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in “xorg-server” package in Ubuntu: New Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType:
[Desktop-packages] [Bug 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
** Attachment added: "xorg0.conf (for seat #0)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1072531/+attachment/3416954/+files/xorg0.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in “xorg-server” package in Ubuntu: New Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not i
[Desktop-packages] [Bug 1072531] Re: [regression] X11 screen blanking after 10 minutes with no UI to change it
** Attachment added: "xorg1.conf (for seat #1)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1072531/+attachment/3416955/+files/xorg1.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1072531 Title: [regression] X11 screen blanking after 10 minutes with no UI to change it Status in “xorg-server” package in Ubuntu: New Bug description: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not i
[Desktop-packages] [Bug 1072531] [NEW] [regression] X11 screen blanking after 10 minutes with no UI to change it
Public bug reported: After updating from Ubuntu 12.04 Precise to Ubuntu 12.10 Quantal, X11 has started automatically blanking the screen after 10 minutes of inactivity even though I have set "Turn off screen when inactive" in "Brightness and Lock" to 1 hour. If I change "Turn off screen when inactive" to 1 minute, then the screen turns off after 1 minute as it should, but if I set it back to 1 hour then the screen goes back to blanking after 10 minutes, not turning off after 1 hour as it should. So it seems that there are two independent timers and the GUI has no effect on the 10 minute one. Looking in xset, there is indeed a 10-minute screen blanking timeout. $ xset q Keyboard Control: auto repeat: onkey click percent: 0LED mask: 2000 XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: on auto repeat delay: 500repeat rate: 33 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On $ Note that I am using a dual head configuration so I have an xorg0.conf and an xorg1.conf, but there is nothing in either related to screen blanking. Both heads experience the same problem. My other machine that I upgraded from 12.04 to 12.10 does not. Running "xset s 0 0" avoids the problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.gpus.1: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/1' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.43 Sun Aug 19 20:14:03 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,gnomecompat,move,place,regex,resize,snap,animation,vpswitch,session,mousepoll,unitymtgrabhandles,compiztoolbox,wall,expo,workarounds,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sun Oct 28 19:41:51 2012 DistUpgraded: 2012-10-28 10:39:13,985 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: nvidia-current, 304.43, 3.2.0-32-generic, x86_64: installed nvidia-current, 304.43, 3.5.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] NVIDIA Corporation GF110 [GeForce GTX 570] [10de:1081] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1570] JockeyStatus: kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Free, Disabled, Not in use) kmod:nvidia_current - nvidia_current (Proprietary, Enabled, Not in use) kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: System76, Inc. The Leopard Extreme MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=e7728359-15b1-4eb6-a7c9-db1b40e7c807 ro quiet splash SourcePackage: xorg-server UpgradeStatus: Upgraded to quantal on 2012-10-28 (0 days ago) dmi.bios.date: 12/14/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: SOX5810J.86A.5529.2010.1214.2317 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DX58SO dmi.board.vendor: Intel Corporation dmi.board.version: AAE29331-503 dmi.chassis.type: 2 dmi.modalias: dm
[Desktop-packages] [Bug 1072506] [NEW] cupsd.conf should not be a dpkg conffile
Public bug reported: The cups package ships a default config at /etc/cups/cupsd.conf as a dpkg conffile, and the CUPS server modifies this file automatically when settings are changed through GUI tools (e.g., system-config-printer- gnome). When the user upgrades to a later version of Ubuntu, there is virtually always a conflict on this conffile if they have changed any server settings (e.g., enabling printer sharing), and the user is presented with a dpkg keep/replace dialog. This is a problem because if the user was not technically savvy enough to modify the config by hand in the first place, then they are certainly not technically savvy enough to understand the conffile keep/replace dialog. This makes upgrading Ubuntu scary for non-technical users. Since the cupsd.conf format does not seem to be undergoing significant churn, the simplest solution is probably for cupsd.conf to not be a conffile, which can be achieved easily: - Stop shipping /etc/cups/cupsd.conf. Continue to ship /etc/cups/cupsd.conf.default. - In package postinst, if /etc/cups/cupsd.conf does not exist, copy /etc/cups/cupsd.conf.default to /etc/cups/cupsd.conf. If the cupsd.conf format undergoes breaking changes in the future, the postinst could rewrite /etc/cups/cupsd.conf upon upgrade. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Oct 28 16:21:46 2012 InstallationDate: Installed on 2011-04-30 (547 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: device for Brother-MFC-7220: ipp://192.168.1.100:631/printers/Brother-MFC-7220 device for Brother-MFC-7220-local: usb://Brother/MFC-7220?serial=000M9N259310 MachineType: System76, Inc. Serval Professional MarkForUpload: True Papersize: letter PpdFiles: Brother-MFC-7220: Brother MFC7220 for CUPS Brother-MFC-7220-local: Brother MFC7220 for CUPS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=355c2248-a24b-4840-8000-e563ad9d0727 ro quiet splash pcie_aspm=off SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-21 (7 days ago) dmi.bios.date: 06/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: Serval Professional dmi.board.vendor: System76, Inc. dmi.board.version: serp7 dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: serp7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd06/01/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7: dmi.product.name: Serval Professional dmi.product.version: serp7 dmi.sys.vendor: System76, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity ** Description changed: The cups package ships a default config at /etc/cups/cupsd.conf as a dpkg conffile, and the CUPS server modifies this file automatically when settings are changed through GUI tools (e.g., system-config-printer- gnome). When the user upgrades to a later version of Ubuntu, there is virtually always a conflict on this conffile if they have changed any server settings (e.g., enabling printer sharing), and the user is presented with a dpkg keep/replace dialog. This is a problem because if the user was not technically savvy enough to modify the config by hand in the first place, then they are certainly not technically savvy enough to understand the conffile keep/replace dialog. This makes upgrading Ubuntu scary for non-technical users. Since the cupsd.conf format does not seem to be undergoing significant - churn, the simplest solution is probably for the default cupsd.conf to - not be a conffile, which can be achieved easily: + churn, the simplest solution is probably for cupsd.conf to not be a + conffile, which can be achieved easily: - Stop shipping /etc/cups/cupsd.conf. Continue to ship /etc/cups/cupsd.conf.default. - In package postinst, if /etc/cups/cupsd.conf does not exist, copy /etc/cups/cupsd.conf.default to /etc/cups/cupsd.conf. If the cupsd.conf format undergoes breaking changes in the future, the postinst could rewrite /etc/cups/cupsd.conf upon upgrade. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Oct 28 16:21:46 2012 InstallationDate: Installed on 2011-04-30 (547 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) Lpstat: - device for Brother-MFC-7220: ipp://192.168.1.100:631/printers/Br
[Desktop-packages] [Bug 492959] Re: Evince cannot save filled PDF forms
Still repros in 12.10. Confirmed that qpdf --decrypt works around the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/492959 Title: Evince cannot save filled PDF forms Status in Evince document viewer: Confirmed Status in “evince” package in Ubuntu: Confirmed Bug description: Binary package hint: evince Whenever I open a PDF form, and make a change to it (any change, such as filling a field), and then try to save a copy on Evince, the resulting file is empty. Not as in empty fields, but as in zero-bytes-long file. However, when trying to save a copy before any changes have been made, it works fine. This is not the same as bug 299409, since in that bug the resulting files are not empty. The particular form I'm trying to fill is http://www.box.net/shared/static/ia8aliz8ne.pdf To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/492959/+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 1025087] Re: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again)
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1025087 Title: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again) Status in “evolution” package in Ubuntu: New Bug description: This bug is back again. In Precise, double-clicking a date in the calendar applet consistently opens the previous day in Evolution for me. Looking in "ps", the calendar applet is launching Evolution with this command-line for July 25: evolution calendar:///?startdate=20120725T08Z I am in the America/Los_Angeles timezone which is GMT -8 or GMT -7 during DST, so that seems to be a valid date string for July 25 (8 AM GMT is 1 AM PDT or 12 AM PST, either of which should mean July 25), but Evolution interprets it as meaning July 24. By trial and error, I found that the threshold where it will start opening July 25 is 20120725T14Z, i.e. July 25 at 2 PM. For December 1, the threshold is 20121201T16Z, i.e. December 1 at 4 PM. The significance to this is that the offset of 14 in the summer is 7 * 2 and the offset of 16 in the winter is 8 * 2, so it appears that Evolution is incorrectly applying the time zone subtraction twice. This is actually an improvement from Oneiric where it was even more broken (bug 919157), but it is a regression from earlier where everything was working. I can't say for sure which was the last release where this worked, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 15 17:50:29 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-28 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1025087/+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 1025087] [NEW] [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again)
Public bug reported: This bug is back again. In Precise, double-clicking a date in the calendar applet consistently opens the previous day in Evolution for me. Looking in "ps", the calendar applet is launching Evolution with this command-line for July 25: evolution calendar:///?startdate=20120725T08Z I am in the America/Los_Angeles timezone which is GMT -8 or GMT -7 during DST, so that seems to be a valid date string for July 25 (8 AM GMT is 1 AM PDT or 12 AM PST, either of which should mean July 25), but Evolution interprets it as meaning July 24. By trial and error, I found that the threshold where it will start opening July 25 is 20120725T14Z, i.e. July 25 at 2 PM. For December 1, the threshold is 20121201T16Z, i.e. December 1 at 4 PM. The significance to this is that the offset of 14 in the summer is 7 * 2 and the offset of 16 in the winter is 8 * 2, so it appears that Evolution is incorrectly applying the time zone subtraction twice. This is actually an improvement from Oneiric where it was even more broken (bug 919157), but it is a regression from earlier where everything was working. I can't say for sure which was the last release where this worked, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 15 17:50:29 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-28 (78 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1025087 Title: [regression] Double-clicking a date in calendar applet opens the previous day in Evolution (again) Status in “evolution” package in Ubuntu: New Bug description: This bug is back again. In Precise, double-clicking a date in the calendar applet consistently opens the previous day in Evolution for me. Looking in "ps", the calendar applet is launching Evolution with this command-line for July 25: evolution calendar:///?startdate=20120725T08Z I am in the America/Los_Angeles timezone which is GMT -8 or GMT -7 during DST, so that seems to be a valid date string for July 25 (8 AM GMT is 1 AM PDT or 12 AM PST, either of which should mean July 25), but Evolution interprets it as meaning July 24. By trial and error, I found that the threshold where it will start opening July 25 is 20120725T14Z, i.e. July 25 at 2 PM. For December 1, the threshold is 20121201T16Z, i.e. December 1 at 4 PM. The significance to this is that the offset of 14 in the summer is 7 * 2 and the offset of 16 in the winter is 8 * 2, so it appears that Evolution is incorrectly applying the time zone subtraction twice. This is actually an improvement from Oneiric where it was even more broken (bug 919157), but it is a regression from earlier where everything was working. I can't say for sure which was the last release where this worked, though. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 15 17:50:29 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-28 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1025087/+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 919157] Re: The Evolution calendar opens with the wrong date
FYI, no longer repros for me in Precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/919157 Title: The Evolution calendar opens with the wrong date Status in The Date and Time Indicator: Incomplete Status in “evolution” package in Ubuntu: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: The date on the calendar always goes back to 1st of january 1970 when I reopen the application ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Jan 20 12:27:42 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=bs_BA.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2012-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/919157/+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 879066] Re: 10bit video does not play
Still a problem in 12.04 precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/879066 Title: 10bit video does not play Status in The GStreamer Multimedia Framework: New Status in “gstreamer0.10” package in Ubuntu: Confirmed Bug description: Ubuntu 11.10 (amd64); gstreamer0.10-ffmpeg 0.10.12; libavcodec53 OR libavcodec-extra-53 (both yield same results for 10bit). I expect to be able to see 10bit video, since it is supported since libav 0.7 and ffmpeg. instead, the following error comes up: Could not find GStreamer caps mapping for FFmpeg codec 'h264', and you are using an external libavcodec. This is most likely due to a packaging problem and/or libavcodec having been upgraded to a version that is not compatible with this version of gstreamer-ffmpeg. Make sure your gstreamer-ffmpeg and libavcodec packages come from the same source/repository. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libgstreamer0.10-0 0.10.35-1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 20 14:49:39 2011 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/879066/+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 825897] Re: network-manager becomes unresponsive, requiring a service restart
Also repros with 802.11n disabled via: sudo rmmod iwlwifi sudo modprobe iwlwifi 11n_disable=1 So apparently not related to 802.11n as I thought. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 825897] Re: network-manager becomes unresponsive, requiring a service restart
As another test I left my computer connected to only wired, but that did _not_ repro the bug after 1 day. So it seems that having a wireless connection is a requirement. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 825897] Re: network-manager becomes unresponsive, requiring a service restart
Interestingly, physically disconnecting the wired network while the applet was unresponsive _did_ correctly update the applet state, so it wasn't totally hung. But the sub-menus continued to be empty and clicking on anything in the main applet menu continued to be ignored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 825897] Re: network-manager becomes unresponsive, requiring a service restart
As a test I left my computer connected to both wired _and_ wireless, and that also repro'ed the bug after 1 day. Update Manager was open with 4 updates, but it was working properly, so probably the Update Manager hang before was unrelated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 825897] Re: network-manager becomes unresponsive, requiring a service restart
Some more information: I can repro this 100% of the time by enabling wireless, connecting to my 802.11n router, disconnecting from the wired network, and leaving the computer on for a long time. 1 day seems to be sufficient. After that, the NM applet becomes unresponsive--clicking on any menu item does nothing, and the submenus are empty. OTOH, the wireless connection continues to work. Killing and restarting nm-applet fixes the problem. There seems to be no need to restart the network-manager service. In my "normal" day-to-day activities I leave wireless disabled and I leave the computer in sleep mode most of the time, which does NOT repro this. Memory usage of nm-applet in top while unresponsive: 1980 tristan 20 0 624m 23m 12m S0 0.3 1:02.16 nm-applet Backtrace of all threads in nm-applet while unresponsive: (gdb) thread apply all bt Thread 3 (Thread 0x7f2ada61d700 (LWP 1986)): #0 0x7f2ae1eddb03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2ae2422ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ae242345a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2adae5e98b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7f2ae24449a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2ae2b48e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f2ae1ee94bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x in ?? () Thread 2 (Thread 0x7f2ad8dab700 (LWP 1991)): #0 0x7f2ae1eddb03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2ae2422ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ae242345a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ae39432c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f2ae24449a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2ae2b48e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f2ae1ee94bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7f2ae4f17980 (LWP 1980)): #0 0x7f2ae1eddb03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f2ae2422ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ae242345a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00414267 in main (argc=1, argv=0x7fffc4aac088) at main.c:106 Memory usage of nm-applet in top after restarting it: 6244 tristan 20 0 618m 17m 11m S0 0.2 0:00.33 nm-applet Almost identical numbers, so clearly the bug has nothing to do with leaks in nm-applet. Backtrace of all threads in nm-applet after restarting it: (gdb) thread apply all bt Thread 3 (Thread 0x7fe01d188700 (LWP 6245)): #0 0x7fe024a48b03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fe024f8dff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe024f8e45a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe01d9c998b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7fe024faf9a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe0256b3e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7fe024a544bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x in ?? () Thread 2 (Thread 0x7fe0177b1700 (LWP 6246)): #0 0x7fe024a48b03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fe024f8dff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe024f8e45a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe0264ae2c6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fe024faf9a5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe0256b3e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7fe024a544bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7fe027a82980 (LWP 6244)): #0 0x7fe024a48b03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fe024f8dff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe024f8e45a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00414267 in main (argc=1, argv=0x7fff28c08c18) at main.c:106 Also no different, so there does not seem to be any obvious hang in the nm-applet process. Curiously, when this happened today I found that Update Manager was open with 3 updates available, and it was also unresponsive--clicking on it in the launcher did not display the window and I also could not Alt+Tab to it. gdb showed no obvious hangs in the update-manager Python process either. Could be related (but not the root cause, since running Update Manager manually did not repro the problem). -- You received this bug notification because you ar
[Desktop-packages] [Bug 825897] Re: network-manager becomes unresponsive, requiring a service restart
I continue to experience this in 12.04. I am unduping since the symptoms and chronology of this bug bear no resemblance to bug 684599. ** This bug is no longer a duplicate of bug 684599 Memory leak in nm-applet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+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 833507] Re: Nautilus doesn't show thumbnail preview for mp4 video icons
I'm using precise and I have this issue as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/833507 Title: Nautilus doesn't show thumbnail preview for mp4 video icons Status in “totem” package in Ubuntu: Confirmed Bug description: Nautilus does not show a thumbnail preview as the icon for mp4 videos. Instead it shows a generic icon of a "film strip." A snapshot of the video should be displayed as the icon. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Aug 24 23:54:41 2011 ExecutablePath: /usr/bin/nautilus LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/833507/+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 884933] Re: eds keeps prompting me for calendar passwords
Doing the unlock captcha seemed to help for me. It stopped the dialogs and seemed to restore access to the Google calendar in Evolution. The current link is https://www.google.com/accounts/UnlockCaptcha. Would be nice if Evolution could display a message suggesting users to try the unlock captcha. Although OTOH, it must have done something wrong to cause the IMAP access to be blocked in the first place. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/884933 Title: eds keeps prompting me for calendar passwords Status in “evolution-data-server” package in Ubuntu: Confirmed Bug description: EDS keeps popping up dialogs asking me for passwords for my Google calendars, even though I checked "remember password", and the actual password appears to be filled in. I checked via wireshark and I'm not experiencing any authentication failures either, so there's absolutely no reason to keep asking me. This is driving me crazy because the dialogs are popping up in clusters every few minutes, and there's nothing I can do to make them stop popping up. lsb_release -rd: Description: Ubuntu 11.10 Release: 11.10 apt-cache policy evolution-data-server: evolution-data-server: Installed: 3.2.0-0ubuntu1 Candidate: 3.2.0-0ubuntu1 Version table: *** 3.2.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/884933/+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 919157] Re: The Evolution calendar opens with the wrong date
FYI, a work-around is to use View -> Select Today after the calendar opens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/919157 Title: The Evolution calendar opens with the wrong date Status in The Date and Time Indicator: Confirmed Status in “evolution” package in Ubuntu: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: The date on the calendar always goes back to 1st of january 1970 when I reopen the application ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Jan 20 12:27:42 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=bs_BA.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2012-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/919157/+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 817326]
Created attachment 55932 gdb trace of all the calls to close(2) when saving a document Seems reasonable. I used gdb to find all the stacks that call close when saving a file (in 3.4.4, since I didn't have time to build my own package with symbols). There's a lot of calls (27), but most are very similar. Transfer_Impl indeed appears in several, and SfxMedium in almost all of them. I noticed that some of the calls are for backing up stuff. Ideally the backup(s) should be fsync'ed too so that a usable backup will be present even if a power outage occurs in the middle of saving the real file, since copying is not atomic like rename is. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
Not sure when I could fit that in ... I'll see. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 919157] Re: The Evolution calendar opens with the wrong date
Opening against indicator-datetime too since the problem may be on that side. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/919157 Title: The Evolution calendar opens with the wrong date Status in “evolution” package in Ubuntu: Confirmed Status in “indicator-datetime” package in Ubuntu: New Bug description: The date on the calendar always goes back to 1st of january 1970 when I reopen the application ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Jan 20 12:27:42 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=bs_BA.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2012-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/919157/+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 919157] Re: The Evolution calendar opens with the wrong date
Also, as mentioned by Charles on bug 855620, the problem does not occur when clicking "Add Event..." from the applet; Evolution shows the current date. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/919157 Title: The Evolution calendar opens with the wrong date Status in “evolution” package in Ubuntu: Confirmed Bug description: The date on the calendar always goes back to 1st of january 1970 when I reopen the application ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Jan 20 12:27:42 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=bs_BA.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2012-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/919157/+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 66028] Re: double click desktop calendar opens wrong day in evolution
@amias and wribeiro, please see bug 919157 for the 1 January 1970 issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/66028 Title: double click desktop calendar opens wrong day in evolution Status in “gnome-panel” package in Ubuntu: Fix Committed Bug description: When I double click a day on the calendar (top right corner when you click the date), evolution opens that day - except it opens the FOLLOWING day. This is inconvenient and annoying and has led me to mis-schedule some critical events! Since I've realized this happens every time I've had to double check over all my appointments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/66028/+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 919157] Re: The Evolution calendar opens with the wrong date
Same here. This is a regression from Natty. The problem occurs whenever double-clicking a date in the calendar applet. Evolution opens showing the current day's appointments but the calendar in the bottom-left of the Evolution window shows 1 January 1970. If Evolution is opened manually, the calendar correctly shows the current date. If I then double-click a date in the calendar applet, Evolution switches to 1 January 1970. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/919157 Title: The Evolution calendar opens with the wrong date Status in “evolution” package in Ubuntu: Confirmed Bug description: The date on the calendar always goes back to 1st of january 1970 when I reopen the application ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Fri Jan 20 12:27:42 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=bs_BA.UTF-8 SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2012-01-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/919157/+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 855620] Re: calendar applet: double-clicking on a date no longer opens Evolution to that date
Charles, this bug report is not about the date being wrong, it is about Evolution not opening at all. For the date issue, see bug 919157. ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/855620 Title: calendar applet: double-clicking on a date no longer opens Evolution to that date Status in “evolution-data-server” package in Ubuntu: New Bug description: Since upgrading to Oneiric, double-clicking on any date in the Calendar applet no longer opens Evolution to that date. Instead, nothing happens. Verifying in the Overview section of control-center confirms that Evolution is selected as the calendar application, so it must be caused by something else. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution-data-server 3.1.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Wed Sep 21 17:41:44 2011 SourcePackage: evolution-data-server UpgradeStatus: Upgraded to oneiric on 2009-09-14 (737 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/855620/+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 861932] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
I have been affected by this bug on 12.04 Precise Pangolin while launching Shotwell Image Viewer for the first time on i386 release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/861932 Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() Status in “gconf” package in Ubuntu: Confirmed Bug description: Crash happened during first boot of live CD from the "try Ubuntu" selection. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gconf2 3.1.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 CasperVersion: 1.284 CrashCounter: 1 Date: Wed Sep 28 23:57:35 2011 ExecutablePath: /usr/bin/gsettings-data-convert LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) ProcCmdline: gsettings-data-convert ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_settings_set_value () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_settings_set () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/861932/+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 817326]
Created attachment 55708 Small utility to test if fsync() is desirable for a certain path Discovered a small bug in my code, attaching a fixed version. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
Created attachment 55617 Small utility to test if fsync() is desirable for a certain path Here you go. Tested on ext3, ext4, tmpfs, "none" filesystems, procfs, sysfs, and bind mounts, including mount points that are renamed after they are mounted and mount points with whitespace in their paths. I hereby release this file into the public domain. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
FYI, the parse_mounts in your patch won't work for paths containing whitespace. The whitespace characters are translated into octal escape sequences in the file. You'd be better off using setmntent and friends, which handle that for you. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
Actually on second thought there is a simpler and more robust approach, just run realpath() on the document file and then scan /etc/mtab for the longest mount point that is a prefix of the document's path. That way tmpfs and such can be detected correctly. That appears to be how df works. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326] Re: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync
@Evan See comment #26--I tested 3.5.0 Beta 2 too and it still repros. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
I'm not sure the enhancement category is the right fit here. I'm sure loss of data was not one of the design criteria, so it doesn't seem to me like this aspect of LibreOffice can be considered to be working as designed. I'll try out 3.5.0 beta 1 when I get a chance. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
Tested 3.5.0 Beta 2 and the bug persists. My repro steps: 1) Open LibreOffice, type something, and save it. 2) Open GEdit Text Editor, type something, and save it. 3) In a terminal, run "sync". The previously-saved versions are now on disk. 4) Change the LibreOffice document and save again. 5) Change the Text Editor document and save again. 6) Pull out the power cord. After powering up, the GEdit document is intact and contains the latest content, whereas the LibreOffice document is gone forever. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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 817326]
(In reply to comment #13) > If some > enterprising kernel hacker wants to create a nice, ultra-liberally licensed > library that turns a dev_t into a boolean: int is_it_safe_to_fsync (dev_t *t); > then I'd be more than happy to see it used un-conditionally in our > system-abstraction for Unix / Linux. I was actually looking into that recently as part of another project and it's pretty easy. Basically, 1) Stat the file to get the st_dev. 2) Stat each file in /dev/disk/by-uuid to find one with a matching st_rdev. 3) Run realpath() on that file. Now you have the device file holding the filesystem. >From there you can easily look up the filesystem type in many places, e.g. /etc/mtab, /proc/fs, or /sys/fs. Probably /etc/mtab is your best bet since it is a generic UNIX thing. On non-Linux or on Linux without udev you could fall back to stat'ing each file in /dev rather than /dev/disk/by-uuid. -- 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/817326 Title: [Upstream] Previously-saved LibreOffice document lost by power outage (became 0 bytes long) - LibreOffice should call fsync Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: I was working on a document in LibreOffice today while my battery was low and so I was frequently saving, which I thought would help me if I lost power. However, when I eventually did lose power and later rebooted, the document had become 0 bytes long. LibreOffice was not able to restore the auto-saved copy either. As a result, I have lost a whole week of notes for one of my courses. After researching online, it seems that this is caused by the application not calling fsync() (or fdatasync()) when saving files. Due to delayed allocation in modern filesystems, there is no guarantee that the new file's data has actually been written to disk unless the application calls fsync. So if an app writes a new file and replaces the old one with it without fsync'ing the new one first then there is a window of opportunity during which a power failure will result in the loss of BOTH versions of the file. In ext4 this window is also much larger than in ext3. Theodore Tso blogged about this at http://ldn.linuxfoundation.org /blog-entry/delayed-allocation-and-zero-length-file-problem and http://www.linuxfoundation.org/news- media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync. He strongly recommends to call fsync in this situation. Please update LibreOffice to fsync() saved files so that other users do not lose their data like I did. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Wed Jul 27 21:37:02 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to natty on 2011-04-29 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/817326/+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
