[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect
Hello, can you add drivers for the Xbox controller? It's one of the most used controllers on PC and it's annoying because xpadneo disables secure boot. -- 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/1750146 Title: Xbox (One) Wireless Controller won't connect Status in gnome-control-center: Confirmed Status in Linux: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
I have the same problem with a ThinkBook 13x Gen 2 with Ubuntu 23.04. The sound works properly when connecting external speakers or headset, but I couldn't get the internal speakers to work :( This laptop also has an ALC287/3306 chip with a CS35L41/CSC3551 amplifier. This seems very similar what is mentioned here: https://gist.github.com/lamperez/862763881c0e1c812392b5574727f6ff?permalink_comment_id=4526397 journalctl displays the following message: "Error: ACPI _DSD Properties are missing for HID CSC3551". I tried it with the base kernel (6.2.0) as well as the latest one (6.3.3). The issue occurs regarless of the BIOS version (factory version: HXCN49WW and 20230517 version: HXCN52WW). I used the ACPICA tools to extract the ACPI tables and noticed the entries relative to the CSC3551 did not contain the required "cirrus" and "dev-index" parameters. This is quite disapointing and I will juste return the laptop to Lenovo. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1983185] [NEW] Recent commit breaks /etc/X11/Xsession
Public bug reported: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch "true" X session --- "true" not found; falling back to default session." There is a "Okay" button on this message, and clicking it does bad things if one happens to be running Ubuntu 22.04 on Xorg (or running Gnome on Xorg, which is seemingly a different option for the the low latency installation I am running: 5.15.0-43-generic #46-Ubuntu SMP Tue Jul 12 10:30:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). See Brendan O'Dea's related comment about this behavior on debian-bugs- dist: https://www.mail-archive.com/debian-bugs- d...@lists.debian.org/msg1857023.html This has consequences in my use of xpra. For example, if I use xpra via the run_scaled-master script to magnify a single application's interface for a 4K display I get the error dialog mentioned above, often with resulting system instability. This behavior cropped up last month. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sat Jul 30 10:14:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-41-lowlatency, x86_64: installed virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2269] NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2022-07-13 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20MBCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_aze0rg@/vmlinuz-5.15.0-43-generic root=ZFS=rpool/ROOT/ubuntu_aze0rg ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET64W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2CET64W(1.47):bd06/10/2022:br1.47:efr1.16:svnLENOVO:pn20MBCTO1WW:pvrThinkPadP72:rvnLENOVO:rn20MBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20MB_BU_Think_FM_ThinkPadP72: dmi.product.family: ThinkPad P72 dmi.product.name: 20MBCTO1WW dmi.product.sku: LENOVO_MT_20MB_BU_Think_FM_ThinkPad P72 dmi.product.version: ThinkPad P72 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu ** Attachment added: "Screenshot of the Xsession error dialog" https://bugs.launchpad.net/bugs/1983185/+attachment/5606047/+files/Xsession%20error%20dialog.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/1983185 Title: Recent commit breaks /etc/X11/Xsession Status in xorg package in Ubuntu: New Bug description: The following command: $/etc/X11/Xsession true opens a dialog with the following error message: "Xsession: unable to launch
[Desktop-packages] [Bug 1902385] [NEW] At times I have an app. menu that opens and never closes
Public bug reported: It has happened twice in the last little bit where I opened a menu on an icon in the dock and the menu remains opened "forever" (until next reboot). Opening other menus from other icons in the dock works as expected. In most cases, the menu that's stuck is "transparent" to clicks, that is, when I try to click a menu item, the thing behind the menu gets clicked. When I'm able to click on an item in the menu (it turns orange when I do that successfully) then the mouse pointer is stuck over that item and that's it... nothing happens. Using Cmd-Tab to switch between windows waken the mouse up so I could use it again. I tried to restart the GDM3, the dock & menu came back as it was before the restart. sudo systemctl restart display-manager I tried once to Log Out (instead of rebooting) and the graphical interface didn't come back. I tried to restart the GDM from another computer (remotely through SSH) and the screen flashed a bit but it went right back to the boot console. So in other words the Log Out failed. Probably waiting on something that has a deadlock? The only way I've found to fix the issue is to reboot the computer (which I do not like to do too much... plus it takes about 3 min. with my monster server). See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon- menu-gets-stuck-open-any-way-to-fix-that-without-having-to ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:09:43 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Attachment added: "Sample of menu that was stuck earlier." https://bugs.launchpad.net/bugs/1902385/+attachment/5429843/+files/menu-stuck.png -- 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/1902385 Title: At times I have an app. menu that opens and never closes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: It has happened twice in the last little bit where I opened a menu on an icon in the dock and the menu remains opened "forever" (until next reboot). Opening other menus from other icons in the dock works as expected. In most cases, the menu that's stuck is "transparent" to clicks, that is, when I try to click a menu item, the thing behind the menu gets clicked. When I'm able to click on an item in the menu (it turns orange when I do that successfully) then the mouse pointer is stuck over that item and that's it... nothing happens. Using Cmd-Tab to switch between windows waken the mouse up so I could use it again. I tried to restart the GDM3, the dock & menu came back as it was before the restart. sudo systemctl restart display-manager I tried once to Log Out (instead of rebooting) and the graphical interface didn't come back. I tried to restart the GDM from another computer (remotely through SSH) and the screen flashed a bit but it went right back to the boot console. So in other words the Log Out failed. Probably waiting on something that has a deadlock? The only way I've found to fix the issue is to reboot the computer (which I do not like to do too much... plus it takes about 3 min. with my monster server). See also: https://askubuntu.com/questions/1288577/ubuntu-18-04-icon- menu-gets-stuck-open-any-way-to-fix-that-without-having-to ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:09:43 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1883295] [NEW] Xorg freeze
Public bug reported: freeze on show applications menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 11:34:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 605 [17aa:39fd] InstallationDate: Installed on 2020-06-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81J2 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32823WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-14IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN26WW:bd07/09/2019:svnLENOVO:pn81J2:pvrLenovoideapadS130-14IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32823WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-14IGM: dmi.product.family: ideapad S130-14IGM dmi.product.name: 81J2 dmi.product.sku: LENOVO_MT_81J2_BU_idea_FM_ideapad S130-14IGM dmi.product.version: Lenovo ideapad S130-14IGM dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1883295 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: freeze on show applications menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 11:34:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 605 [17aa:39fd] InstallationDate: Installed on 2020-06-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:112b Acer, Inc EasyCamera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81J2 ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=8dc8d3e5-254c-4aea-8f07-294a527b810c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2019 dmi.bios.vendor: LENOVO
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
I had the on Ubuntu 19.10 (and have it still on Ubuntu 20.04). I agree that I see it more frequently in LibreOffice Writer, but I see it elsewhere. Unstable clipboard behavior is unhappy making. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1855489] Re: Chromium auto-restart feature breaks many features
*** This bug is a duplicate of bug 1616650 *** https://bugs.launchpad.net/bugs/1616650 Okay, another updated happened today (version 79.0.3945.79) and I can confirm that it creates the issue where I lose the dot under the Gnome icon. So bug $1616650 definitely looks like the solution to this problem. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: Incomplete Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I insist that changing the Download folder had no effects. That's not the issue in this case. Also, I could download files and they would go in my ~/Downloads folder as expected. No problem on that one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855489/+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 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Me too. CPU: Intel(R) Xeon(R) E-2176M 2.70GHz Ubuntu 19.10 GPU: Nvidi Quadro P4200 |===+==+==| | 0 Quadro P4200 wi... Off | :01:00.0 Off | N/A | | N/A 52CP029W / N/A | 1206MiB / 8119MiB | 4% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1240 G /usr/lib/xorg/Xorg 142MiB | |0 1974 G /usr/lib/xorg/Xorg 416MiB | |0 2225 G /usr/bin/gnome-shell 514MiB | |0 2477 G evolution 75MiB | +-+ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+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 1855489] Re: Chromium auto-restart feature breaks many features
Well, I can't really confirm whether it is a refresh (which I called auto-restart) after an auto-update or a an actual crash... but for sure the window does not change yet it gets disconnected from the Gnome Desktop (and that has happened many times now). At least I'll post to confirm that the history fails next time that happens and I'll check the versions to see whether it happens when an upgrade happens. However, the problem doesn't look like bug #1616650 in terms of functionality, the tabs all remain in place and work just fine without having to restart for many days after it gets disconnected from Gnome. That being said, the read-only folder (point 2) sounds like that could be part of the issue. I'm also not so sure that there was an update. I'll now pay attention to the exact version and see whether it changes next time the dot under the icon disappear. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: Incomplete Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I
[Desktop-packages] [Bug 1855489] [NEW] Chromium auto-restart feature breaks many features
Public bug reported: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the other issues. The features I've noticed that broke completely after such a restart: (1) Gnome Icon The small arrow in the Chromium Icon from my Gnome toolbar (the bar which by default is on the left side of the screen) disappears. That in itself is not the end of the world except that this means I can't click the icon to go back to my window. Clicking the icon opens a new instance. To fix this problem, you would have to run an additional binary. The first binary has to remain in place to hold the icon as expected. Without doing that, you lose the connection to Gnome. There may be other methods to do that. It may also be because you close the old connection to X-Windows and Gnome views that as "now you're gone". Either way, this is not too important to me and it's not a big bad bug in itself. (2) Trying to Install Extensions generates: "Could not create download directory" As such, this error doesn't sound too bad. You should be able to tweak your directory and make sure that it's writable. The fact is that my download directory was just fine. However, it looks like Chrome doesn't think it is. My take is that Chrome has a form of lock and the old lock is still in place making it impossible for new version to access the folders that are locked. This is rather bad since many functionalities may be affected by this. I've only noticed the problem with downloading extensions, but it is not unlikely that other features are also affected in a similar manner. (3) Changing Settings As I was in that situation, I thought I would change my "On Startup" settings so that I could get my windows back on a restart. That way the restart is mostly transparent. Oh but... The changes to the settings did not take; while still using Chromium it looked like it was properly changed, but it was not auto-saved as it ought to be. I am thinking that a similar lock (as mentioned in the previous section) is still in place and it prevents the settings from being saved. (4) Non-Existent History After my restart, the windows did not come back. That is, I only got two windows from a while back... Not the newest windows as I would expect. (i.e. all the windows at the time I last closed the browser). So I decided to check out the history. Nothing. I could only see history from many days ago. Again, my take is that when we had that background auto-restart of Chromium, it was not able to access the history file. It kept the history in memory and never told anyone it couldn't save it anywhere. (Maybe the logs are also affected... I've not checked. But that could explain why developers did not notice and I would imagine that developers open/close the app. all the time). I think this is the worst one. I like to have my history so I can go back to pages where I have been in the past. I don't always use it, but in this very situation I was interested by one specific page and the link is gone. - Note 1: I'm on Ubuntu 18.04 using the Chromium snap version 78.0.3904.108 (64 bit). Note 2: I insist that changing the Download folder had no effects. That's not the issue in this case. Also, I could download files and they would go in my ~/Downloads folder as expected. No problem on that one. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: auto-restart -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855489 Title: Chromium auto-restart feature breaks many features Status in chromium-browser package in Ubuntu: New Bug description: Once in a while, Chromium "auto-restarts" to take advantage of new features and especially apply security patches. This sounds like a great feature only it currently has very bad repercussions (as in, it's terribly bogus). Steps to reproduce: 1. start Chromium 2. browse to various pages 3. let the app. sit there until it auto-restarts 4. from this point on, the app. is bogus, it's not able to save many different things 5. restarting the app. will not see all changes you make between step 3 and 5 (see below) Note that the duration of the session is probably not an issue in itself. I think only the auto-restart feature is what causes all the
[Desktop-packages] [Bug 1079190] Re: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly
I got here because of a question asked on the Ubuntu stack here: https://askubuntu.com/questions/115333/how-do-i-disable-the-sleep- button-on-my-keyboard My keyboard Sleep button is right next to the Esc key. It's just too close and way to easy to end up clicking on it. It would be nicer to have the keys in the usual Keyboard Shortcuts window. It sounds like this should be an easy one since it's very much the same as the other keys... right? -- 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/1079190 Title: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: My keyboard has a "sleep" button on it. I wish to reassign it to open a terminal rather than shut down my computer. To do so, I click on gnome-control-center -> keyboard -> shortcuts -> launchers -> Launch Terminal, then I press the "sleep" button on my keyboard. The "sleep" button appears to be properly assigned to run the terminal command. However, when I press the "sleep" button now, I would expect it to launch a terminal. Instead it puts the computer to sleep. Digging further, it appears that the power buttons on the computer (including those on the keyboard) are controlled by the following dconf settings: org.gnome.settings-daemon.plugins.power button-hibernate org.gnome.settings-daemon.plugins.power button-power org.gnome.settings-daemon.plugins.power button-sleep org.gnome.settings-daemon.plugins.power button-suspend If I use dconf-editor to set these values to 'nothing', then the "sleep" button on my keyboard opens the terminal as expected. The gnome-control-center keyboard shortcuts GUI does not disable the power settings for this button automatically for me. The gnome-control-center keyboard shortcuts GUI should know about and manage the org.gnome.settings-daemon.plugins.power button settings. It should allow the buttons to be re-assigned like other keyboard buttons. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Thu Nov 15 08:33:50 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2012-10-31 (14 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-11-01 (14 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1079190/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
I rebooted on Ubuntu 16.04 (4.4.0-142-generic) and it worked as expected once gpm was turned off. I used the following command to prevent gpm from starting on a reboot and messing up the login screen: sudo systemctl mask gpm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: New Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1814261] Re: gpm prevents loging to the console: spurious “Enter” events seems inserted
I have the exact same problem on Ubuntu 16.04 (vmlinuz-4.4.0-142-generic). I will try to turn off GPM and see how my console functions without it. What a surprise though! Not being able to log in the simplest console. Not something I've seen in ages... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1814261 Title: gpm prevents loging to the console: spurious “Enter” events seems inserted Status in gpm package in Ubuntu: New Bug description: Hello, When our servers boot, We can't login because of spurious “enter”. We have this problem on virtual and physical machines since: * kernel linux-image-4.15.0-44-generic on bionic * kernel linux-image-4.4.0-142-generic on xenial To reproduce: 1. start an ubuntu server with the specific kernel 2. install GPM 3. on a console 1. type the user name “root” 2. hit “enter” 3. wait few seconds => spurious “Enter” are send to the console 4. Stop gpm.service 5. retry to login on a console => no problem lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Same problem with ASUS S406 (no graphic card, CPU i5-8250U) The most awkward thing is sometimes it is working, sometimes it's not. I can't figure out why. When not working, even a restart does not re- enable it but xrandr can enable mirroring laptop display. Any advice? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x25b) 74.250MHz +HSync +VSync
[Desktop-packages] [Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer
I left a message on Canon site, in a survey, about the obsolete dependencies in their Debian package. -- 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/1795150 Title: Canon PIXMA MG4250 unhandled by system-config-printer Status in system-config-printer package in Ubuntu: New Bug description: Let us start by the beginning, and describe my printer’s configuration: it is a Canon Pixma MG4250, connected by Wi-Fi to my internet box, and thus available on my local network. On XUbuntu 18.04.1 LTS (as returned by 'lsb_release -rd'), it is detected by system-config-printer (1.5.11-1ubuntu2, from http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages, as said by 'apt-cache policy system-config-printer'), which by default chooses automatically the corresponding driver, by fails at last step to define the new printer and returns cups-error-internal-error. My first reaction was of course to check the Web for others having a similar problem, and the way they solved it if any did, but I did not find anything relevant. I then tried something else: instead of choosing the automatically detected printer, I gave the URI found on XUbuntu 16.04, which is cnijnet:/ followed by (what I think to be) the MAC address of the printer. I then have to choose a driver (where system-config-printer automatically did it in previous method), but adding the printer still fails at last step, this time with cups-error-not-possible. I found a turnaround, but it is not straightforward: I applied the method which worked on XUbuntu 16.04, which is to use Canon driver (from https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers). I choose the Debian archive from their page (https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers==Linux%20(64-bit)), and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (https://packages.ubuntu.com - but the last one, libtiff14, needs a direct access to tiff directory of the French archive site (http://fr.archive.ubuntu.com/ubuntu/pool/main/t/tiff), as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. I still have to verify whether printing works (but it should be OK). I applied the method which worked on XUbuntu 16.04, which is to use Canon driver. I choose the Debian archive from their page, and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (but the last one, libtiff14, needs a direct access to tiff directory of the French archive site, as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. Everything then works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: system-config-printer 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: 8723de ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 17:23:26 2018 InstallationDate: Installed on 2018-08-10 (50 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Bus 001 Device 002: ID 04ca:707e Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-cf0xxx PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=72197e8c-0319-4e27-a20b-00aab768871f ro quiet splash vt.handoff=1 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B2 dmi.board.vendor: HP dmi.board.version: KBC Version
[Desktop-packages] [Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer
I also had the same problems (and same solution) with a Dell laptop Latitude E6430s, with the same system (fresh install, as upgrade from 16.04 did not work). lsb_release -rd: Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy system-config-printer: system-config-printer: Installé : 1.5.11-1ubuntu2 Candidat : 1.5.11-1ubuntu2 Table de version : *** 1.5.11-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status -- 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/1795150 Title: Canon PIXMA MG4250 unhandled by system-config-printer Status in system-config-printer package in Ubuntu: New Bug description: Let us start by the beginning, and describe my printer’s configuration: it is a Canon Pixma MG4250, connected by Wi-Fi to my internet box, and thus available on my local network. On XUbuntu 18.04.1 LTS (as returned by 'lsb_release -rd'), it is detected by system-config-printer (1.5.11-1ubuntu2, from http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages, as said by 'apt-cache policy system-config-printer'), which by default chooses automatically the corresponding driver, by fails at last step to define the new printer and returns cups-error-internal-error. My first reaction was of course to check the Web for others having a similar problem, and the way they solved it if any did, but I did not find anything relevant. I then tried something else: instead of choosing the automatically detected printer, I gave the URI found on XUbuntu 16.04, which is cnijnet:/ followed by (what I think to be) the MAC address of the printer. I then have to choose a driver (where system-config-printer automatically did it in previous method), but adding the printer still fails at last step, this time with cups-error-not-possible. I found a turnaround, but it is not straightforward: I applied the method which worked on XUbuntu 16.04, which is to use Canon driver (from https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers). I choose the Debian archive from their page (https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers==Linux%20(64-bit)), and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (https://packages.ubuntu.com - but the last one, libtiff14, needs a direct access to tiff directory of the French archive site (http://fr.archive.ubuntu.com/ubuntu/pool/main/t/tiff), as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. I still have to verify whether printing works (but it should be OK). I applied the method which worked on XUbuntu 16.04, which is to use Canon driver. I choose the Debian archive from their page, and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (but the last one, libtiff14, needs a direct access to tiff directory of the French archive site, as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. Everything then works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: system-config-printer 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: 8723de ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 17:23:26 2018 InstallationDate: Installed on 2018-08-10 (50 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Bus 001 Device 002: ID 04ca:707e Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-cf0xxx
[Desktop-packages] [Bug 1795150] Re: Canon PIXMA MG4250 unhandled by system-config-printer
Once the turnaround applied, 'lpstat -v' returns "matériel pour Maison-Canon_MG4250 : cnijnet:/00-BB-C1-90-A8-B4". The computer is a HP Laptop 14-cf0013nf. -- 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/1795150 Title: Canon PIXMA MG4250 unhandled by system-config-printer Status in system-config-printer package in Ubuntu: New Bug description: Let us start by the beginning, and describe my printer’s configuration: it is a Canon Pixma MG4250, connected by Wi-Fi to my internet box, and thus available on my local network. On XUbuntu 18.04.1 LTS (as returned by 'lsb_release -rd'), it is detected by system-config-printer (1.5.11-1ubuntu2, from http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages, as said by 'apt-cache policy system-config-printer'), which by default chooses automatically the corresponding driver, by fails at last step to define the new printer and returns cups-error-internal-error. My first reaction was of course to check the Web for others having a similar problem, and the way they solved it if any did, but I did not find anything relevant. I then tried something else: instead of choosing the automatically detected printer, I gave the URI found on XUbuntu 16.04, which is cnijnet:/ followed by (what I think to be) the MAC address of the printer. I then have to choose a driver (where system-config-printer automatically did it in previous method), but adding the printer still fails at last step, this time with cups-error-not-possible. I found a turnaround, but it is not straightforward: I applied the method which worked on XUbuntu 16.04, which is to use Canon driver (from https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers). I choose the Debian archive from their page (https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers==Linux%20(64-bit)), and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (https://packages.ubuntu.com - but the last one, libtiff14, needs a direct access to tiff directory of the French archive site (http://fr.archive.ubuntu.com/ubuntu/pool/main/t/tiff), as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. I still have to verify whether printing works (but it should be OK). I applied the method which worked on XUbuntu 16.04, which is to use Canon driver. I choose the Debian archive from their page, and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (but the last one, libtiff14, needs a direct access to tiff directory of the French archive site, as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. Everything then works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: system-config-printer 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: 8723de ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 17:23:26 2018 InstallationDate: Installed on 2018-08-10 (50 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Bus 001 Device 002: ID 04ca:707e Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-cf0xxx PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=72197e8c-0319-4e27-a20b-00aab768871f ro quiet splash vt.handoff=1 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B2
[Desktop-packages] [Bug 1795150] [NEW] Canon PIXMA MG4250 unhandled by system-config-printer
Public bug reported: Let us start by the beginning, and describe my printer’s configuration: it is a Canon Pixma MG4250, connected by Wi-Fi to my internet box, and thus available on my local network. On XUbuntu 18.04.1 LTS (as returned by 'lsb_release -rd'), it is detected by system-config-printer (1.5.11-1ubuntu2, from http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages, as said by 'apt-cache policy system-config-printer'), which by default chooses automatically the corresponding driver, by fails at last step to define the new printer and returns cups-error-internal-error. My first reaction was of course to check the Web for others having a similar problem, and the way they solved it if any did, but I did not find anything relevant. I then tried something else: instead of choosing the automatically detected printer, I gave the URI found on XUbuntu 16.04, which is cnijnet:/ followed by (what I think to be) the MAC address of the printer. I then have to choose a driver (where system-config-printer automatically did it in previous method), but adding the printer still fails at last step, this time with cups-error-not-possible. I found a turnaround, but it is not straightforward: I applied the method which worked on XUbuntu 16.04, which is to use Canon driver (from https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers). I choose the Debian archive from their page (https://www.canon.fr/support/consumer_products/products/fax__multifunctionals/inkjet/pixma_mg_series/pixma_mg4250.aspx?type=drivers==Linux%20(64-bit)), and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (https://packages.ubuntu.com - but the last one, libtiff14, needs a direct access to tiff directory of the French archive site (http://fr.archive.ubuntu.com/ubuntu/pool/main/t/tiff), as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. I still have to verify whether printing works (but it should be OK). I applied the method which worked on XUbuntu 16.04, which is to use Canon driver. I choose the Debian archive from their page, and tried to install it. However, it needed three packages (libpango1.0, libpng12 and libtiff14) while only the first is still available on 18.04 (the two others are obsolete). A web search indicated that older packages can be used, I thus got those of the previous LTS (xenius) on the Ubuntu archive site (but the last one, libtiff14, needs a direct access to tiff directory of the French archive site, as the library is not referenced, only its dev part). Once those package are saved and installed (with a sudo dpkg -i ...), Canon’s installation script works fine, and adds the printer. Everything then works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: system-config-printer 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: 8723de ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 17:23:26 2018 InstallationDate: Installed on 2018-08-10 (50 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. Bus 001 Device 002: ID 04ca:707e Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-cf0xxx PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=72197e8c-0319-4e27-a20b-00aab768871f ro quiet splash vt.handoff=1 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B2 dmi.board.vendor: HP dmi.board.version: KBC Version 74.22 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/27/2018:svnHP:pnHPLaptop14-cf0xxx:pvrType1ProductConfigId:rvnHP:rn84B2:rvrKBCVersion74.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-cf0xxx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification
[Desktop-packages] [Bug 1762314] Re: Sound output too low
Same issue here on T570 running Manjaro, this is the only bug report talking about the problem which seems not related to Ubuntu but to alsa. All sliders are up in alsamixer, sound is around half-volume compared to the Windows install. ALSA Driver Version: k4.14.67-1-MANJARO. these did not help: https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low -- 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/1762314 Title: Sound output too low Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound output on lenovo p51s is too low. No option to go above 100% in volume settings. Download pulse audio volume control to raise application and output volume to 153%, which helps to some extent, but then leads to distortion. Was running windows 10 on same system and audio was loud enough! Also after this morning s update, the volume keys no longer work, even after re-mapping them in shortcuts.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jatin 2098 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Apr 8 22:50:04 2018 InstallationDate: Installed on 2018-03-23 (17 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET36W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS06601 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.modalias: dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51s dmi.product.name: 20HCS06601 dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+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 1779829] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’]
*** This bug is a duplicate of bug 1737750 *** https://bugs.launchpad.net/bugs/1737750 I forgot maybe the bug was because I was playing while updating something. Now it is working fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1779829 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: The system tell me that there is an error, however I do not observe the reason for such error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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.15.0-24-generic Date: Tue Jul 3 10:18:46 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv.c:2407:5: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GL [Quadro K600] [103c:094b] InstallationDate: Installed on 2017-04-05 (453 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Z620 Workstation PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic.efi.signed root=UUID=d29b3598-8eb7-440a-8a11-6b959fbb3879 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: CZC3377H35 dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC3377H35 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: Mon Jul 2 11:18:43 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1779829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1779829] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’]
*** This bug is a duplicate of bug 1737750 *** https://bugs.launchpad.net/bugs/1737750 Hello, how are you, some problems with my nvidia gforce 210, EVGA. that my problem with linux. Now let`s see how is going. Because it is working yet. But it reported an bug rigth now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1779829 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: The system tell me that there is an error, however I do not observe the reason for such error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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.15.0-24-generic Date: Tue Jul 3 10:18:46 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv.c:2407:5: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GL [Quadro K600] [103c:094b] InstallationDate: Installed on 2017-04-05 (453 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP Z620 Workstation PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic.efi.signed root=UUID=d29b3598-8eb7-440a-8a11-6b959fbb3879 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: CZC3377H35 dmi.board.name: 158A dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: CZC3377H35 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ620Workstation:pvr:rvnHewlett-Packard:rn158A:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z620 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: Mon Jul 2 11:18:43 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1779829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)
Sure, I don't think anyone has ever looked in this problem, unfortunately. Although "it works for me" now, doesn't mean it's fixed. That's all I'm saying. The code of Thunderbird is huge so I was never able to look enough through it and understand where the problem could be. Anyway, it can be closed since I'm good with the current version and now I make sure I keep compacting my folders... Thank you, Alexis -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/675673 Title: One junk email repeat thousand of times (until thunderbird is stopped) Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird It is the 3rd time that this happens. I do not know why it would happen, but at some point Thunderbird reads an email, decides that it is Junk mail, and moves it to the Junk folder. Then it repeats it over and over again until stopped by closing Thunderbird (the first time, it duplicated the email 5,501 times). When I restart Thunderbird, the problem doesn't repeat itself. I have used Thunderbird for some time now and it is only recently that this behavior started. It happened 3 times now and each time I can tell that it is one single email being duplicated over and over again. Since I do not know why it happens, I have no clue how to reproduce it. I was thinking that it could have something to do with my filters. If it is possible to export those, I'd be glad to post them here. Otherwise, Thunderbird connects to Postfix to download the emails and that works just fine. Just in case, I verified that the email wasn't duplicated on the server and sure enough it isn't. Thank you. Alexis ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.10+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-hostname 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-server x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Nov 15 10:03:14 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/675673/+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 675673] Re: One junk email repeat thousand of times (until thunderbird is stopped)
I don't recall having that bug happen to me for some time. However, it stops only because I understood what was causing some other problem. You have a feature called "Compact Folders" which is bogus and I think that when that other problem occurs, this very bug happens. I have had it with Thunderbird about 2 years ago (when I finally understood that I really had to compact folders.) The problem with compacting folders was that if a local file grows beyond 2Gb, its size is (most certain) viewed as being negative, which then prevents the auto-compaction from happen. As a result, the file continues to grow "forever"--or more precisely until it reaches 4Gb or whatever the limit is on your OS/Filesystem. Once that limit is reached, then you start seeing this very bug appearing. I guess something doesn't know how to get rid of that email and it the code generates an error on the save which tells another piece of code to try again and hence loops forever and adds new emails all the time. I'm pretty such that the file that caused the problem was the one representing the Junk folder on my Local Folders. When I deleted that file, the problems stopped and by making sure I run the compact folders once in a while, the size is kept in check. So, it's not fixed if that file size / compact test is not fixed. Actually, compact should become mandatory once the file is over 1Gb. Who needs that much data in emails?! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/675673 Title: One junk email repeat thousand of times (until thunderbird is stopped) Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird It is the 3rd time that this happens. I do not know why it would happen, but at some point Thunderbird reads an email, decides that it is Junk mail, and moves it to the Junk folder. Then it repeats it over and over again until stopped by closing Thunderbird (the first time, it duplicated the email 5,501 times). When I restart Thunderbird, the problem doesn't repeat itself. I have used Thunderbird for some time now and it is only recently that this behavior started. It happened 3 times now and each time I can tell that it is one single email being duplicated over and over again. Since I do not know why it happens, I have no clue how to reproduce it. I was thinking that it could have something to do with my filters. If it is possible to export those, I'd be glad to post them here. Otherwise, Thunderbird connects to Postfix to download the emails and that works just fine. Just in case, I verified that the email wasn't duplicated on the server and sure enough it isn't. Thank you. Alexis ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.10+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-hostname 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-server x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Nov 15 10:03:14 2010 InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/675673/+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 1720908] [NEW] Firefox cannot load Flash because of libxul broken dependency
Public bug reported: When I start Firefox version 56 in my console and then go to a page using Adobe Flash, I get the following errors: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (94): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (41): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Each time the problem is the same: gdk_screen_get_monitor_workarea is undefined. Gnome marked that function as deprecated, but Firefox version 55 worked just fine, whereas Firefox 56 fails with Flash. https://developer.gnome.org/gdk3/stable/GdkScreen.html#gdk-screen-get- monitor-workarea ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 56.0+build6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexis24733 F pulseaudio /dev/snd/controlC0: alexis24733 F pulseaudio BuildID: 20170928135459 Channel: Unavailable CurrentDesktop: Unity Date: Mon Oct 2 17:05:32 2017 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2010-12-27 (2471 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-33216e86-e3b0-440b-a25a-2754b1171002 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20170928135459 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-05-20 (500 days ago) dmi.bios.date: 09/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P55A-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1720908 Title: Firefox cannot load Flash because of libxul broken dependency Status in firefox package in Ubuntu: New Bug description: When I start Firefox version 56 in my console and then go to a page using Adobe Flash, I get the following errors: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (94): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gdk_screen_get_monitor_workarea [18352] WARNING: pipe error (41): Connection reset by peer: file /build/firefox-6SoPIC/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Each time the problem is the same: gdk_screen_get_monitor_workarea is undefined. Gnome marked that function as deprecated, but Firefox version 55 worked just fine, whereas Firefox 56 fails with Flash. https://developer.gnome.org/g
[Desktop-packages] [Bug 1292324] Re: Support non-root X
Robert, I know you weren't interested in this but would review patches if needed. Could you point people to the right directions on where to drop privileges before running X server and stuff like that? -- 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/1292324 Title: Support non-root X Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm package in Debian: Confirmed Status in lightdm package in Fedora: Unknown Bug description: Support running X as an unprivileged user. Currently X servers are run as root means a large complex process has access to services it might not need (i.e. potential security and stability problems). It would be nice to run each X server as either an unprivileged user or in the session they are being used in. Logind provides a system for sharing access to the display and input devices so this can be done - this seems like the most likely implementation of non-root X. For more information see Hans de Goede request: http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+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 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
same issue exactly from 16.04 to 16.10 here come my log files too. ** Attachment added: "log files" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/4774006/+files/dist-upgrade.tar.gz -- 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/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+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 1292324] Re: Support non-root X
** Bug watch added: Debian Bug tracker #809067 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809067 ** Also affects: lightdm (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809067 Importance: Unknown Status: Unknown -- 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/1292324 Title: Support non-root X Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm package in Debian: Unknown Bug description: Support running X as an unprivileged user. Currently X servers are run as root means a large complex process has access to services it might not need (i.e. potential security and stability problems). It would be nice to run each X server as either an unprivileged user or in the session they are being used in. Logind provides a system for sharing access to the display and input devices so this can be done - this seems like the most likely implementation of non-root X. For more information see Hans de Goede request: http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+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 1516831] Re: XDMCP Request packet with no addresses crashes LightDM
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-8316 -- 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/1516831 Title: XDMCP Request packet with no addresses crashes LightDM Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] If LightDM receives an XDMCP Request packet with no addresses then it will attempt to access a negative index into an array and crash. This only occurs if the XDMCP server is enabled. [Test Case] 1. Enable XDMCP in lightdm.conf: [XDMCPServer] enabled=true 2. Start LightDM 3. Send an XDMCP Request without an empty addresses field (valid XDMCP servers do not send this). Expected result: The request is ignored. Observed result: LightDM crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1516831/+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 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
There is information about KWallet. https://wiki.archlinux.org/index.php/KDE_Wallet It is marked as optional because it is allowed to fail as it does when you are running with Gnome (unity uses Gnome by default). So this is not a bug. You make comment out the lines as shown in #19 but you may regret it if you switch to KUbuntu one day... -- 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/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+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 1370852] Re: Scans all user accounts when not required
It seems that this change actually broke .dmrc files on Debian. I'm currently investigating, but it seems that the files (~/.dmrc and /var/cache/lightdm/dmrc/user.dmrc) are not updated anymore with the selected session. -- 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/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] When AccountsService is not present on startup LightDM scans all the user accounts and attempts to access the dmrc file for each user. It does not use any information from the dmrc files. If you have many users and/or the dmrc files are on a slow filesystem this creates a big startup delay. [Test Case] 1. Start LightDM on a system that doesn't have AccountsService and has many users Expected result: LightDM starts quickly Observed result: LightDM takes a long time to start [Regression potential] Low. We now only access the dmrc files when information from them i s required (lazy load). Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1370852] Re: Scans all user accounts when not required
Actually sorry, that's wrong, it's unrelated, it's due to our own patch setting USERS_DIR to /var/lib/lightdm (I don't really understand why, but that's off-topic for this bug). -- 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/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] When AccountsService is not present on startup LightDM scans all the user accounts and attempts to access the dmrc file for each user. It does not use any information from the dmrc files. If you have many users and/or the dmrc files are on a slow filesystem this creates a big startup delay. [Test Case] 1. Start LightDM on a system that doesn't have AccountsService and has many users Expected result: LightDM starts quickly Observed result: LightDM takes a long time to start [Regression potential] Low. We now only access the dmrc files when information from them i s required (lazy load). Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+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 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP
It seems that gdm now supports setting XDG_CURRENT_DESKTOP but uses the DesktopNames [1] property. It might make sense to migrate LightDM to uses that too. [1] https://bugzilla.gnome.org/show_bug.cgi?id=727546 ** Bug watch added: GNOME Bug Tracker #727546 https://bugzilla.gnome.org/show_bug.cgi?id=727546 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1212408 Title: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP Status in Light Display Manager: Fix Released Status in “gdm” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Bug description: Since the switch to upstart, some processes in the user environment, such as gnome-screensaver, now get launched without $XDG_CURRENT_DESKTOP being set. This is currently causing screen locking issues. This used to get set by gnome-session, but it is no longer high enough in the process tree to set it for the complete user session. Consensus in #ubuntu-desktop was that lightdm should be setting it. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1212408/+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 799069] Re: xf86OpenConsole: setpgid failed
Seems we don't use the patch since long, and it seems to work fine even with plymouth. Sorry for the delay. -- 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/799069 Title: xf86OpenConsole: setpgid failed Status in “lightdm” package in Ubuntu: Fix Released Bug description: Binary package hint: lightdm Oneiric i386 on nvidia (xorg-edgers) got logged into xorg.log: xf86OpenConsole: setpgid failed: Operation not permitted xf86OpenConsole: setsid failed: Operation not permitted i've found similar issue reported but against xdm/slim/wdm: Bug #585853 #19 post seems to point the real problem: - This appears to be caused by the lightdm package not integrating with upstart. - The plymouth process which holds the console open is waiting for a signal that the lightdm job is starting up, so that it can let go of the console; but the lightdm package doesn't have an upstart job, so there's no signal sent, which means the plymouth and lightdm processes are fighting over the console. Note: need to check that the above comments are correct ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.0-1.2-generic-pae 3.0.0-rc3 Uname: Linux 3.0-1-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jun 18 09:26:09 2011 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, no user) LANG=fr_FR.utf8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/799069/+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 1250814] Re: CCSM fails to read current Desktop Size values
*** This bug is a duplicate of bug 1294341 *** https://bugs.launchpad.net/bugs/1294341 The Desktop Size is still affected. But the command: gsettings get org.compiz.core:/org/compiz/profiles/unity/plugins/core/ hsize Seems to work for me. I currently use 2x2 and the command lines give me 2 and 2 as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1250814 Title: CCSM fails to read current Desktop Size values Status in Compiz: In Progress Status in “compiz” package in Ubuntu: In Progress Bug description: Version: Ubuntu 13.10 64-bits Opening the General Options - Desktop Size tab of CompizConfig Settings Manager (CCSM) does not display the (correct) current values for Horizontal-, Vertical Virtual Size and Number of Desktops. The Horizontal Virtual Size is displayed as 1 irrespecitive of the actual value. And worse, just visiting this Desktop Size tab page sets the Horizontal Virtual Size to this unintended value of 1 even if this field is not touched. Not a big problem of course if you are aware of this behavior but it can lead to unexpected changes in workspace settings if you are not. Reproduction: I ran into this problem after installation 13.10. Easiest reproduction however is from a very clean starting point: - create a bootable USB stick following the instructions of http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows - boot the USB stick and select 'Try Ubuntu' - install CompizConfig Settings Manager with Ubuntu Software Center - run CompizConfig Settings Manager and select General Options - Desktop Size ( Not sure if this is the right place to report this problem. Sorry for that) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1250814/+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 1294341] Re: Some of the input fields are blank in CompizConfig Settings Manager
I suppose this was not back ported to 13.10, correct? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1294341 Title: Some of the input fields are blank in CompizConfig Settings Manager Status in Compiz: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Bug description: [Impact] Users trying to use Compiz Config Settings Manager (CCSM) cannot see some of the fields' values. Also, due to this issue, some values will automatically reset to a value not set by the user. This can cause much user frustration when trying to set values in CCSM and can cause behaviors not intended by the user. [Test Case] To reproduce: * Open CCSM by either typing ccsm in the command line or finding it in the Dash. * Browse different settings and notice some of the values are missing in the input boxes. For example, General Options-Edge Trigger Delay is blank. [Regression Potential] None identified. Original Description: Input fields of some of the parameters in CompizConfig Settings Manager are blank. It is possible to modify them by typing a value or by pressing up/down buttons next to the input field. But leaving the particular plugin and returning back leads to the input fields being blank again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compizconfig-settings-manager 1:0.9.11+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Mar 19 00:14:55 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-01-27 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) MachineType: TOSHIBA Satellite U400 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=ade20c72-1376-4808-b6fb-4b0c1cdba8c8 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V3.00 dmi.board.name: Satellite U400 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV3.00:bd07/12/2008:svnTOSHIBA:pnSatelliteU400:pvrPSU40E-02000FRU:rvnTOSHIBA:rnSatelliteU400:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite U400 dmi.product.version: PSU40E-02000FRU dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 18 23:43:31 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14145 vendor SEC xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1294341/+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 1331473] [NEW] Mounting floppy disks via gnome-disks fails.
Public bug reported: The option utf8 is included in the default mount options for floppy disks. This option prevents successful mounting of ext4 file systems. (EXT4-fs (fd0): Unrecognized mount option utf8 or missing value) Lubuntu 14.04, x86. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1331473 Title: Mounting floppy disks via gnome-disks fails. Status in “apport” package in Ubuntu: New Bug description: The option utf8 is included in the default mount options for floppy disks. This option prevents successful mounting of ext4 file systems. (EXT4-fs (fd0): Unrecognized mount option utf8 or missing value) Lubuntu 14.04, x86. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1331473/+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 1329318] [NEW] gpointing-device-settings does not retain settings.
Public bug reported: The application does not retain settings after I log out. One setting that is very important is the ability to disable the tapping feature on the touch pad. Lubuntu 14.04, x86. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1329318 Title: gpointing-device-settings does not retain settings. Status in “apport” package in Ubuntu: New Bug description: The application does not retain settings after I log out. One setting that is very important is the ability to disable the tapping feature on the touch pad. Lubuntu 14.04, x86. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1329318/+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 1328558] [NEW] Lubuntu 14.04 partition issue during installation.
Public bug reported: I'm attempting to install Lubuntu 14.04 on an encrypted volume. During the partitioning phase, partman crashes with an error code of 141. If I disable swap via swapoff -a, the installation proceeds. However, I have to manually create a swap partition after the installation completes. (Also, your bug report didn't allow me to specify partman as the package even though it located it in the search.) ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1328558 Title: Lubuntu 14.04 partition issue during installation. Status in “apport” package in Ubuntu: New Bug description: I'm attempting to install Lubuntu 14.04 on an encrypted volume. During the partitioning phase, partman crashes with an error code of 141. If I disable swap via swapoff -a, the installation proceeds. However, I have to manually create a swap partition after the installation completes. (Also, your bug report didn't allow me to specify partman as the package even though it located it in the search.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1328558/+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 1024482] Re: Mouse cursor theme does not change from default after login
** Also affects: lightdm-gtk-greeter Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #742460 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742460 ** Also affects: lightdm-gtk-greeter (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742460 Importance: Unknown Status: Unknown -- 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/1024482 Title: Mouse cursor theme does not change from default after login Status in LightDM GTK+ Greeter: New Status in “unity-greeter” package in Ubuntu: Confirmed Status in “lightdm” package in Debian: Confirmed Status in “lightdm-gtk-greeter” package in Debian: Unknown Bug description: When using LightDM to login to a GNOME Shell session, the mouse cursor's appearance does not change from what it is in the lightdm login screen (black pointer from default X theme). Any custom mouse cursor theme actually does apply within any open application windows, but hovering the cursor over the window title bar, the root window, or the Shell interface changes it back to the default black pointer, leading to an inconsistent appearance. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1024482/+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 1024482] Re: Mouse cursor theme does not change from default after login
Control: tag -1 confirmed On Sun, Mar 23, 2014 at 11:10:34PM +, Ken Milmore wrote: LightDM causes problems with mouse cursors and startup notifications on the Xfce desktop (and possibly elsewhere). These seem to be caused by the lightdm greeter setting a device-specific cursor on the root window (i.e. a cursor set through XIDefineCursor, called in this case through gdk_window_set_cursor). This cusror overrides any normal cursors set in the desktop environment with XDefineCursor. On Xfce in particular, the most noticeable effect is that application startup notifications do not work - no busy cursor is shown when an application is launched from the desktop or menus. Also, if a pointer theme is set, this is overridden on the root window which continues to show the pointer which was set by lightdm. An easy way to demonstrate this problem is to run xsetroot -cursor_name watch from a terminal window. A busy cursor should appear when the pointer is moved over the desktop; but instead the default arrow cursor remains. This problem appears to have already been reported in several other places: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694353 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671121 https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1024482 The discussion following on from the Ubuntu bug report seems to have got to the root of the problem: When a device cursor has been set, it overrides any ordinary cursor defined on the window. Unfortunately nobody seems to have applied a fix yet. Thanks for the report and the patch. Since there's already a large discussion on the launchpad bug, I'm CC:ing it in order to make discussion there. I would like to suggest that the attached patch be applied, which I have tested on Wheezy with Xfce. It sets the root cursor using XDefineCursor, which avoids the problems caused by the XInput2 cursor precedence rules. A fairly thorough explanation of why this should work appears on comment 15 of the Ubuntu bug report. I think the patch should also apply against Jessie/Sid, although I haven't had a chance to test it on those platforms yet. I'm not completely sure it's the right solution here. I mean, it might be the wisest short-term one, but it'll also break XInput2 features. I guess not much people already use them and I'm not sure how well they work, but I guess the best way to fix the issue would be to use XInput2 API correctly everywhere, so the “right” cursor is always found. I'm not sure what that means concerning “global” cursors like the notification one (I guess it has no reason to be defined until we arrive at the root window), but I guess that's something which should be discussed at the GTK level. Regards, -- Yves-Alexis Perez ** Bug watch added: Debian Bug tracker #694353 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694353 -- 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/1024482 Title: Mouse cursor theme does not change from default after login Status in LightDM GTK+ Greeter: New Status in “unity-greeter” package in Ubuntu: Confirmed Status in “lightdm” package in Debian: Confirmed Status in “lightdm-gtk-greeter” package in Debian: Unknown Bug description: When using LightDM to login to a GNOME Shell session, the mouse cursor's appearance does not change from what it is in the lightdm login screen (black pointer from default X theme). Any custom mouse cursor theme actually does apply within any open application windows, but hovering the cursor over the window title bar, the root window, or the Shell interface changes it back to the default black pointer, leading to an inconsistent appearance. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1024482/+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 967091] Re: Wrong tint in flash when it uses video acceleration
I had that problem on one of my computers where I installed the CUDA development system. The CUDA installs its own libraries and the libvdpau_nvidia.so library was not getting used! I used the following command to remove the offensive vdpau library: sudo rm /usr/lib/libvdpau.so /usr/lib/libvdpau.so.1 /usr/lib/libvdpau.so.304.54 /usr/lib/libvdpau_trace.so Then I restarted my browser and it worked like a charm. You should have another library named: /usr/lib/libvdpau_nvidia.so If not, then you probably will have problems... FYI, I had CUDA installed with: cuda_5.0.35_linux_64_ubuntu11.10-1.run When running 12.04 and it worked fine. When I upgraded to 13.04 I decided to remove CUDA for the time being and still had that color problem. I found the solution (a mention of that library) from this Adobe bug report: https://bugbase.adobe.com/index.cfm?event=bugid=3109467 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/967091 Title: Wrong tint in flash when it uses video acceleration Status in Adobe Flash Plugin Tools: New Status in VDPAU vendor-independent libraries: Fix Released Status in “adobe-flashplugin” package in Ubuntu: Won't Fix Status in “apparmor” package in Ubuntu: Invalid Status in “libvdpau” package in Ubuntu: Fix Released Status in “adobe-flashplugin” source package in Precise: Won't Fix Status in “apparmor” source package in Precise: Fix Released Status in “libvdpau” source package in Precise: Fix Released Status in “adobe-flashplugin” source package in Quantal: Won't Fix Status in “apparmor” source package in Quantal: Invalid Status in “libvdpau” source package in Quantal: Fix Released Status in “adobe-flashplugin” source package in Raring: Won't Fix Status in “apparmor” source package in Raring: Invalid Status in “libvdpau” source package in Raring: Fix Released Status in “flashplugin-nonfree” package in Debian: New Bug description: Using Ubuntu 11.10 64 bit, nvidia binary driver, youtube videos show blue faces after the upgrade to flashplugin 11.2. Didn't occur with 11.1. See example at: http://i.imgur.com/S58GP.jpg SRU description [IMPACT] * Flash videos have the wrong tint (blue faces) on Precise when using nvidia-current or nvidia-current-updates. * This effectively renders Flash videos unwatchable for all LTS users with an NVidia video card. [TESTCASE] * Install nvidia-current, view any Flash video on YouTube, eg. https://www.youtube.com/watch?v=dkVBXW4JeUI. * Reproducable with various Nvidia video cards from at least the GeForce 8 series up to the GeForce 600 series. * Screenshot included in Aloysius' original bug description. [Regression Potential] * While Stephen Warren's patch is not exactly a one-liner, it is rather straightforward and only changes libvdpau's behaviour for Flash. * On the off-chance that this change causes instability, it can be easily disabled via vdpau_wrapper.cfg. * The patch is widely tested, is included in upstream since 0.5 and has been backported for 0.4.1 by the Debian team. The fix is included in Quantal (0.4.1-6ubuntu1). To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/967091/+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 1255514] Re: The spread windows functionality (super+w) does not always work
The issue seems to be fixed after a software update this week ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1255514 Title: The spread windows functionality (super+w) does not always work Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes the spread functionality does not work in a login session. Login out and in again is makes it work. I think the problem always occurs in the first login session after I start my computer. expected behaviour: super+w spreads all the windows on the active workspace actual behaviour: The windows are not spread (and a w is typed in the active window if it's possible to type anything there). (I'm sorry if I indicated the wrong package, I didn't really know which to choose.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CheckboxSubmission: 545f0c3c73676a721a0ffbc52795c2f4 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 27 12:27:20 2013 DistUpgraded: 2013-11-09 12:56:02,508 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1712] NVIDIA Corporation GF108M [GeForce GT 550M] [10de:0df6] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-05-02 (208 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. N53SN MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=4500db2a-7566-47cc-b27b-fc416554b61b ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-11-09 (17 days ago) dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SN.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SN.207:bd07/15/2011:svnASUSTeKComputerInc.:pnN53SN:pvr1.0:rvnASUSTeKComputerInc.:rnN53SN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53SN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Nov 27 12:26:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12620 vendor SEC xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1255514/+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 818852] Re: X cursor often not shown
Looks that this one is fixed indeed. ** Changed in: lightdm-gtk-greeter Status: Triaged = Fix Released -- 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/818852 Title: X cursor often not shown Status in LightDM GTK+ Greeter: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” package in Arch Linux: New Status in “lightdm” package in Debian: Fix Released Bug description: It seems that, since 0.9.2, cursor is often not shown in GTK+ greeter. This is a regression from 0.9.0, afaict, but it might be a GTK+ 3.0 issue too. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/818852/+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 1236569] Re: Close session takes more than three minutes to complete
I closed session twice, the problem occurs always, attached file containing the output of sudo gnome-session --debug ** Attachment added: Debug log https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1236569/+attachment/3867344/+files/Debug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1236569 Title: Close session takes more than three minutes to complete Status in “gnome-session” package in Ubuntu: New Bug description: pressing the logout button, the system takes more than three minutes to close the user's session. There are no messages in the file. Xsession-errors each time the error occurs, displays these messages sys.log file: gnome-session [1809]: WARNING: Client '/ org/gnome/SessionManager/Client1' failed to reply before timeout or gnome-session [2900]: WARNING: Client '/ org/gnome/SessionManager/Client2' failed to reply before timeout The closing session on Ubuntu 13.04 lasted a few seconds. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 16:43:52 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1236569/+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 1236569] [NEW] Close session takes more than three minutes to complete
Public bug reported: pressing the logout button, the system takes more than three minutes to close the user's session. There are no messages in the file. Xsession-errors each time the error occurs, displays these messages sys.log file: gnome-session [1809]: WARNING: Client '/ org/gnome/SessionManager/Client1' failed to reply before timeout or gnome-session [2900]: WARNING: Client '/ org/gnome/SessionManager/Client2' failed to reply before timeout The closing session on Ubuntu 13.04 lasted a few seconds. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 16:43:52 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1236569 Title: Close session takes more than three minutes to complete Status in “gnome-session” package in Ubuntu: New Bug description: pressing the logout button, the system takes more than three minutes to close the user's session. There are no messages in the file. Xsession-errors each time the error occurs, displays these messages sys.log file: gnome-session [1809]: WARNING: Client '/ org/gnome/SessionManager/Client1' failed to reply before timeout or gnome-session [2900]: WARNING: Client '/ org/gnome/SessionManager/Client2' failed to reply before timeout The closing session on Ubuntu 13.04 lasted a few seconds. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 16:43:52 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-07 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1236569/+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 1230172] Re: gnome-calculator menu unreachable when global menu is off
I have the same problem. I cannot use the global menus because I setup my X environment to focus the window my mouse goes over. That really does not work with global menus since I lose those menus as soon as I move the mouse over another window (although Atl-F10 can help, it's not easy to type that one!) So... the gnome-calculator is reduced to a totally unusable simplistic calculator! And there are no command line options from what I can see that would allow me to change the settings. However, as a temporary solution, if we could change the current settings and get a better rendering, it would be great. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1230172 Title: gnome-calculator menu unreachable when global menu is off Status in “gnome-calculator” package in Ubuntu: New Bug description: The Ubuntu's new Enhanced Menu project[1] aims to add the option of choosing whether you want the Global menu or not. Due to a faulty upgrade, my Ubuntu 13.04 desktop turned out to be missing the indicator-appmenu (and dependencies). And without those, there was no global menu. That wasn't a problem for me, until I found out that I couldn't put the gnome-calculator back into PROGRAMMING mode because it had no menu to do so [2]. I tried to hack around a bit in the code, but I didn't get very far. See patch attempt in [2]. Kind regards, Walter Doekes OSSO B.V. [1] https://bugs.launchpad.net/unity/+bug/682788 [2] http://wjd.nu/notes/2013#gnome-calculator-missing-menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1230172/+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 31746] Re: Difficult to find out how to use multiple profiles at the same time
I notice that more than 7 years have passed since this bug has been first reported and it is still happening here in Kubuntu Raring, Firefox 23.0. Will anyone ever take time to fix this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/31746 Title: Difficult to find out how to use multiple profiles at the same time Status in The Mozilla Firefox Browser: Won't Fix Status in “firefox” package in Ubuntu: Invalid Status in “firefox-3.0” package in Ubuntu: Won't Fix Bug description: Since I upgraded to Firefox 1.5 from Dapper, I can no longer use two different profiles at the same time. When I run firefox for the first time, I see the profile manager window and I can choose a profile. If I then run 'firefox -P different-profile-name', I get a new browser window that uses the same profile. If I run 'firefox -ProfileManager', I also get a new browser window instead of the profile manager. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/31746/+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 1173335] Re: Resolution continually switches with dual monitors + screen flickering
Downgrading to 12.10 or 12.04 did not help, my screen was still flickering. I am now on Debian/Gnome and everything is fine. Yet, I occasionally have a minor flickering, I'm not sure whether or not it is the same problem. I still cannot use dual screens without having total random behaviour: monitors alternate between clone, one on one off and both on, like every minute. -- 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/1173335 Title: Resolution continually switches with dual monitors + screen flickering Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I've had this bug since Ubuntu 12.04 and have battled with it for 8+ months. Originally, switching from 11.10 to 12.04, I experienced bad screen flickering (3-45 seconds between flickers) and could not find the issue. I was also not able to run multiple monitors because when I plugged in the HDMI cable, the resolution between screens would continually change (every ~2 seconds) and would not settle on a configuration. I finally was able to fix the issue by switching kernel versions to the 3.4 kernel (back when I had 12.04). When I upgraded to 12.10 (upgrading the kernel again to the default shipped with 12.10), I had the same issue and reinstalled the 3.4 kernel and fixed the issue. Now I'm back to the same issue after upgrading to 13.04. I have screen/window flickering at random intervals and I cannot run an external monitor (although, I can get about 10 minutes out of it before it resets configurations for me). I can't reinstall the 3.4 kernel as there is no version for ringtail. Specs: Description:Ubuntu 13.04 Release:13.04 Memory: 5.7 GiB Processor: Intel® Core™ i7-2640M CPU @ 2.80GHz × 4 Graphics: Intel® Sandybridge Mobile (with discrete AMD graphics) (open source drivers xorg-edgers) OS type: 64-bit lspci dump for discrete graphics card: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] (rev ff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1173335/+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 1207152] [NEW] System freezes when managing graphical windows
Public bug reported: I'm an intensive user of MATLAB. I was using MATLAB R2010b with 10.10 and later with Ubuntu 11.04. I did that for a long time. But a month ago I decided to upgrade to Ubuntu 12.10 and my MATLAB scripts began to crash and freeze the whole system. I was not able to open console sessions with ctrl-alt-f1 .. f6 so the only solution was to restart. This happened everyday. A week ago I decided to upgrade to Ubuntu 13.04 and I also installed a later version of MATLAB: R2013a. But the problems persisted. I installed the app: matlab-support but this did not help. Indeed, I was about to downgrade to Ubuntu 11.04 again, but I foundt the SoftwareUpdates-AdditionalDrivers option. Then, I decided to change the driver of NVIDIA G84GL [Quadro FX 1700] to: VDPAU library from nvidia-310 (proprietary, tested) This driver seems to be working better (No crashes today) but still need to test. Anyway, it is clearly working better than the default (from nouveau). Another small issue that was solved is the text of the path in the title of the console window: when the console window is set to a small size, then the path does not fit in the title section and it is cut off. But with the original dirver the cut looks awful (it looks like the rest of the text is stacked up in the last section looking terrible. With the nvidia-310 driver this bad looking is not happening and the text is being cut off beautifully! This report is for you to check the compatibility of the default driver which seems to be failing. Thanks a lot for Ubuntu. It is a great operating system! ** Affects: nvidia-graphics-drivers (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/1207152 Title: System freezes when managing graphical windows Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I'm an intensive user of MATLAB. I was using MATLAB R2010b with 10.10 and later with Ubuntu 11.04. I did that for a long time. But a month ago I decided to upgrade to Ubuntu 12.10 and my MATLAB scripts began to crash and freeze the whole system. I was not able to open console sessions with ctrl-alt-f1 .. f6 so the only solution was to restart. This happened everyday. A week ago I decided to upgrade to Ubuntu 13.04 and I also installed a later version of MATLAB: R2013a. But the problems persisted. I installed the app: matlab-support but this did not help. Indeed, I was about to downgrade to Ubuntu 11.04 again, but I foundt the SoftwareUpdates-AdditionalDrivers option. Then, I decided to change the driver of NVIDIA G84GL [Quadro FX 1700] to: VDPAU library from nvidia-310 (proprietary, tested) This driver seems to be working better (No crashes today) but still need to test. Anyway, it is clearly working better than the default (from nouveau). Another small issue that was solved is the text of the path in the title of the console window: when the console window is set to a small size, then the path does not fit in the title section and it is cut off. But with the original dirver the cut looks awful (it looks like the rest of the text is stacked up in the last section looking terrible. With the nvidia-310 driver this bad looking is not happening and the text is being cut off beautifully! This report is for you to check the compatibility of the default driver which seems to be failing. Thanks a lot for Ubuntu. It is a great operating system! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1207152/+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 1054615] Re: Gnome-power-statistics will not refresh unless a button is clicked in the window
** Tags added: raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1054615 Title: Gnome-power-statistics will not refresh unless a button is clicked in the window Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Graphs and data will not refresh automatically in the window. To display new collected power data, an action must be taken e.g. in the Laptop BatteryHistory tab, one must click the Show data points checkbox in order to display all the data points taken since the previous refresh (data points taken every 30 seconds) This is a regression. It first appeared with Oneiric, if I remember well. To reproduce: - Open gnome-power-statistics through gnome panel barbattery iconbattery - Go to laptop battery from the left list - Go to History tab: the graph will not refresh when new data points are taken - Click on Show data points or Use smoothed line: the graph (and info in the Details tab) is updated with the last data points ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sat Sep 22 09:48:35 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1054615/+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 1172818] Re: Pidgin doesn't show online facebook contacts
I've exactly the same problem and I have NOT chance anything in my Facebook account. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1172818 Title: Pidgin doesn't show online facebook contacts Status in “pidgin” package in Ubuntu: New Bug description: I use the xmpp facebook connection for years but a few days ago it stopped working. I have no idea what could provoke this, but Pidgin shows every accounts are connected I am online but there not seems to be online facebook friends. They are listed as offline contacts. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pidgin 1:2.10.3-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 Date: Thu Apr 25 21:43:25 2013 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1172818/+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 780117] Re: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 -12.04)
** Changed in: brasero (Ubuntu) Assignee: (unassigned) = metayer alexis (xixi1996) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/780117 Title: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 -12.04) Status in A disc burning application for gnome 2: New Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “brasero” package in Ubuntu: Fix Released Status in “brasero” source package in Precise: Fix Released Status in “brasero” source package in Quantal: Fix Released Status in Baltix GNU/Linux: Fix Committed Status in “brasero” package in Fedora: New Bug description: SRU Justification ~ Impact: Currently Brasero will fail to write files to a disc in on-the-fly mode using the libburnia plugin resulting in 'coastered' media. This is the default mode of operation and unless the user is writing a pre-built ISO image, this fails 100% of the time and has since Oneiric -- possibly Natty. Fix: Complete/fix part of the following commit: http://git.gnome.org/browse/brasero/commit/?id=1b8397ee252df2d554682ca2d694d5937fbf6e39 Particularly the change to plugins/libburnia/burn-libisofs.c around line 200 that hoisted the priv-libburn_src-read_xt() call out of the if() statement should have actually removed it instead of duplicating it. Patch: http://git.gnome.org/browse/brasero/commit/?id=253031b69c5dcbcf079c445ec530afb7ccd9ea82 Test Case: * Insert blank CD or DVD in drive: (1) Attempt to write files to the writable optical disc by dragging files from Nautilus to a blank disc. (2) Click on the 'Write Files to Disc' button in nautilus. (3) Make sure 'on the fly' mode is enabled by selecting 'Burn image directly without saving to disc' (which should be the default). (4) Click on the 'burn' button. * If the bug is fixed, you should have a properly written and readable disc. Otherwise, the procedure will fail and the disc will be unusable. -- Binary package hint: brasero When I burn a DVD (4,7 and 8,5 GB) Brasero show the progressbar till about 30-40% (exact point is randomly) and than says, that it is finalizing the media. This finalizing messages is showing for the rest of the burning process (~10min @8x 8,5GB). After that, it ejects the media without any error. But when I insert the media again, nothing happens, except, that the DVD-Drive disappears from the computer:/// location in nautilus. This problem only exists when burning On-The-Fly. Burning ISO Images or automatic creation of ISO Images before burning works without problems. The burning speed doesn't matter to this problem. I test 8x, 4x and 2x. All the same problem. On-The-Fly burning using K3B works quite well @8x speed. One thing I also notice is, that Brasero uses 100% CPU on one core, while K3B uses just about 5-15%. I attached the last Brasero log. I don't know, why it just says, that it was only at 49% and then says it's finished. The burning took about 28 minutes. The media was unusable on all my three devices (Linux/Windows). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: brasero 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon May 9 22:10:24 2011 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (brasero:2453): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()' (brasero:2453): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed (unknown:4557): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/780117/+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 1133879] [NEW] Display problems (ATI RS690)
Public bug reported: Enabling the Unity dash to select an application, the system is extremely slow and display errors are observed. This problem also occurs in Firefox tabs when closing the Unity Dash. ~$ lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 ~$ apt-cache policy xserver-xorg-video-ati xserver-xorg-video-ati: Instalados: 1:7.1.0-0ubuntu1 Candidato: 1:7.1.0-0ubuntu1 Tabla de versión: *** 1:7.1.0-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 27 03:47:43 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0213] LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) MachineType: eMachines eMachines E625 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2009 dmi.bios.vendor: eMachines dmi.bios.version: V1.11 dmi.board.name: HM50-YK dmi.board.vendor: eMachines dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: N/A dmi.modalias: dmi:bvneMachines:bvrV1.11:bd06/03/2009:svneMachines:pneMachinesE625:pvrV1.11:rvneMachines:rnHM50-YK:rvrN/A:cvneMachines:ct10:cvrN/A: dmi.product.name: eMachines E625 dmi.product.version: V1.11 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Wed Feb 27 02:45:29 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: radeon ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring running-unity ubuntu ** Attachment added: Bug.png https://bugs.launchpad.net/bugs/1133879/+attachment/3548655/+files/Bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1133879 Title: Display problems (ATI RS690) Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: Enabling the Unity dash to select an application, the system is extremely slow and display errors are observed. This problem also occurs in Firefox tabs when closing the Unity Dash. ~$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 ~$ apt-cache policy xserver-xorg-video-ati xserver-xorg-video-ati: Instalados: 1:7.1.0-0ubuntu1 Candidato: 1:7.1.0-0ubuntu1 Tabla de versión: *** 1:7.1.0-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 27 03:47:43 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI
[Desktop-packages] [Bug 1133879] Re: Display problems (ATI RS690)
** Attachment added: Bug1.2 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1133879/+attachment/3548676/+files/Bug1.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1133879 Title: Display problems (ATI RS690) Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: Enabling the Unity dash to select an application, the system is extremely slow and display errors are observed. This problem also occurs in Firefox tabs when closing the Unity Dash. ~$ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 ~$ apt-cache policy xserver-xorg-video-ati xserver-xorg-video-ati: Instalados: 1:7.1.0-0ubuntu1 Candidato: 1:7.1.0-0ubuntu1 Tabla de versión: *** 1:7.1.0-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CasperVersion: 1.330 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 27 03:47:43 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0213] LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) MachineType: eMachines eMachines E625 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2009 dmi.bios.vendor: eMachines dmi.bios.version: V1.11 dmi.board.name: HM50-YK dmi.board.vendor: eMachines dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: N/A dmi.modalias: dmi:bvneMachines:bvrV1.11:bd06/03/2009:svneMachines:pneMachinesE625:pvrV1.11:rvneMachines:rnHM50-YK:rvrN/A:cvneMachines:ct10:cvrN/A: dmi.product.name: eMachines E625 dmi.product.version: V1.11 dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.9~daily13.02.19-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 xserver.bootTime: Wed Feb 27 02:45:29 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1133879/+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 1020506] Re: Hangs with Insert Comment then Insert Hyperlink
Similar problem here. Let me describe it: 1 - I select a text 2 - Click on Insert - Hyperlink 3 - Begin to type a hyperlink 4 - The URL text box starts responding very slowly to keyboard input, around 1 minute or more per character. System monitor doesn't show any significant increase in CPU or memory consumption. -- 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/1020506 Title: Hangs with Insert Comment then Insert Hyperlink Status in “libreoffice” package in Ubuntu: Expired Bug description: Problem occurs with: libreoffice 1:3.5.3-0ubuntu1, Ubuntu 12.04 Does not occur with: LibreOffice 3.5.4.2, Mac OS X 10.8 beta 1. Open a new text document. 2. Choose Insert Comment. 3. Choose Insert Hyperlink. What happens: LibreOffice hangs. What should happen: Either LibreOffice allows hyperlinks in comments, or the menu item is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1020506/+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 1047893] [NEW] Message Read-Error appears when opening files that contain images in the header.
Public bug reported: 1) The release of Ubuntu you are using: Ubuntu 12.04 LTS 2) The version of the package you are using: 1:3.5.4-0ubuntu1.1 (amd64) 3) What you expected to happen: When I open the file with extension RTF display images in the document header. 4) What happened instead: Read-Error message appears instead of the images. - The problem always occurs. - The fedora 17 Package libreoffice-3.5.6.2-2.fc17 solved this bug. - The problem does not happen in version 3.4 of libreoffice. - The problem does not happen in Abiword package. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1047893 Title: Message Read-Error appears when opening files that contain images in the header. Status in “libreoffice” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using: Ubuntu 12.04 LTS 2) The version of the package you are using: 1:3.5.4-0ubuntu1.1 (amd64) 3) What you expected to happen: When I open the file with extension RTF display images in the document header. 4) What happened instead: Read-Error message appears instead of the images. - The problem always occurs. - The fedora 17 Package libreoffice-3.5.6.2-2.fc17 solved this bug. - The problem does not happen in version 3.4 of libreoffice. - The problem does not happen in Abiword package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1047893/+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 1047893] Re: Message Read-Error appears when opening files that contain images in the header.
** Attachment added: Document-Error.rtf https://bugs.launchpad.net/bugs/1047893/+attachment/3301301/+files/Document-Error.rtf -- 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/1047893 Title: Message Read-Error appears when opening files that contain images in the header. Status in “libreoffice” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using: Ubuntu 12.04 LTS 2) The version of the package you are using: 1:3.5.4-0ubuntu1.1 (amd64) 3) What you expected to happen: When I open the file with extension RTF display images in the document header. 4) What happened instead: Read-Error message appears instead of the images. - The problem always occurs. - The fedora 17 Package libreoffice-3.5.6.2-2.fc17 solved this bug. - The problem does not happen in version 3.4 of libreoffice. - The problem does not happen in Abiword package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1047893/+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 793366] Re: Sets $LANG to invalid value de
Robert, I disagree about lightdm not touching the locale setting. If there are other ways to login to the system, fine. That doesn't prevent to read .dmrc which has the correct locale selected by the user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/793366 Title: Sets $LANG to invalid value de Status in “language-selector” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Bug description: Binary package hint: lightdm When I moved from gdm to lightdm, I now get an invalid locale: $ locale locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Kann LC_ALL nicht auf die Standard-Lokale einstellen: Datei oder Verzeichnis nicht gefunden LANG=de LANGUAGE=de:en LC_CTYPE=de LC_NUMERIC=de LC_TIME=de LC_COLLATE=de LC_MONETARY=de LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de LC_NAME=de LC_ADDRESS=de LC_TELEPHONE=de LC_MEASUREMENT=de LC_IDENTIFICATION=de LC_ALL= It seems it takes the de from my ~/.dmrc, which was set up that way by gdm: $ cat .dmrc [Desktop] Language=de Langlist=de:en LCMess=de_DE.UTF-8 Layout=us Session=gnome From that, gdm sets LANG=de_DE.UTF-8 LANGUAGE=de:en while lightdm sets LC_MESSAGES=de_DE.UTF-8 LANG=de LANGUAGE=de:en I'm not entirely sure how gdm derives an appropriate $LANG locale name from just a language name. I'm subscribing Gunnar about this. BTW, I noticed that the current lightdm does not have a language/keyboard chooser at all any more. It used to have one a week or two ago? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/793366/+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 1003301] Re: Empathy aim can't connect
Same problem here. I will try to follow the steps proposed to the first user. -Please provide steps you take to reproduce this issue on your machine Open empathy, add an AIM account, username, password. Then empathy endlessely tries to connect to AIM with no success. Tried to disable/enable TLS/SSL, no help. ** Attachment added: haze (msn, yahoo)-06-07-12_13-50-47.log https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1003301/+attachment/3215236/+files/haze%20%28msn%2C%20yahoo%29-06-07-12_13-50-47.log -- 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/1003301 Title: Empathy aim can't connect Status in “empathy” package in Ubuntu: Invalid Status in “telepathy-haze” package in Ubuntu: Incomplete Bug description: I can't even connect with aim in Empathy I have tried varied options as far as making sure the username and password is right and looking thrue the boards for different advanced options ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: empathy 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 23 04:41:56 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) 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/1003301/+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 798277] Re: $PATH does not contain /usr/games on Ubuntu Oneiric (11.10) - /etc/environment not sourced or environment not preserved
/etc/environment is empty on Debian. I picked up the correct PATH from gdm so at least at one point it was the default used by gdm (2 I guess). -- 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/798277 Title: $PATH does not contain /usr/games on Ubuntu Oneiric (11.10) - /etc/environment not sourced or environment not preserved Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Bug description: Steps to reproduce: 1. Open a terminal. 2. Run echo $PATH Expected result: the path contains the folder /usr/games like on earlier releases of Ubuntu. Actual result: PATH does not include /usr/games path i natty: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games path i oneiric: /usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin/bin For some reason /usr/games is missing in Oneiric, which results in games not being run without specifying the complete path. For instance to run gbrainy, /usr/games/gbrainy is necessary. Also notice that /usr/bin and /usr/sbin have reversed order in Oneiric, though I'm not sure if this is related. I have unfortunately not been able to discover which package is responsible for path, so I have not assigned this bug to a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/798277/+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 798277] Re: $PATH does not contain /usr/games on Ubuntu Oneiric (11.10) - /etc/environment not sourced or environment not preserved
Here's an updated patch ** Patch added: updated patch for 1.1.4 https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/798277/+attachment/2800624/+files/01_set-default-path.patch -- 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/798277 Title: $PATH does not contain /usr/games on Ubuntu Oneiric (11.10) - /etc/environment not sourced or environment not preserved Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Bug description: Steps to reproduce: 1. Open a terminal. 2. Run echo $PATH Expected result: the path contains the folder /usr/games like on earlier releases of Ubuntu. Actual result: PATH does not include /usr/games path i natty: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games path i oneiric: /usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin/bin For some reason /usr/games is missing in Oneiric, which results in games not being run without specifying the complete path. For instance to run gbrainy, /usr/games/gbrainy is necessary. Also notice that /usr/bin and /usr/sbin have reversed order in Oneiric, though I'm not sure if this is related. I have unfortunately not been able to discover which package is responsible for path, so I have not assigned this bug to a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/798277/+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 883865] Re: lightdm doesn't drop privileges when reading ~/.dmrc
Yes, good point, code is removed now, sorry for that. -- 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/883865 Title: lightdm doesn't drop privileges when reading ~/.dmrc Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Status in “lightdm” source package in Precise: Fix Released Bug description: LightDM doesn't drop privileges when reading the ~/.dmrc file. This allows a local user to read configuration files he would normally not have read permissions for, for example, mysql configuration files that contain passwords. How to reproduce: 1- Create a /etc/app.conf file owned by root with 600 permissions, containing the following: [App] password=xyz 2- Log in as a regular user 3- rm ~/.dmrc 4- ln -s /etc/app.conf ~/.dmrc 5- Log out, log back in 6- look at ~/.dmrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/883865/+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 799069] Re: xf86OpenConsole: setpgid failed
Sorry I somehow missed the question. In Debian we still ship the patch, but I'll try without and report back. -- 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/799069 Title: xf86OpenConsole: setpgid failed Status in “lightdm” package in Ubuntu: Fix Released Bug description: Binary package hint: lightdm Oneiric i386 on nvidia (xorg-edgers) got logged into xorg.log: xf86OpenConsole: setpgid failed: Operation not permitted xf86OpenConsole: setsid failed: Operation not permitted i've found similar issue reported but against xdm/slim/wdm: Bug #585853 #19 post seems to point the real problem: - This appears to be caused by the lightdm package not integrating with upstart. - The plymouth process which holds the console open is waiting for a signal that the lightdm job is starting up, so that it can let go of the console; but the lightdm package doesn't have an upstart job, so there's no signal sent, which means the plymouth and lightdm processes are fighting over the console. Note: need to check that the above comments are correct ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.0-1.2-generic-pae 3.0.0-rc3 Uname: Linux 3.0-1-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jun 18 09:26:09 2011 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, no user) LANG=fr_FR.utf8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/799069/+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 883865] Re: lightdm doesn't drop privileges when reading ~/.dmrc
Any news on this? -- 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/883865 Title: lightdm doesn't drop privileges when reading ~/.dmrc Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Status in “lightdm” source package in Precise: Fix Released Bug description: LightDM doesn't drop privileges when reading the ~/.dmrc file. This allows a local user to read configuration files he would normally not have read permissions for, for example, mysql configuration files that contain passwords. How to reproduce: 1- Create a /etc/app.conf file owned by root with 600 permissions, containing the following: [App] password=xyz 2- Log in as a regular user 3- rm ~/.dmrc 4- ln -s /etc/app.conf ~/.dmrc 5- Log out, log back in 6- look at ~/.dmrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/883865/+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 883865] Re: lightdm doesn't drop privileges when reading ~/.dmrc
This patch seems to fix the problem. ** Patch added: 07_CVE-2011-4105.patch https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/883865/+attachment/2609002/+files/07_CVE-2011-4105.patch -- 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/883865 Title: lightdm doesn't drop privileges when reading ~/.dmrc Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Status in “lightdm” source package in Precise: Fix Released Bug description: LightDM doesn't drop privileges when reading the ~/.dmrc file. This allows a local user to read configuration files he would normally not have read permissions for, for example, mysql configuration files that contain passwords. How to reproduce: 1- Create a /etc/app.conf file owned by root with 600 permissions, containing the following: [App] password=xyz 2- Log in as a regular user 3- rm ~/.dmrc 4- ln -s /etc/app.conf ~/.dmrc 5- Log out, log back in 6- look at ~/.dmrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/883865/+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 883865] Re: lightdm doesn't drop privileges when reading ~/.dmrc
Note that the patch uses O_NOFOLLOW flag to open() which is Linux-only. -- 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/883865 Title: lightdm doesn't drop privileges when reading ~/.dmrc Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Oneiric: Fix Released Status in “lightdm” source package in Precise: Fix Released Bug description: LightDM doesn't drop privileges when reading the ~/.dmrc file. This allows a local user to read configuration files he would normally not have read permissions for, for example, mysql configuration files that contain passwords. How to reproduce: 1- Create a /etc/app.conf file owned by root with 600 permissions, containing the following: [App] password=xyz 2- Log in as a regular user 3- rm ~/.dmrc 4- ln -s /etc/app.conf ~/.dmrc 5- Log out, log back in 6- look at ~/.dmrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/883865/+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 836616] Re: 100% cpu usage in lightdm
Still present in 1.0.1 -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+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 866035] Re: long delay when accountsservice is not present
Confirmed, no delay in 1.0.2 without accountsservice. -- 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/866035 Title: long delay when accountsservice is not present Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Bug description: With 1.0.0, when accountsservice is not present, both lightdm startup and login are really slow. Looking at the logs (I don't have them handy, will make a copy/paste later), in both cases there's a timeout trying to reach the dbus service (which is 30s or so, I guess), then the process continue normally. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/866035/+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 836616] Re: 100% cpu usage in lightdm
Seems indeed fixed again in 1.0.2 ** Changed in: lightdm Status: Triaged = Fix Released -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Triaged Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+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 836616] Re: 100% cpu usage in lightdm
Indeed the problem seems back in 1.0.0 -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+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 836616] Re: 100% cpu usage in lightdm
Then it's a different bug, please open a new one. -- 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/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+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 834079] Re: files written as root to user-controlled folders
Robert, any news? -- 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/834079 Title: files written as root to user-controlled folders Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Oneiric: Triaged Status in “lightdm” package in Debian: Confirmed Bug description: Hey, as you were on CC: I guess you're already aware, but reporting so it can be tracked upstream. Short version: http://seclists.org/oss-sec/2011/q3/393 Long version: .dmrc and Xauthority files are written by lightdm running as root while they're in user controlled folders. An user can, via a symlink, overwrite root-owned files. It doesn't look like it can achieve easily privilege-escalation (since the content is quite fixed) but it's still bad. Basically the correct fix seems to have workers process which would setuid() to the user before writing content to those files. There's no CVE affected yet. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/834079/+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 818201] Re: Login doesn't remember the last desktop session
See the thread on lightdm list for remarks about accountservice (and no, hosting it at freedesktop.org doesn't mean it's cross-desktop, right now the only way to tune stuff there is gnome-control-center). I guess you meant “Note” instead of “Not” in the last sentence. Right now this fallback is broken. Afaict it's because (I think) the current implementation in lightdm loads .dmrc (dmrc_load()) in start_user_session(), but it's too late. The current session as already been chosen (display-priv-user_session) and the key file loaded from dmrc_load isn't used at all: /* Load the users login settings (~/.dmrc) */ dmrc_file = dmrc_load (user_get_name (user)); /* Update the .dmrc with changed settings */ g_key_file_set_string (dmrc_file, Desktop, Session, display-priv-user_session); dmrc_save (dmrc_file, user_get_name (user)); g_key_file_free (dmrc_file); // FIXME: Copy old error file log_filename = g_build_filename (user_get_home_directory (user), .xsession-errors, NULL); display-priv-session = create_session (display, authentication, display-priv-user_session, FALSE, log_filename); I'm not completely sure the issues lies there or in the gtk-greeter (without user-list). -- 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/818201 Title: Login doesn't remember the last desktop session Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Fix Released Bug description: I log into Oneiric and choose the Ubuntu 2D desktop. Then I reboot and go to log in again, but lightdm doesn't remember that I chose Ubuntu 2D last time, so by default it will log me in with the default Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/818201/+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 818201] Re: Login doesn't remember the last desktop session
Yes, confirmed, it's user-list related (so it might make sense to move that to another bug). When I set greeter-hide-users=false, selecting the user in the list loads the correct session but not when manually entering the username. If you want me to open another bug instead of continuing with this one, please say so. -- 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/818201 Title: Login doesn't remember the last desktop session Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Fix Released Bug description: I log into Oneiric and choose the Ubuntu 2D desktop. Then I reboot and go to log in again, but lightdm doesn't remember that I chose Ubuntu 2D last time, so by default it will log me in with the default Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/818201/+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 819240] Re: no way to go back to the login entry from the password one (no-userlist specific)
Fixes looks fine, but shouldn't the same thing happen when the authentication count overflows (and when pressing escape, for example :) -- 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/819240 Title: no way to go back to the login entry from the password one (no- userlist specific) Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Oneiric: Fix Committed Bug description: Hey, I noticed a weird behavior of LightDM 0.9.2 with GTK+ greeter and user list disabled. If one mistypes the username (or enter a wrong one) the systems keeps asking about password, but it never returns to the username choice. Even clicking “cancel” doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/819240/+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 818201] Re: Login doesn't remember the last desktop session
HOME permission don't matter as lightdm read/write them as root (and it's bad anyway). It's still not fixed in 0.9.4 without account services, and account services doesn't look like a suitable dependency for a cross-desktop display manager. -- 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/818201 Title: Login doesn't remember the last desktop session Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Fix Released Bug description: I log into Oneiric and choose the Ubuntu 2D desktop. Then I reboot and go to log in again, but lightdm doesn't remember that I chose Ubuntu 2D last time, so by default it will log me in with the default Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/818201/+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 818852] Re: X cursor often not shown
Any indication what would be the GTK+ version fixing the issue? I'm running 3.0.12 and still have no cursor, for indication. -- 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/818852 Title: X cursor often not shown Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” package in Arch Linux: New Status in “lightdm” package in Debian: Confirmed Bug description: It seems that, since 0.9.2, cursor is often not shown in GTK+ greeter. This is a regression from 0.9.0, afaict, but it might be a GTK+ 3.0 issue too. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/818852/+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
