[Desktop-packages] [Bug 2031252] Re: Playing video with audio freezes
** Package changed: alsa-driver (Ubuntu) => wireplumber (Ubuntu)
--
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/2031252
Title:
Playing video with audio freezes
Status in wireplumber package in Ubuntu:
Confirmed
Bug description:
I'm not sure when this started, but any video I play with audio is not
working properly - it severely lags and/or freezes. This happens in
Youtube on both Chrome and Firefox, and in the regular GNOME media
player. Audio by itself works fine, and video with audio muted works
fine. I tried restarting and downgrading the kernel, to no avail.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ari2679 F pipewire
ari2700 F wireplumber
/dev/snd/seq: ari2679 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 13 17:22:56 2023
InstallationDate: Installed on 2022-06-07 (432 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago)
dmi.bios.date: 06/12/2023
dmi.bios.release: 1.61
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET85W (1.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XWCTO1WW
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.34
dmi.modalias:
dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XWCTO1WW
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2031252/+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 2031252] Re: Playing video with audio freezes
This is still happening for me under Ubuntu 23.10. -- 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/2031252 Title: Playing video with audio freezes Status in alsa-driver package in Ubuntu: New Bug description: I'm not sure when this started, but any video I play with audio is not working properly - it severely lags and/or freezes. This happens in Youtube on both Chrome and Firefox, and in the regular GNOME media player. Audio by itself works fine, and video with audio muted works fine. I tried restarting and downgrading the kernel, to no avail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ari2679 F pipewire ari2700 F wireplumber /dev/snd/seq:ari2679 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 13 17:22:56 2023 InstallationDate: Installed on 2022-06-07 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago) dmi.bios.date: 06/12/2023 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET85W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW 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.34 dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+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 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
This was fixed in Ubuntu 23.04, but then broke again with 23.10. The workaround that worked for me in 22.04 was to install https://extensions.gnome.org/extension/4673/alt-tab-move-mouse/, but that's not available for GNOME 45. Supposedly this update to mutter fixes the issue but I haven't tested it: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3258 -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland
I'd been running into this issue on Ubuntu 22.04 with Google Chrome, GNOME Shell under Wayland, and multiple monitors - opening Chrome will frequently crash my whole GNOME session. I could also reliably reproduce it once Chrome is running by moving a Chrome window to another monitor from the GNOME activities overview. After I built & installed libmutter 42.6 (42.5 was previously installed), the problem went away. -- 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/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Update: a workaround to recover the "gdm user chooser" is to avoid the smartcard support from launching, which can be done editing this file /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop comment out the existing "Exec" line, and add a new one pointing to this harmless do-nothing binary, /usr/bin/true The chooser now works. Still wondering how is it that 22.04 was working with no problem with my yubikey always plugged since June till November -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
-- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
I've been using 22.04 (fresh install) since June and today after a routine update this "bug" popped up. This is in a system that has a yubikey 4 permanently plugged in. It's weird that the bug just popped out of nowhere. The last workaround from wastrel worked great for me. Now in addition to this bug, GDM's "face chooser" disappeared, no longer shows up, on boot I get prompted for a username. 22.04 was supposed to be a stable long-term release :/ -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland. Curiously though, when I try systemctl suspend-then-hibernate (my default way of suspending), I get the following in dmesg: NVRM: GPU :02:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README. and suspend does not work (I get a login prompt) Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend-then-hibernate also works fine. Could this be a bug on systemd? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
Unfortunately nvidia.NVreg_EnableS0ixPowerManagement=1 did not work on an old Asus Rog Maximus VIII mobo (Kabylake), nvidia 1650. I also tried this: /etc/modprobe.d/nvidia-power-management.conf options nvidia NVreg_PreserveVideoMemoryAllocations=1 and it didn't work either. Missing textures after suspend. Any other hint? -- 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/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku:
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
The updated package worked 20.04, GTX 1650 Driver 440.100 Monitor: 4K, 32". This a new setup - the screen is large enough that 100% is kind of usable, although the GUI fonts of GTK apps (gnome shell, darktable) was in general too tiny - with the Trevino's patch I could now set the resolution to 125% but then found that the ubuntu GUI became too large. Ideally, I noticed that a of 110% scale or so, like my mac does on the same screen, works best. In case it helps anyone: if you prefer scaling at 100% but want larger fonts in most apps Gnome Tweaks > Fonts > Scaling Factor = 1.1 Firefox > about:config > layout.css.devPixelsPerPx = 1.1 (Preferences > General > Zoom > Default: 100%) Terminal / Tilix > Fonts > Inconsolata 14px -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left
This bug is ubuntu-specific. Fedora's 3.36.3 gnonme-control-center does not have this issue, see this report & closure upstream https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1034#note_844891 In my case Tweaks does NOT exhibit this bug. This weird behavior only happens in gnome-control-center ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1034 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1034 -- 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/1873638 Title: Titlebar buttons incorrectly placed when set to appear on the left Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Unexpected button location on settings. Check image as screenshot attachment. Gnome Tweaks -> move the Titlebar buttons from Right to Left. Buttons should be paced on the extreme left -> for gnome-control- center they are centrally placed. OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question how be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Has anyone found a solution to this problem? I have it too, my computer is an HP Envy x360 Convertible. Any help would be greatly appreciated! -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1715931] Re: Update to exiv2 version 0.27
it doesn't look like it's going to be actioned at all, focal (graphics): EXIF/IPTC/XMP metadata manipulation tool [universe] 0.25-4ubuntu3: amd64 arm64 armhf ppc64el s390x which is awful, unfortunately. It's been 3 years now without an update. Not only for the security implications and all the known vulnerabilities but also for the problems this brings to other photography software that depends on exiv2, e.g. lensfun and all the apps that use lensfun, like darktable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1715931] Re: Update to exiv2 version 0.26
Thanks Jeremy. It's a bit challenging for anyone doing photography work with recent hardware. Key apps like darktable and digicam rely on this library and ubuntu/debian are way behind. Last year's fedora had 0.26. Flatpaks could help, I tried darktable's and it includes an updated exiv2, but it has a huge drawback, OpenCL doesnt work with flatpaks (or snaps) yet, so its useless in my case (my photography workstation is built specifically for photo editing with opencl) I guess there is no choice but to try and build exiv2 manually and hope the system doesnt break :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Unknown Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
This is still breaking tilix functionality and polluting the logs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Fix Released Bug description: gnome-terminal and vte are still at their 3.20 (and 0.44) versions because they now hard-depend on pcre2, but the pcre2 MIR (LP: #163) has stalled because there is already one version of pcre in main and it would be a major task to convert all of main to use pcre2. So I reverted 3 commits for gnome-terminal and 5 for vte to make that MIR less urgent. I am concerned about the long-term maintainability of this approach - the vte patch is over 1600 lines. gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3 Staging PPA for yakkety and zesty for months. I am not aware of any issues from that. This is slightly different since I haven't tested those versions without pcre2 until this weekend. The development cycle for gnome-terminal and vte has been fairly quiet so I believe it's safe to go ahead and update gnome-terminal to 3.23.90 and vte to 0.47.90. https://git.gnome.org/browse/gnome-terminal/log https://git.gnome.org/browse/vte/log The packages are currently available for testing at https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1715931] Re: Update to exiv2 version 0.26
Exiv2 0.25 as used by ubuntu 18.04 and the upcoming 18.10 is really obsolete and this brings all kinds of annoying problems with darktable - inability to recognize lenses and so on. Even the current package in 18.10 is obsolete. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: Triaged Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 788626] Re: Error: Unable to save resume file: File name too long
I'm experiencing this on Ubuntu 16.10. The file system is non-encrypted. Thanks Felix Moreno for the "crappy" solution to get around the problem. It seems to work fine. I didn't see the solution offered in any any other discussions that I read around the web. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/788626 Title: Error: Unable to save resume file: File name too long Status in Transmission: New Status in transmission package in Ubuntu: Confirmed Bug description: Binary package hint: transmission I'm trying to download a torrent (from http://www.jamendo.com/en/album/48348) but I get the message: "Error: Unable to save resume file: File name too long" and I don't see that there is much I can do about that. It would be nice if transmission dealt with the problem itself and made up a shorter name for itself, as I have no idea how to shorten the name myself. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: transmission-gtk 2.05-0ubuntu0.2 Uname: Linux 2.6.37-rc4-fireworks2 x86_64 Architecture: amd64 Date: Fri May 27 00:06:46 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/transmission InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANG=en_AU.utf8 SHELL=/usr/bin/zsh SourcePackage: transmission To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/788626/+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 1631560] Re: Narrow spacing of icons in Files affects file names
@ Sebastian Bacher: I found an existing bug report about this problem at Gnome Bugzilla, and I added my comment to it: https://bugzilla.gnome.org/show_bug.cgi?id=745968 The report and the latest comment are a year and a half old, but the bug is marked as new. I guess it's better not to expect a quick patch. @ dino99: Thanks for the workaround, dino99. It alleviated the problem somewhat. It would help more if I'd decrease the font size further, but the text would get too small then. ** Bug watch added: GNOME Bug Tracker #745968 https://bugzilla.gnome.org/show_bug.cgi?id=745968 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1631560 Title: Narrow spacing of icons in Files affects file names Status in nautilus package in Ubuntu: New Bug description: When I upgraded to Ubuntu 16.10 beta a few days ago, horizontal distance between icons in Files and on the desktop got much smaller. Because of this there's less room horizontally for the file names, and many words got their last letters cut off to the next row. In many file names full rows now alternate with rows of only a couple of cut off letters. Name fields with longer file names also look disproportionately narrow and tall now. I think the spacing should be changed back to what it was, or at least it should be user selectable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-20.22-generic 4.8.0 Uname: Linux 4.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 04:04:55 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time']" InstallationDate: Installed on 2016-03-27 (194 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fi PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1631560/+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 1631560] [NEW] Narrow spacing of icons in Files affects file names
Public bug reported: When I upgraded to Ubuntu 16.10 beta a few days ago, horizontal distance between icons in Files and on the desktop got much smaller. Because of this there's less room horizontally for the file names, and many words got their last letters cut off to the next row. In many file names full rows now alternate with rows of only a couple of cut off letters. Name fields with longer file names also look disproportionately narrow and tall now. I think the spacing should be changed back to what it was, or at least it should be user selectable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-20.22-generic 4.8.0 Uname: Linux 4.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 04:04:55 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time']" InstallationDate: Installed on 2016-03-27 (194 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fi PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1631560 Title: Narrow spacing of icons in Files affects file names Status in nautilus package in Ubuntu: New Bug description: When I upgraded to Ubuntu 16.10 beta a few days ago, horizontal distance between icons in Files and on the desktop got much smaller. Because of this there's less room horizontally for the file names, and many words got their last letters cut off to the next row. In many file names full rows now alternate with rows of only a couple of cut off letters. Name fields with longer file names also look disproportionately narrow and tall now. I think the spacing should be changed back to what it was, or at least it should be user selectable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-20.22-generic 4.8.0 Uname: Linux 4.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 04:04:55 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time']" InstallationDate: Installed on 2016-03-27 (194 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fi PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1631560/+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 1527817] Re: unhelpful error message "Parsing filters is unsupported."
I just had this very same problem,after downloading Mac OS Sierra 6.0GB Archive Manager gave me the same error as described here, I went and installed unrar and problem solved. sudo apt-get install unrar Note: I am running a clean install of Ubuntu 16.10 daily build (Yakety Yak) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1527817 Title: unhelpful error message "Parsing filters is unsupported." Status in file-roller package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. download http://www.speedlink.com/support/bin/sl-8861-b-cd-content-02-26-10.zip 2. try to extract the `.iso` file into `/tmp/` The error message `Parsing filters is unsupported.` doesn't provide any information and doesn't explain if something and what is wrong and thus needs to be replaced by a message which does that. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: file-roller 3.16.4-1ubuntu3 Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 19 02:11:40 2015 InstallationDate: Installed on 2015-12-12 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1527817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout
Please fix openoffice. This was fixed once and came back. Could be done much better. On Tue, Jul 12, 2016 at 12:43 AM, Norbert <1226...@bugs.launchpad.net> wrote: > ** Tags added: yakkety > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1226962 > > Title: > Hotkeys not functional in non-latin keyboard layout > > Status in aptana-studio-installer: > New > Status in Default settings and artwork for Baltix OS: > New > Status in LibreOffice: > Fix Released > Status in ibus: > New > Status in Indicator keyboard: > Fix Released > Status in Inkscape: > New > Status in Intellij Idea: > New > Status in monodevelop: > New > Status in mutter: > Fix Released > Status in okular: > New > Status in OpenOffice: > New > Status in sigram: > New > Status in Unity: > Fix Released > Status in gnome-settings-daemon package in Ubuntu: > Triaged > Status in gnome-terminal package in Ubuntu: > Triaged > Status in kdevelop package in Ubuntu: > Confirmed > Status in openjdk-7 package in Ubuntu: > Incomplete > Status in unity package in Ubuntu: > Fix Released > Status in unity-settings-daemon package in Ubuntu: > In Progress > Status in gnome-settings-daemon source package in Xenial: > Triaged > Status in gnome-terminal source package in Xenial: > Triaged > Status in kdevelop source package in Xenial: > Confirmed > Status in openjdk-7 source package in Xenial: > Incomplete > Status in unity source package in Xenial: > Fix Released > Status in unity-settings-daemon source package in Xenial: > In Progress > Status in gnome-shell package in Fedora: > Unknown > Status in openoffice package in Fedora: > Unknown > > Bug description: > New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any > system or application hotkey witch use char (for example: ctrl+alt+t for > terminal or ctrl+t for new tab in browser) become unfunctional when > selected non-latin keyboard layout. > Hotkeys with F1-12, numbers and other non-character buttons works > perfectly. > > Window manager hotkeys not affected by this bug. All hotkeys in system > parameters->keyboard->hotkeys->windows works perfect with any keyboard > layout. > > Workaround for some system hotkeys and two layouts (english and non- > latin): rebind all hotkeys in your local layout. For example instead > of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with > english layout. If you use english and two different non-latin > layouts this workaround helps only with one of them. > > > Dear Ubuntu users and developers! > Please include the following information to your comment about non-latin > shortcuts problems: > 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, > Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or > clean installed > 2. What keyboard layout do you have > 3. What shortcut for keyboard layout switching do you use > 4. On which session you have problems - that is one from Unity, GNOME > Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback > (Compiz) > 5. With which program and its version and origin (Ubuntu repositories, > PPA, non-deb binary package from some website) you have problems. > > By providing this information you can make bug-fixing much simpler and > may be faster. > > -- > For other layout switching problems introduced in Ubuntu 13.10 you can > see bug 1218322. > -- > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions > -- The information in this email is confidential. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in Intellij Idea: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in openjdk-7 source package in Xenial: Incomplete Status in
[Desktop-packages] [Bug 1582200] Re: citrix does not start
I have the same issue and I have tried to add info about my system,
following the instructions in help.ubuntu.com/community/ReportingBugs to
gather information about my system and the firefox package. This did not
work as it should. I then did:
apport-cli -f -p firefox --save bug.apport
followed by:
ubuntu-bug -c bug.apport -u 1582200
This however, produced the message:
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
Usage: ubuntu-bug [valg] [symptom|pid|pakke|programsti|.apport/.crash-fil]
ubuntu-bug: error: -u/--update-bug option cannot be used together with
options for a new report
And so, I am stuck. If anyone can help, I will gladly complete the
process.
--
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/1582200
Title:
citrix does not start
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Citrix is installed according the manuals but it does not switch to
the other (external) system.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ton1702 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: XFCE
Date: Mon May 16 13:56:47 2016
ExecutablePath: /usr/lib/firefox/firefox
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2016-05-09 (7 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IpRoute:
default via 192.168.2.254 dev wlp12s0 proto static metric 600
169.254.0.0/16 dev wlp12s0 scope link metric 1000
192.168.2.0/24 dev wlp12s0 proto kernel scope link src 192.168.2.14
metric 600
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-40d6e3ec-8d44-4421-891c-4fc972160509
Plugins: Citrix Receiver for Linux - /opt/Citrix/ICAClient/npica.so
(icaclient)
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=nl
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions: icaclient 13.3.0.344519
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs: bp-40d6e3ec-8d44-4421-891c-4fc972160509
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.name: 0W612R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA27:bd12/06/2011:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn0W612R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1582200/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode
@ercoppa Once you've logged in, hit Alt+F2 and restart Unity by entering 'unity'. It fixes the pointer size until your next reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1359211 Title: Mouse cursor tiny when hovering unity elements in high DPI mode Status in Compiz: Fix Committed Status in Unity: Fix Committed Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: On a high DPI screen (220 DPI) the mouse cursor is really tiny when hovering unity elements. There are various keys in dconf to change the cursor's scale factor or size. I've managed to change it in a way that it looks normal when inside application windows, but its still tiny when on unity elements. I think this should be set automatically by the scale factor setting in system settings. (Using unity 7.3.1+14.10.20140811-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1359211/+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 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta
I have experienced this bug as long as I can remember, years anyway. My hardware has changed completely during that time, but the bug stays :-) I haven't let send the automatic bug report often, because I have thought that sending too many of them annoys the developers. Would it be better to send them all, or perhaps one every week or couple so that the developers know that the bug still exists ? I'm using 15.10 now, and currently the crash happens at every boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1351286 Title: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. Status in sane-backends package in Ubuntu: Confirmed Bug description: Upgraded from 14.04 to 14.10 alpha. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: colord 1.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AssertionMessage: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. Date: Fri Aug 1 14:00:57 2014 ExecutablePath: /usr/lib/colord/colord-sane InstallationDate: Installed on 2013-12-26 (217 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/colord/colord-sane ProcEnviron: Signal: 6 SourcePackage: colord StacktraceTop: __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:92 __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 "simple-watch.c", line=454, function=0x7fcd926fa140 "avahi_simple_poll_prepare") at assert.c:101 avahi_simple_poll_prepare () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_simple_poll_iterate () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-kodakaio.so.1 Title: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. UpgradeStatus: Upgraded to utopic on 2014-07-31 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout
Fantastic! How do you get it to work with apacheoffice? thx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice Productivity Suite: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: New Status in monodevelop: New Status in mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Fedora: Unknown Status in openoffice package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters->keyboard->hotkeys->windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1246583] Re: All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10]
*** This bug is a duplicate of bug 1226962 *** https://bugs.launchpad.net/bugs/1226962 For 2 years a critical bug in a new version of Ubuntu goes unfixed. It is GROSSLY inconvenient. This bug should have been fixed automatically and within days. -- 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/1246583 Title: All hotkeys of LibreOffice don't work in non-English keyboard layout [ubuntu 13.10] Status in LibreOffice Productivity Suite: Confirmed Status in libreoffice package in Ubuntu: Incomplete Status in libreoffice package in Fedora: Unknown Bug description: Hotkeys (Ctrl+b, Ctrl+s etc) in LibreOffice are language dependent and work in English language only. While writing in any other language i.e. any Cyrillic, it's impossible to use hotkeys, they just don't do anything. Switching to English input language enable hotkeys once again. This is very frustrating as user needs to switch language to save document, to make it bold, or italic, etc. This was not experienced in Ubuntu 13.04. Steps to reproduce: 1. System Settings > Text Entry. 2. Add another keyboard layout beside English [In my case it is Bengali (Probhat)] 3. Now launch Writer. 4. Switch the keyboard layout from English (US) to Bengali (Probhat) by pressing Ctrl+Space. 5. Press Ctrl+B to change font weight to bold. Error: Font weight does not get changed. Expected: Font weight should change to bold. Note: none other system hotkeys work as expected. I.e. Ctrl+s to save, or Ctrl+b to subscript, or Ctrl+i to italic etc. Workaround: The only way is to - 1. change the keyboard layout to English 2. then press desired hotkey 3. then switch keyboard layout back to Bengali. The issue is critical, as it make writer very slow for keyboard-only typing. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice-core 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 10:11:53 2013 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-05-13 (170 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1246583/+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 1480924] Re: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build
*** This bug is a duplicate of bug 1479913 *** https://bugs.launchpad.net/bugs/1479913 My system also doesn't boot because of the driver problem. The boot is halted somewhere before the login screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1480924 Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: I changed the graphics card of my computer from Nvidia to Ati. I changed the driver from proprietary Nvidia to Nouveau before changing the card. After putting in the Ati card, there were no displaydrivers available in Additional Drivers. Because of this, I used Software Center to install fglrx driver. Something seems to have gone wrong with the installation, because automatic error reporting was triggered. Software Center says fxlrx is installed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 3.19.0-26-generic Date: Mon Aug 3 16:31:04 2015 DistUpgraded: 2015-04-25 14:00:20,098 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2269] InstallationDate: Installed on 2014-07-26 (372 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: System manufacturer System Product Name PackageVersion: 2:15.200-0ubuntu4.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=427b2fa5-4971-41b8-933f-ac3ade6e1951 ro nomodeset quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 Renderer: Software SourcePackage: fglrx-installer Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build UpgradeStatus: Upgraded to vivid on 2015-04-25 (100 days ago) dmi.bios.date: 01/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd01/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Aug 3 15:53:02 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech K270KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1480924/+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 1480924] [NEW] fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build
Public bug reported: I changed the graphics card of my computer from Nvidia to Ati. I changed the driver from proprietary Nvidia to Nouveau before changing the card. After putting in the Ati card, there were no displaydrivers available in Additional Drivers. Because of this, I used Software Center to install fglrx driver. Something seems to have gone wrong with the installation, because automatic error reporting was triggered. Software Center says fxlrx is installed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 3.19.0-26-generic Date: Mon Aug 3 16:31:04 2015 DistUpgraded: 2015-04-25 14:00:20,098 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2269] InstallationDate: Installed on 2014-07-26 (372 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: System manufacturer System Product Name PackageVersion: 2:15.200-0ubuntu4.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=427b2fa5-4971-41b8-933f-ac3ade6e1951 ro nomodeset quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 Renderer: Software SourcePackage: fglrx-installer Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build UpgradeStatus: Upgraded to vivid on 2015-04-25 (100 days ago) dmi.bios.date: 01/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M3A78-T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd01/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Aug 3 15:53:02 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech K270KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputLogitech USB Receiver KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed ubuntu vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1480924 Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build Status in fglrx-installer package in Ubuntu: New Bug description: I changed the graphics card of my computer from Nvidia to Ati. I changed the driver from proprietary Nvidia to Nouveau before changing the card. After putting in the Ati card, there were no displaydrivers available in Additional Drivers. Because of this, I used Software Center to install fglrx driver. Something seems to have gone wrong with the installation, because automatic error reporting was triggered. Software Center says fxlrx is installed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fglrx-core 2:15.200-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion:
[Desktop-packages] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad
** Tags added: ux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1026046 Title: Missing support for thumb resting on bottom of clickpad Status in xf86-input-synaptics: Unknown Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics source package in Precise: Confirmed Status in xserver-xorg-input-synaptics package in Debian: New Bug description: When using the trackpad on the MacBook Pro In Mac OS X it is possible to have the thumb resting (ready to click) on the bottom part of the touchpad while moving the mouse pointer around with your index or middle finger. Likewise it is also possible to use two finger scrolling with the index and middle finger on the upper part on the track pad while resting the thumb on the lower part of the trackpad. This behaviour is not currently supported with the synaptics driver in 12.04. It wil register a two finger scroll when the thumb is resting in the bottom part and index finger moves around in the upper part. I have tried playing aroud with the setting AreaBottomEdge that disables all motion on the bottom part of the touchpad. Unfortunately when this setting is enabled it still detects a finger in the area, so it wil register a two finger scroll like before. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+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 488247] Re: Inkscape is slow starting
I can confirm that the start-up time has been improved significantly with the latest patches. Kudos to everyone who contributed to these fixes! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/488247 Title: Inkscape is slow starting Status in Inkscape: A Vector Drawing Tool: Fix Committed Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Arch Linux: New Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Status in “inkscape” package in Mandriva: Unknown Bug description: Hi, Although Inkscape is a nice program, I recognize that it's becoming slower and slower each time a new version is released. Also I have compiled inkscape from subversion (Revision: 22608) in a Ubuntu 8.10 box. (Intel Core 2 duo 1.8 GHz and 2 GB of RAM) In the build I have disabled the -g option in all the Makefiles, but launching inkscape takes more than 10 seconds!! And in its actions it demostrates that it has become slower. Is any way to improve the performance of Inkscape (for example, using a separate thread to loading the plugins, using a load of components by demand, using OpenGL+Shaders for drawings,...) I have some knowledge of optimization in C/C++ but I know next to nothing how Inkscape has been programmed. Thanks guys for this great program. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/488247/+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 1284635] Re: IBus does not support certain keyboard layouts
Did sudo apt-get purge ibus Removed a total of three ibus packages. Logged out and in, still US keyboard. Did an edit of keyboard layout and closed Settings panel. Re-opened Settings panel, edit keyboard layout back to UK with win keys. Log out log in and have a UK keyboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1284635 Title: IBus does not support certain keyboard layouts Status in “ibus” package in Ubuntu: Triaged Status in “ibus” source package in Trusty: Triaged Bug description: installed trusty beta1 with keyboard layout set correctly during install install completes, login to new install - layout as set during install once logged in - layout set to US and keyboard layout set during install is missing from list ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Feb 25 12:55:56 2014 InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635/+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 931967] Re: Corrupted graphics after the login until the unity launcher appears
This bug persists for me in Ubuntu 13.04 with: unity-greeter: 13.10.3-0ubuntu1 nvidia-319: 319.32-0ubuntu7 I have the Nvidia GTX 295. I also use an SSD like Sapsan, though I don't know if that is relevant. -- 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/931967 Title: Corrupted graphics after the login until the unity launcher appears Status in OEM Priority Project: Fix Released Status in OEM Priority Project oneiric series: Fix Released Status in OEM Priority Project precise series: Fix Released Status in Unity Greeter: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Released Status in “unity-greeter” source package in Quantal: Fix Released Bug description: [Impact] After login, it's very possible the screen will appear corrupted and show artifacts of a previous session. This is a security and privacy concern. [Test Case] Simple as logging in several times. It's highly reproducable (over 50% in my tests). [Regression Potential] Seems low. We had this same patch in 12.04, but it got accidentally dropped for 12.10. [Original Report] With the latest updates im getting corrupted graphics - images after the login until the unity launcher - desktop appears and this is happening in every system restart - relogin. Im attaching a screenshot of what im getting , it looks like its a combination of corrupted images from the windows that was running while i was doing the latest updates , my last session before the problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+10ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 290.10 Wed Nov 16 17:39:29 PST 2011 GCC version: gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-12ubuntu1) .tmp.unity.support.test.0: ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,regex,animation,snap,move,place,mousepoll,vpswitch,wall,resize,gnomecompat,workarounds,compiztoolbox,grid,imgpng,expo,fade,ezoom,scale,session,switcher,unityshell] CompositorRunning: compiz Date: Tue Feb 14 11:40:18 2012 DistUpgraded: Log time: 2011-09-27 15:36:23.910451 DistroCodename: precise DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86 [GeForce 8600M GS] [10de:0425] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Device [104d:9005] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: Sony Corporation VGN-FZ31Z PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-15-generic root=UUID=12e02107-7815-4276-b7ac-7bceee898897 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2012-02-02 (11 days ago) XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 12/21/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2110J7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31Z:pvrC6006UGW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FZ31Z dmi.product.version: C6006UGW dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu33 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
Janis, any chance you have been able to find a workaround/fix in the meantime? The crashes have gotten more frequent for me and it's now at a point where I am considering dropping Synapse for good (which I would hate to do). I tried uploading my stack traces to launchpad but unfortunately apport didn't give me the option to add them to an existing bug report so I had to open a new one: https://bugs.launchpad.net/synapse-project/+bug/1236922 -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
On a second thought, this bug is likely unrelated to the one I am experiencing. I don't have any crashes with applications other than Synapse and your problem seems to be identical to the one described in the following bug reports: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/997212 https://bugzilla.icculus.org/show_bug.cgi?id=5460 Please note that the bug has been fixed in the latest openbox releases. I hope this helps. ** Bug watch added: bugzilla.icculus.org/ #5460 http://bugzilla.icculus.org/show_bug.cgi?id=5460 -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 812476] Re: gvfsd-trash crashed with signal 5 in _g_dbus_oom()
I can confirm this bug on Ubuntu 12.04.3 LTS. Like Jakob said after the crash the trash can't be accessed any more. What works for me though is manually deleting ~/.local/share/Trash/files and ~/.local/share/Trash/info. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/812476 Title: gvfsd-trash crashed with signal 5 in _g_dbus_oom() Status in GVFS: Confirmed Status in “gvfs” package in Ubuntu: Triaged Bug description: I was updating system and the crash reports appeared. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gvfs 1.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic i686 Architecture: i386 Date: Mon Jul 18 21:34:41 2011 ExecutablePath: /usr/lib/gvfs/gvfsd-trash InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=fi_FI.UTF-8 Signal: 5 SourcePackage: gvfs StacktraceTop: _g_dbus_oom () from /usr/lib/gvfs/libgvfscommon.so _g_dbus_append_file_attribute () from /usr/lib/gvfs/libgvfscommon.so _g_dbus_append_file_info () from /usr/lib/gvfs/libgvfscommon.so g_vfs_job_enumerate_add_info () from /usr/lib/gvfs/libgvfsdaemon.so ?? () Title: gvfsd-trash crashed with signal 5 in _g_dbus_oom() UpgradeStatus: Upgraded to oneiric on 2011-07-15 (3 days ago) UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/812476/+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 177929] Re: Should autodetect filename character encoding in zip files
*** This bug is a duplicate of bug 580961 *** https://bugs.launchpad.net/bugs/580961 I can confirm that the workaround described in #46 worked for me. Thank you, temik! (Ubuntu 12.04.3 LTS) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/177929 Title: Should autodetect filename character encoding in zip files Status in File Roller: Confirmed Status in “file-roller” package in Ubuntu: Triaged Status in “xarchiver” package in Ubuntu: Fix Released Bug description: Binary package hint: file-roller Many compressed file such as zip don't specify filename encoding. But file-roller read every file as UTF-8, so it sometimes makes encoding problem. I think may be, you could think that it's not a big problem or it's not a bug or we don't need those feature. If you deal with only English it's not a problem at all. But it's a big problem for East Asian people such as Chinese, Japanese and Korean. Because zip file is still popular. And many people compress zip file in Windows, and share the zip files. Windows don't use UTF-8. Many CJK people want to uncompress these zip files. There are some way to solve this problem (by another software). But all are too complex to Ubuntu newbies. I wish file-roller support encoding select function. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/177929/+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 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
I can confirm this bug on Ubuntu 12.04.3 LTS with openbox 3.5.0-7 installed. For me this bug is most often triggered either by resizing a window or expanding the list view in Synapse launcher. Attached to this comment are 4 Xorg backtraces. ** Attachment added: Xorg.0.log.20130418 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+attachment/3786076/+files/Xorg.0.log.20130418 -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
** Attachment added: Xorg.0.log.20130824 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+attachment/3786078/+files/Xorg.0.log.20130824 -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
** Attachment added: Xorg.0.log.old.20130423 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+attachment/3786077/+files/Xorg.0.log.old.20130423 -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 1163981] Re: Xorg crashes when maximizing/resizing windows in openbox
Additional information: $ apt-cache policy xorg xorg: Installed: 1:7.6+12ubuntu2 Candidate: 1:7.6+12ubuntu2 $ apt-cache policy openbox openbox: Installed: 3.5.0-7~precise Candidate: 3.5.0-7~precise $ lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 $ uname -a Linux UBN 3.5.0-39-generic #60~precise1-Ubuntu SMP Wed Aug 14 15:38:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ xrandr -q Screen 0: minimum 320 x 200, current 3288 x 1080, maximum 3286 x 1920 LVDS connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 164mm 1366x768 60.0*+ 1360x768 60.0 1280x768 60.0 1280x720 60.0 1024x768 60.0 1024x600 60.0 800x60060.0 800x48060.0 640x48060.0 DFP1 connected 1920x1080+1368+0 (normal left inverted right x axis y axis) 478mm x 269mm 1920x1080 60.0*+ 1680x1050 60.0 1400x1050 60.0 1600x900 60.0 1280x1024 60.0 75.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.8 1152x864 60.0 75.0 1280x768 59.8 1280x720 60.0 1024x768 75.0 70.1 60.0 1024x600 75.0 70.1 60.0 800x60072.2 75.0 60.3 56.2 800x48072.2 75.0 60.3 56.2 640x48075.0 72.8 67.0 59.9 CRT1 disconnected (normal left inverted right x axis y axis) $ apt-cache policy fglrx fglrx: Installed: 2:9.012-0ubuntu1 Candidate: 2:9.012-0ubuntu1 Please let me if there is anything else I can provide. -- 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/1163981 Title: Xorg crashes when maximizing/resizing windows in openbox Status in “xorg-server” package in Ubuntu: Confirmed Bug description: After running openbox for a random amount of time (usually a few hours) window resizing and maximizing will cause Xorg to crash with a segmentation fault. Relaunching Xorg no longer causes behaviour until a few hours later. Tested on both standalone openbox and LXDE, precise and quantal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40 Uname: Linux 3.2.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Apr 3 16:48:08 2013 InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-03-29 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1163981/+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 1205055] [NEW] Impossible to change column width of Nautilus in list view
Public bug reported: In Gnome Nautilus 3.8.2 under kernel 3.8.0-26-generic (64-bit), using the mouse to change column width is unavailing. It's as if these widths are hard coded. This seems to be a reversion, since the problem has been reported by various people ever since 2007. Now, 6 years later, the bug remains unswatted. This sort of thing is an embarrassment to Ubuntu. Can something be done? ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1205055 Title: Impossible to change column width of Nautilus in list view Status in “nautilus” package in Ubuntu: New Bug description: In Gnome Nautilus 3.8.2 under kernel 3.8.0-26-generic (64-bit), using the mouse to change column width is unavailing. It's as if these widths are hard coded. This seems to be a reversion, since the problem has been reported by various people ever since 2007. Now, 6 years later, the bug remains unswatted. This sort of thing is an embarrassment to Ubuntu. Can something be done? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1205055/+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 1105918] Re: [g33] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x01000000
*** This bug is a duplicate of bug 1105619 *** https://bugs.launchpad.net/bugs/1105619 this crash is driving me nuts,it comes up every few minutes or so and there is no problems with the system,no crash at all.what is going on here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1105918 Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: random crash ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 05:08:29 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=64aef999-fcb8-4d4c-a27a-4302b8b75a35 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.41-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.1.901-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.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Sat Jan 26 04:38:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1105918/+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 1105918] [NEW] [g33] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x01000000
Public bug reported: random crash ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 05:08:29 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=64aef999-fcb8-4d4c-a27a-4302b8b75a35 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.41-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.1.901-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.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Sat Jan 26 04:38:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze raring ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1105918 Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: random crash ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Sat Jan 26 05:08:29 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron:
Re: [Desktop-packages] [Bug 1105619] Re: [g33] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x7d990000
On 01/26/2013 06:12 AM, Timo Aaltonen wrote: Do you have any idea what might've triggered the error? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Incomplete not at all it happens randomly after i boot with no app opened,so i have no clues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1105619 Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: don't know ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 20:49:02 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=64aef999-fcb8-4d4c-a27a-4302b8b75a35 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-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.1.901-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.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Fri Jan 25 20:39:39 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1105619/+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 1105619] [NEW] [g33] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000002 IPEHR: 0x7d990000
Public bug reported: don't know ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 20:49:02 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=64aef999-fcb8-4d4c-a27a-4302b8b75a35 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.41-0ubuntu1 xserver-xorg-video-intel 2:2.20.19-0ubuntu3 SourcePackage: xserver-xorg-video-intel Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-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.1.901-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.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Fri Jan 25 20:39:39 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze raring ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1105619 Title: [g33] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: don't know ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Chipset: g33 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 20:49:02 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [g33] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0002 IPEHR: 0x7d99 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a6f] InstallationDate: Installed on 2013-01-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) InterpreterPath: /usr/bin/python3.3 MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic
[Desktop-packages] [Bug 1099242] [NEW] package cups-daemon 1.6.1-0ubuntu15 failed to install/upgrade: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubunt
Public bug reported: Don't Know! ProblemType: Package DistroRelease: Ubuntu 13.04 Package: cups-daemon 1.6.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic i686 ApportVersion: 2.8-0ubuntu1 Architecture: i386 Date: Sun Jan 13 19:52:14 2013 DuplicateSignature: Unpacking replacement cups-daemon ... dpkg: error processing /var/cache/apt/archives/cups-daemon_1.6.1-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 ErrorMessage: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 InstallationDate: Installed on 2013-01-13 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130113) Lpstat: device for Deskjet-3840: hp:/usb/Deskjet_3840?serial=TH46G151T2040R MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True Papersize: letter PpdFiles: Deskjet-3840: HP Deskjet 3840, hpcups 3.12.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=61fa9e93-bd7f-4e8f-8012-6eebb7f25195 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=61fa9e93-bd7f-4e8f-8012-6eebb7f25195 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups-daemon 1.6.1-0ubuntu15 failed to install/upgrade: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1099242 Title: package cups-daemon 1.6.1-0ubuntu15 failed to install/upgrade: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 Status in “cups” package in Ubuntu: New Bug description: Don't Know! ProblemType: Package DistroRelease: Ubuntu 13.04 Package: cups-daemon 1.6.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic i686 ApportVersion: 2.8-0ubuntu1 Architecture: i386 Date: Sun Jan 13 19:52:14 2013 DuplicateSignature: Unpacking replacement cups-daemon ... dpkg: error processing /var/cache/apt/archives/cups-daemon_1.6.1-1_i386.deb (--unpack): trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 ErrorMessage: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 InstallationDate: Installed on 2013-01-13 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130113) Lpstat: device for Deskjet-3840: hp:/usb/Deskjet_3840?serial=TH46G151T2040R MachineType: HP-Pavilion NC692AA-ABA m9510f MarkForUpload: True Papersize: letter PpdFiles: Deskjet-3840: HP Deskjet 3840, hpcups 3.12.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=61fa9e93-bd7f-4e8f-8012-6eebb7f25195 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=61fa9e93-bd7f-4e8f-8012-6eebb7f25195 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups-daemon 1.6.1-0ubuntu15 failed to install/upgrade: trying to overwrite '/usr/share/man/man7/backend.7.gz', which is also in package cups 1.6.1-0ubuntu15 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.33 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.33:bd11/07/2008:svnHP-Pavilion:pnNC692AA-ABAm9510f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: NC692AA-ABA m9510f dmi.sys.vendor: HP-Pavilion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1099242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1035799] Re: show offline contacts is missing
The option in settings dialog was available in earlier versions, but I'm really missing the on click entry in the menu. It's really annoying to change settings to show offline contacts, send a message to the contact and after that go to settings again and hide offline contacts. Empathy user experience goes from bad to worse with every gnome-shell version. -- 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/1035799 Title: show offline contacts is missing Status in Chat app, and Telepathy user interface: Invalid Status in Contacts manager for gnome: New Status in “empathy” package in Ubuntu: Triaged Bug description: show offline contacts option in the menu is missing. I need this option! Where are my chat contacts? Search for contacts... does not help, too. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Sun Aug 12 07:21:52 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-08-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1035799/+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 874218] Re: LightDM restarts after first login attempt
I have the exact same problem as the original poster. I am using Ubuntu 12.04 with nvidia proprietary binary drivers. -- 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/874218 Title: LightDM restarts after first login attempt Status in “lightdm” package in Ubuntu: Confirmed Bug description: When I initially boot or reboot my computer and am presented with the LightDM login screen, two strange things happen: 1) There are some weird graphical artifacts near the top of the screen that change as I type in my password. 2) After entering the password (correctly) and hitting enter, the LightDM screen disappears, my displays are turned off, and only moments later I'm presented with the login screen again. Logging in the second time is successful and I'm able to reach the desktop. It seems like these might be part of the same problem. I can't say for sure whether this is consistent behavior because I only upgraded yesterday. I'm using NVIDIA binary drivers with TwinView, Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/874218/+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 874218] Re: LightDM restarts after first login attempt
I should note that it MAY be nvidia related, since it does not happen when I use the open-source nouveau drivers. -- 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/874218 Title: LightDM restarts after first login attempt Status in “lightdm” package in Ubuntu: Confirmed Bug description: When I initially boot or reboot my computer and am presented with the LightDM login screen, two strange things happen: 1) There are some weird graphical artifacts near the top of the screen that change as I type in my password. 2) After entering the password (correctly) and hitting enter, the LightDM screen disappears, my displays are turned off, and only moments later I'm presented with the login screen again. Logging in the second time is successful and I'm able to reach the desktop. It seems like these might be part of the same problem. I can't say for sure whether this is consistent behavior because I only upgraded yesterday. I'm using NVIDIA binary drivers with TwinView, Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/874218/+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 972537] Re: lightdm doesn't allow expired passwords
Password expiration seems to have problem with other PAM modules as well in LightDM; in #1023854 eCryptFS' password updating fails, while it works with passwd. -- 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/972537 Title: lightdm doesn't allow expired passwords Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Precise: Triaged Bug description: In Ubuntu 12.04, when logging in using the unity greeter in lightdm (1.1.9-0ubuntu1) with a user using Kerberos with an expired password, the login screen doesn't give the user the appropriate feedback to set their new password. The text console works correctly. The previous LTS used GDM, which behaved correctly. The normal prompting for this is: Username: cmo-test Password: Password expired. You must change it now. Enter new password: Enter it again: Instead, in lightdm, it is: Username: cmo-test Password: Enter it again: The Password expired message is never shown, and Enter it again is shown in the box instead of Enter new password. If you use lighdm- gtk-greeter, you get the password expired message printed under the box, but still have the same prompting, never asking for the new password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/972537/+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 1023854] [NEW] Changed expired password in lightdm does not change eCrypfs password
Public bug reported: In a system with eCryptfs encrypted home directories and expiring user passwords, when a password expires, lightdm correctly asks for a new password but fails to update eCryptfs's passphrase with the new password. This causes a situation where graphical login fails and the user needs to log in from the text mode console and change the eCryptfs password manually to match the new login password. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 12 14:18:25 2012 EcryptfsInUse: Yes 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: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1023854 Title: Changed expired password in lightdm does not change eCrypfs password Status in “lightdm” package in Ubuntu: New Bug description: In a system with eCryptfs encrypted home directories and expiring user passwords, when a password expires, lightdm correctly asks for a new password but fails to update eCryptfs's passphrase with the new password. This causes a situation where graphical login fails and the user needs to log in from the text mode console and change the eCryptfs password manually to match the new login password. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 12 14:18:25 2012 EcryptfsInUse: Yes 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: 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/1023854/+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 1023854] Re: Changed expired password in lightdm does not change eCrypfs password
-- 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/1023854 Title: Changed expired password in lightdm does not change eCrypfs password Status in “lightdm” package in Ubuntu: New Bug description: In a system with eCryptfs encrypted home directories and expiring user passwords, when a password expires, lightdm correctly asks for a new password but fails to update eCryptfs's passphrase with the new password. This causes a situation where graphical login fails and the user needs to log in from the text mode console and change the eCryptfs password manually to match the new login password. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jul 12 14:18:25 2012 EcryptfsInUse: Yes 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: 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/1023854/+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 637379] Re: [11.04] Brasero unable to write to Blu Ray Recordable disk (BD-R)
in addition, brasero doesn't recognize BD-RE re-writable bluray media -- 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/637379 Title: [11.04] Brasero unable to write to Blu Ray Recordable disk (BD-R) Status in A disc burning application for gnome 2: Confirmed Status in OEM Priority Project: Won't Fix Status in “brasero” package in Ubuntu: Triaged Status in “cdrkit” package in Ubuntu: Invalid Bug description: Binary package hint: brasero This partially relates to bug 637358 Using 10.10 build Sept 13 2010. When trying to burn data to a BD-R disk using Brasero or through Nautilus (using the Brasero plug-in) it will segfault. * Target initial fixes for 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/637379/+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 329968] Re: No suggestions from spell checker if two are installed (OpenMedSpel)
** Also affects: df-libreoffice 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/329968 Title: No suggestions from spell checker if two are installed (OpenMedSpel) Status in LibreOffice Productivity Suite: New Status in The OpenOffice.org Suite: Fix Released Status in “libreoffice” package in Ubuntu: Incomplete Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org I am attempting to install the OpenMedSpel plugin (an extension that adds a medical terms dictionary to OO.o 3.0) from http://extensions.services.openoffice.org/project/OMS . Installing the extension disables the normal English dictionary on OO.o 3.0 on Ubuntu 8.10 64-bit from https://launchpad.net/~openoffice- pkgs/+archive/ppa . Once the package is installed and OO.o is restarted, all normal English words are marked as misspelled. Only medical jargon like reticulocyte is considered spelled correctly. Uninstalling the plugin fixes the problem. I've contacted the plugin author, and he told me that this is not the case in WinXP. I am not able to check in Jaunty since my VirtualBox network connection is not working (https://bugs.launchpad.net/ubuntu/+bug/326003) Is there any additional info you might need or any suggestions you can recommend? To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/329968/+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 915786] [NEW] package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 915688 *** https://bugs.launchpad.net/bugs/915688 Public bug reported: have no idea ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0 Uname: Linux 3.2.0-8-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Thu Jan 12 21:04:03 2012 DuplicateSignature: Unpacking replacement libreoffice-math ... Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120102) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- 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/915786 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: have no idea ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0 Uname: Linux 3.2.0-8-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Thu Jan 12 21:04:03 2012 DuplicateSignature: Unpacking replacement libreoffice-math ... Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120102) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915786/+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 915786] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 915688 *** https://bugs.launchpad.net/bugs/915688 -- 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/915786 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: have no idea ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0 Uname: Linux 3.2.0-8-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Thu Jan 12 21:04:03 2012 DuplicateSignature: Unpacking replacement libreoffice-math ... Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120102) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915786/+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 831341] Re: can't open empathy chat windows
Going offline (with all accounts) usual fix the problem. -- 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/831341 Title: can't open empathy chat windows Status in “empathy” package in Ubuntu: Fix Released Bug description: as of relatively recently in oneiric, empathy chat dialogs no longer open. double clicking a contact in the contact list opens a gnome-shell message tray bubble, but clicking on that bubble doesn't open an empathy chat dialog. there appears to be no way to enter a group chat, and clicking on room - group chat name does nothing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 08:13:26 2011 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+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 861064] Re: mbox account needs better initial settings
It seems that I might be suffering from the same problem. After upgrading to Ubuntu 11.10, the only account visible in Evolution is me@localhost, when it should be me@gmail.com. The old messages were imported to this localhost account during the upgrade, but I'm not able to receive any messages any more. Everything seems normal in the Evolution settings. I don't know if it's related, but Evolution has two items in default applications selection. Selecting one or the other doesn't seem to affect anything though. I wouldn't mind getting some help to solve this problem, as currently I have to send and read email through Gmail web interface, which I find very unpleasant to use. So, how do I get my me@gmail account back, visible and working again? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/861064 Title: mbox account needs better initial settings Status in “evolution” package in Ubuntu: New Bug description: Upon upgrade to Oneiric, my local folders were migrated to a new 'mbox' account. Unlike local folders, the mbox account has send and receive settings. Those settings, after migration, are not however set to anything useful. My username is 'jim', so the Email was set to 'jim@localhost'. No one on another system can reach me using that e-mail. In my case, it's not simply that people might receive e-mails with a seemingly nonsensical from address; my service provider will actually block messages because the from address is not registered with it (an anti-spam measure). I would recommend instead that this account clone the settings from whatever account was set up as 'Default', or that it simply defer to the Default account when mail is sent while accessing that folder as Evolution did with the local folders account. This bug is exacerbated by bug#861060, which prevents me from actually changing the default settings. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.1.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CheckboxSubmission: fc2d0c1a9f7a9107c5104c45d6ee1b22 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Tue Sep 27 21:29:59 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-09-05 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/861064/+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 841315] [NEW] on thinkpad-acpi devices, brightness setting ommits most steps
Public bug reported: Brightness changes in very rough steps on some Machines, but only when there is the gpm-OSD appearing showing the brightness setting. So the bug appears not when the session showed is locked, but in an active session or on the login screen the bug appears. On my machine (thinkpad X60) brightness changes with two steps between min and max - these steps are different depending on wether you go up or down hough. So you can hit 6 settings. I think the firmware is capable I think 8, surely indepent on wether set higher or lower. This is found on an X60 Tablet, an Lenovo Netbook (sorry, not sure which device exactly) and an X201 Tablet. This leads me to believe this is an issue with the thinkpad-acpi kernel module, which has an proprietary interface for the screen brightness. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 Date: Sun Sep 4 21:28:58 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: LENOVO 6363C7G ProcEnviron: LANGUAGE=de_CH:en LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/hostname/ubuntu ro splash quiet cryptopts=source=UUID=fc6bed20-d029-418d-82ca-cf4b932bb6c5,target=hostname-crypt,lvm=hostname-ubuntu loop.max_part=63 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7JET27WW (1.12 ) dmi.board.name: 6363C7G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7JET27WW(1.12):bd01/23/2008:svnLENOVO:pn6363C7G:pvrThinkPadX60Tablet:rvnLENOVO:rn6363C7G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6363C7G dmi.product.version: ThinkPad X60 Tablet dmi.sys.vendor: LENOVO ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty running-unity unity-2d -- 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/841315 Title: on thinkpad-acpi devices, brightness setting ommits most steps Status in “gnome-power-manager” package in Ubuntu: New Bug description: Brightness changes in very rough steps on some Machines, but only when there is the gpm-OSD appearing showing the brightness setting. So the bug appears not when the session showed is locked, but in an active session or on the login screen the bug appears. On my machine (thinkpad X60) brightness changes with two steps between min and max - these steps are different depending on wether you go up or down hough. So you can hit 6 settings. I think the firmware is capable I think 8, surely indepent on wether set higher or lower. This is found on an X60 Tablet, an Lenovo Netbook (sorry, not sure which device exactly) and an X201 Tablet. This leads me to believe this is an issue with the thinkpad-acpi kernel module, which has an proprietary interface for the screen brightness. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 Date: Sun Sep 4 21:28:58 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: LENOVO 6363C7G ProcEnviron: LANGUAGE=de_CH:en LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/hostname/ubuntu ro splash quiet cryptopts=source=UUID=fc6bed20-d029-418d-82ca-cf4b932bb6c5,target=hostname-crypt,lvm=hostname-ubuntu loop.max_part=63 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7JET27WW (1.12 ) dmi.board.name: 6363C7G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7JET27WW(1.12):bd01/23/2008:svnLENOVO:pn6363C7G:pvrThinkPadX60Tablet:rvnLENOVO:rn6363C7G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6363C7G dmi.product.version: ThinkPad X60 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/841315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 841315] Re: on thinkpad-acpi devices, brightness setting ommits most steps
-- 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/841315 Title: on thinkpad-acpi devices, brightness setting ommits most steps Status in “gnome-power-manager” package in Ubuntu: New Bug description: Brightness changes in very rough steps on some Machines, but only when there is the gpm-OSD appearing showing the brightness setting. So the bug appears not when the session showed is locked, but in an active session or on the login screen the bug appears. On my machine (thinkpad X60) brightness changes with two steps between min and max - these steps are different depending on wether you go up or down hough. So you can hit 6 settings. I think the firmware is capable I think 8, surely indepent on wether set higher or lower. This is found on an X60 Tablet, an Lenovo Netbook (sorry, not sure which device exactly) and an X201 Tablet. This leads me to believe this is an issue with the thinkpad-acpi kernel module, which has an proprietary interface for the screen brightness. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic x86_64 Architecture: amd64 Date: Sun Sep 4 21:28:58 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: LENOVO 6363C7G ProcEnviron: LANGUAGE=de_CH:en LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/hostname/ubuntu ro splash quiet cryptopts=source=UUID=fc6bed20-d029-418d-82ca-cf4b932bb6c5,target=hostname-crypt,lvm=hostname-ubuntu loop.max_part=63 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7JET27WW (1.12 ) dmi.board.name: 6363C7G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7JET27WW(1.12):bd01/23/2008:svnLENOVO:pn6363C7G:pvrThinkPadX60Tablet:rvnLENOVO:rn6363C7G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6363C7G dmi.product.version: ThinkPad X60 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/841315/+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
