[Desktop-packages] [Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
Is there a known workaround for this bug? I've found that holding an additional finger on the screen before pressing an element will sometimes work. -- 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/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu DisplayManager: sddm DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2021-06-21 (1035 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xorg-server PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 46.0-1ubuntu7 Tags: noble Uname: Linux 6.8.0-28-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 Package: xorg-server PackageArchitecture: arm64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 Tags: noble third-party-packages Uname: Linux 4.9.140-l4t aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip gdm lpadmin plugdev sambashare sudo users video weston-launch _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+subscriptions -- Mailing list: https://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 2020259] [NEW] [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: No sound whatsoever on freshly imaged Zenbook UM3504DA Sound control panel only occasionally shows activity, cannot consistently get it to provide sound. Attempted many fixes from other users experiencing same issue, many say this issue occurs after booting to windows or that sound only works at either 100% or 0% but this is not the case for myself. Since this is a recently released device, there are no matching fixes provided by the community that work for me. Hopefully this is at all helpfull ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.3-060303-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 21 20:20:32 2023 InstallationDate: Installed on 2023-05-21 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3504DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3504DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.302:bd03/10/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook 15 UM3504DA_UM3504DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-05-21T20:12:51.201988 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2020259 Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound whatsoever on freshly imaged Zenbook UM3504DA Sound control panel only occasionally shows activity, cannot consistently get it to provide sound. Attempted many fixes from other users experiencing same issue, many say this issue occurs after booting to windows or that sound only works at either 100% or 0% but this is not the case for myself. Since this is a recently released device, there are no matching fixes provided by the community that work for me. Hopefully this is at all helpfull ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.3-060303-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 21 20:20:32 2023 InstallationDate: Installed on 2023-05-21 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3504DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3504DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.302:bd03/10/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook 15 UM3504DA_UM3504DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-05-21T20:12:51.201988 To manage notifications about this
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
To summarize for other people with the problem: `sudo aa-complain /usr/bin/evince` fixes this for me. (I had to install the apparmor-utils package to run that) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://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 1966921] Re: Display freezes after entering password from login screen
Thanks Daniel. You were right about the extensions, thank you for the suggestion. It appears to be caused by the "Nothing to Say" gnome extension. I uninstalled this, and can now use the wayland session again. It looks like it's probably the same issue as reported here (by a user running 20.04): https://github.com/wbolster/nothing-to-say/issues/49 Thanks for your time, sorry if I wasted it by suggesting the bug was was mutter-related. ** Bug watch added: github.com/wbolster/nothing-to-say/issues #49 https://github.com/wbolster/nothing-to-say/issues/49 -- 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/1966921 Title: Display freezes after entering password from login screen Status in mutter package in Ubuntu: Incomplete Bug description: The display freezes with the same background colour as the login screen. The mouse pointer no longer moves. I was unable to change to another VT when the display freezes. Only a press of the power button seemed to make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+subscriptions -- Mailing list: https://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 1966921] Re: Display freezes after entering password from login screen
Thanks Daniel, I have attached the requested output. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574560/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966921 Title: Display freezes after entering password from login screen Status in mutter package in Ubuntu: Incomplete Bug description: The display freezes with the same background colour as the login screen. The mouse pointer no longer moves. I was unable to change to another VT when the display freezes. Only a press of the power button seemed to make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+subscriptions -- Mailing list: https://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 1966921] Re: Display freezes after entering password from login screen
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+attachment/5574561/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966921 Title: Display freezes after entering password from login screen Status in mutter package in Ubuntu: Incomplete Bug description: The display freezes with the same background colour as the login screen. The mouse pointer no longer moves. I was unable to change to another VT when the display freezes. Only a press of the power button seemed to make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+subscriptions -- Mailing list: https://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 1966921] [NEW] Display freezes after entering password from login screen
Public bug reported: The display freezes with the same background colour as the login screen. The mouse pointer no longer moves. I was unable to change to another VT when the display freezes. Only a press of the power button seemed to make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - I was unable to change to another VT when the display freezes. Only a - press of the power button seemed to make the laptop respond by - triggering a shutdown. + The display freezes with the same background colour as the login screen. + The mouse pointer no longer moves. I was unable to change to another VT + when the display freezes. Only a press of the power button seemed to + make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) -- 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/1966921 Title: Display freezes after entering password from login screen Status in mutter package in Ubuntu: New Bug description: The display freezes with the same background colour as the login screen. The mouse pointer no longer moves. I was unable to change to another VT when the display freezes. Only a press of the power button seemed to make the laptop respond by triggering a shutdown. I've had to switch to "GNOME on Xorg" to be able to login/see the desktop. Wayland was working fine until some time around the last week. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 29 18:34:41 2022 InstallationDate: Installed on 2021-09-13 (196 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-02-19 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966921/+subscriptions -- Mailing list: https://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 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1 and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved this issue for me. Note: The updated libmutter from focal-proposed also had to be explicitly installed by me, as it was not automatically pulled in when updating mutter. Steps: 1) Enabled focal-proposed 2) apt update 3) apt install mutter libmutter 4) Disabled focal-proposed 5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml 6) Rebooted 7) After login, I successfully applied my desired monitor configuration (changing the primary monitor and setting other monitor to portrait orientation). Side notes: 1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for the correct primary monitor and orientation to be set on the login screen. 2) After applying the display configuration, the icons in the top-right of the gnome panel appeared blured (network/bluetooth). This was resolved by applying 150% fractional scaling and then applying 100% scaling again in the gnome display settings. I haven't had time to reproduce this to know if it's a one-off or ongoing bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bi
[Desktop-packages] [Bug 1874567] Re: Secondary (rotated) monitor configuration is not applied correctly in gnome settings
** Attachment added: "Screenshot from 2020-04-24 08-37-43.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874567/+attachment/5358812/+files/Screenshot%20from%202020-04-24%2008-37-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: Secondary (rotated) monitor configuration is not applied correctly in gnome settings Status in xorg package in Ubuntu: New Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874567/+subscriptions -- Mailing list: https://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 1874567] [NEW] Secondary (rotated) monitor configuration is not applied correctly in gnome settings
Public bug reported: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01: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: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal nvidia ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: Secondary (rotated) monitor configuration is not applied correctly in gnome settings Status in xorg package in Ubuntu: New Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.
[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "lspci -k" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310908/+files/lspcik.txt -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+subscriptions -- Mailing list: https://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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+attachment/5310910/+files/Xorg.0.log -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in xorg-server package in Ubuntu: Incomplete Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853094/+subscriptions -- Mailing list: https://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 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions
Thanks for the feedback, but I don't believe I am using fractional scaling. My scaling is set to 100%, but I have changed the font scaling to 1.25. If I set font scaling to 1.0, then I see the same tearing. -- 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/1846398 Title: Fractional scaling has significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions -- Mailing list: https://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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "tearing-1.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4 -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "tearing-2.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4 -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "modinfo-i915.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306547/+files/modinfo-i915.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
*-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:140 memory:eb00-ebff memory:a000-afff ioport:f000(size=64) memory:c-d The two monitors are 2560x1440, with no scaling. But I do use a 1.25 font scaling factor in gnome-tweaks. I am using the ubuntu-x-swat ppa, which was an attempt to resolve some previous graphics issues, but I can try removing this again if you'd like me to test? libdrm-amdgpu1: ubuntu-x-swat/updates/ubuntu libdrm-common: ubuntu-x-swat/updates/ubuntu libdrm-dev: ubuntu-x-swat/updates/ubuntu libdrm-intel1: ubuntu-x-swat/updates/ubuntu libdrm-nouveau2: ubuntu-x-swat/updates/ubuntu libdrm-radeon1: ubuntu-x-swat/updates/ubuntu libdrm2: ubuntu-x-swat/updates/ubuntu libegl-mesa0: ubuntu-x-swat/updates/ubuntu libegl1-mesa: ubuntu-x-swat/updates/ubuntu libgbm1: ubuntu-x-swat/updates/ubuntu libgl1-mesa-dev: ubuntu-x-swat/updates/ubuntu libgl1-mesa-dri: ubuntu-x-swat/updates/ubuntu libgl1-mesa-glx: ubuntu-x-swat/updates/ubuntu libglapi-mesa: ubuntu-x-swat/updates/ubuntu libglx-mesa0: ubuntu-x-swat/updates/ubuntu libllvm9: ubuntu-x-swat/updates/ubuntu libxatracker2: ubuntu-x-swat/updates/ubuntu mesa-common-dev: ubuntu-x-swat/updates/ubuntu mesa-va-drivers: ubuntu-x-swat/updates/ubuntu mesa-vdpau-drivers: ubuntu-x-swat/updates/ubuntu ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306546/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://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 1853094] [NEW] Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
Public bug reported: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Summary changed: - Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thubderbolt dock + Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock ** Description changed: - I have the WD19TB Thubderbolt dock connected to a Dell Latitude 7480 + I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day (#1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day-to-day - (#1849405). + (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 C
[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
This happens to me about three times a week on Ubuntu 18.04.3 LTS with kernel 4.15.0-70-generic. I have not been able to find a way to consistently reproduce it. It is a random complete system freeze. The mouse does not respond, caps lock and numlock do not change light on keyboard, ctrl alt f2/f3/etc does not work, and even Alt + SysRq REISUB does not respond. Only a hard reset works by pressing the power button will reboot the system. The first sign of it happening is the mouse begins to stutter for a couple seconds before the whole screen completely freezes. Here is some system info: CPU: AMD Ryzen Threadripper 1950X 16-Core Processor Graphics: Nvidia Quadro P4000 Motherboard: Asus ROG STRIX X399-E GAMING Ubuntu version: 18.04.3 Memory: 62.8 GiB Gnome: 3.28.2 Disk capacity: 903.7 GB -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://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 1849405] Re: Repeated keypresses from bluetooth keyboard
I've now been using an Xorg session rather than Wayland and haven't seen the repeated keys issue. I do get some very nasty screen tearing when scrolling (e.g. websites) on Xorg however, so ideally I'd like to continue using Wayland. Does that mean that this is likely a mutter bug, rather than bluez? -- 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/1849405 Title: Repeated keypresses from bluetooth keyboard Status in bluez package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g. around every 10-15mins) end up with repeated keypresses being made (e.g. apppt get update). This seems to happen when the machine is under slight stress, or when a new notification pops up in gnome, so it could be related to wayland possibly - but even if wayland or other processes are causing stress, I should imagine the bluetooth hid driver should not cause repeated key presses. Please let me know if you require further information about my environment, it's difficult to know where to begin with determining which process is the root cause of this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 23 09:38:20 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude 7480 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:63:3F:E9:51:8C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0 TX bytes:605292 acl:98 sco:0 commands:2484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849405/+subscriptions -- Mailing list: https://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 1809826] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1809826/+attachment/5227744/+files/GsettingsChanges.txt -- 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/1809826 Title: Gnome Activites view on multiple desktops wrong applications Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-19 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+subscriptions -- Mailing list: https://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 1809826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1809826/+attachment/5227745/+files/ProcCpuinfoMinimal.txt -- 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/1809826 Title: Gnome Activites view on multiple desktops wrong applications Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-19 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+subscriptions -- Mailing list: https://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 1809826] Re: Gnome Activites view on multiple desktops wrong applications
The bug 1743736 seems to be the same issue from what I can tell from the description. I ran the apport-collect. Please let me know if there's anything else I can provide to help with this. Much thanks! -- 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/1809826 Title: Gnome Activites view on multiple desktops wrong applications Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-19 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+subscriptions -- Mailing list: https://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 1809826] Re: Gnome Activites view on multiple desktops wrong applications
apport information ** Tags added: apport-collected ** Description changed: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-12-19 (20 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 + Tags: cosmic + Uname: Linux 4.18.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1809826/+attachment/5227743/+files/Dependencies.txt -- 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/1809826 Title: Gnome Activites view on multiple desktops wrong applications Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-19 (20 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+subscriptions -- Mailing list: https://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 1809826] [NEW] Gnome Activites view on multiple desktops wrong applications
Public bug reported: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description:Ubuntu 18.10 Release:18.10 Gnome 3.30.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1809826 Title: Gnome Activites view on multiple desktops wrong applications Status in gnome-shell package in Ubuntu: New Bug description: I have 2 monitors and have configured through tweak tool on the "Workspaces" tab "Dynamic Workspaces" and "Workspaces span displays". Everything is working as advertised except that when I hit the Meta/Windows key or use hot corner to open the Gnome Activities view on the second monitor only it shows the application windows for all 2nd monitor workspaces together. On the primary monitor it only shows the applications that exist for that monitor on that workspace. I believe it should show on the 2nd display only the applications that exist for that display in the current work space. This is how it functioned on the previous version of Ubuntu I was using prior to install of Ubuntu 18.10. Thanks! Description: Ubuntu 18.10 Release: 18.10 Gnome 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809826/+subscriptions -- Mailing list: https://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 626321]
This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the spam. -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate Status in Wine: Won't Fix Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Applications like games change desktop resolution (graphics mode) for their needs. Unfortunately when such applications crash then X.org server doesn't revert the resolution back to its initial mode. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+subscriptions -- Mailing list: https://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 626321]
Closing. -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate Status in Wine: Won't Fix Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Applications like games change desktop resolution (graphics mode) for their needs. Unfortunately when such applications crash then X.org server doesn't revert the resolution back to its initial mode. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+subscriptions -- Mailing list: https://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 702452]
(In reply to Eike Hein from comment #19) > I've tested this now and I can confirm it works nicely. Thanks, this > improves the experience for our users quite a bit. Reported fixed (please reopen if it's not). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Fix Released Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+subscriptions -- Mailing list: https://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 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t
Thank you - I can confirm that installing nvidia-340 from xenial- proposed resolved this for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1741671 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"] Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: not compiling after installation of linux-image-4.13.0-21-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.102-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.13.0-21-generic Date: Sat Jan 6 18:36:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!" GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2016-04-26 (619 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: 340.102-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039E202413102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 6 18:17:29 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions -- Mailing list: https://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 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t
Possible duplicate of #1724872. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1741671 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"] Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: not compiling after installation of linux-image-4.13.0-21-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.102-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.13.0-21-generic Date: Sat Jan 6 18:36:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!" GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2016-04-26 (619 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: 340.102-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039E202413102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 6 18:17:29 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions -- Mailing list: https://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 1735798] Re: Unable to access any subdomain provided by VPN provider until reboot.
I have figured this out as well. It would be nice to be able to use gnome-network-manager though. On Jan 9, 2018 18:25, "mash" <1735...@bugs.launchpad.net> wrote: > The problem occurs when I use network-manager to initiate the VPN. > > > The problem does not occur when I run openconnect from the command line: > > sudo openconnect --cafile /etc/ssl/certs/ca-certificates.crt --juniper > https://vpn.myschool.edu > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1735798 > > Title: > Unable to access any subdomain provided by VPN provider until reboot. > > Status in network-manager package in Ubuntu: > Confirmed > Status in openconnect package in Ubuntu: > Confirmed > > Bug description: > After disconnecting from VPN, ubuntu is unable to reconnect to the VPN > and any domain hosted by the server. For reference, this is my > school's VPN, and I am unable to get on mygateway or even the school's > main website after I disconnect from the VPN or the computer sleeps > after the VPN has been started. It uses EAP authentication. > > Here is the log after connecting once, turning off, and restarting: > LOG: > POST https://vpn.myschool.edu/ > getaddrinfo failed for host 'vpn.myschool.edu': Name or service not > known > Failed to open HTTPS connection to vpn.myschool.edu > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: network-manager 1.8.4-1ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 > Uname: Linux 4.13.0-17-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Dec 1 11:39:56 2017 > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > InstallationDate: Installed on 2016-12-02 (364 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > IpRoute: >default via 192.168.1.1 dev wlp5s0 proto static metric 600 >169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown >192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 > metric 600 >192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > linkdown > NetworkManager.state: >[main] >NetworkingEnabled=true >WirelessEnabled=true >WWANEnabled=true > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: network-manager > UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago) > nmcli-nm: >RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING > WIFI-HW WIFI WWAN-HW WWAN >running 1.8.4connected started full enabled > enabled enabled enabled enabled > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1735798/+ > subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1735798 Title: Unable to access any subdomain provided by VPN provider until reboot. Status in network-manager package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Confirmed Bug description: After disconnecting from VPN, ubuntu is unable to reconnect to the VPN and any domain hosted by the server. For reference, this is my school's VPN, and I am unable to get on mygateway or even the school's main website after I disconnect from the VPN or the computer sleeps after the VPN has been started. It uses EAP authentication. Here is the log after connecting once, turning off, and restarting: LOG: POST https://vpn.myschool.edu/ getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known Failed to open HTTPS connection to vpn.myschool.edu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 11:39:56 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-02 (364 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bas
[Desktop-packages] [Bug 1735798] [NEW] Unable to access any subdomain provided by VPN provider until reboot.
Public bug reported: After disconnecting from VPN, ubuntu is unable to reconnect to the VPN and any domain hosted by the server. For reference, this is my school's VPN, and I am unable to get on mygateway or even the school's main website after I disconnect from the VPN or the computer sleeps after the VPN has been started. It uses EAP authentication. Here is the log after connecting once, turning off, and restarting: LOG: POST https://vpn.myschool.edu/ getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known Failed to open HTTPS connection to vpn.myschool.edu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 11:39:56 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-02 (364 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Also affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Description changed: After disconnecting from VPN, ubuntu is unable to reconnect to the VPN and any domain hosted by the server. For reference, this is my school's VPN, and I am unable to get on mygateway or even the school's main website after I disconnect from the VPN or the computer sleeps after the - VPN has been started. + VPN has been started. It uses EAP authentication. + + Here is the log after connecting once, turning off, and restarting: + LOG: + POST https://vpn.myschool.edu/ + getaddrinfo failed for host 'vpn.myschool.edu': Name or service not known + Failed to open HTTPS connection to vpn.myschool.edu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 11:39:56 2017 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2016-12-02 (364 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: - default via 192.168.1.1 dev wlp5s0 proto static metric 600 - 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown - 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 600 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown + default via 192.168.1.1 dev wlp5s0 proto static metric 600 + 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown + 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.144 metric 600 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-24 (38 days ago) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.8.4connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.8.4connected started full enabled enabled enabled enabled enabled -- You received this bug notification beca
[Desktop-packages] [Bug 619403] Re: [KDE] no option for mouse wheel acceleration
** Changed in: xorg-server (Ubuntu) Status: Opinion => Confirmed -- 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/619403 Title: [KDE] no option for mouse wheel acceleration Status in X.Org X server: Won't Fix Status in xorg-server package in Ubuntu: Confirmed Bug description: I am very used to mouse wheel acceleration but I haven't found any setting for it in the KDE settings. Also, the maximum possible value you can fill there (strangely it counts per lines) still is very slow. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kdebase (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.39-generic-pae 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 17 20:50:50 2010 InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-kde To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions -- Mailing list: https://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 1637683] Re: ubuntu 16.10 internal speakers don't work, but headphones do
PSA: This may be related to a broken headphone jack that is supposed to detect whether headphones are plugged in and change output accordingly. Work around in ubuntu right now is to run alsamixer from terminal, select correct soundcard, then disable auto-mute, then unmute and turn up speakers. -- 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/1637683 Title: ubuntu 16.10 internal speakers don't work, but headphones do Status in alsa-driver package in Ubuntu: New Bug description: Under sound settings only headphone output is listed as an option, no internal speakers are listed. Headphone playback does work. In alsamixer, speaker output was at 0 and muted, but unmuting and increasing volume does not produce playback in speakers. ASUS X550LB laptop ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 28 20:42:56 2016 InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637683/+subscriptions -- Mailing list: https://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 1637683] [NEW] ubuntu 10.16 internal speakers don't work, but headphones do
Public bug reported: Under sound settings only headphone output is listed as an option, no internal speakers are listed. Headphone playback does work. In alsamixer, speaker output was at 0 and muted, but unmuting and increasing volume does not produce playback in speakers. ASUS X550LB laptop ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 28 20:42:56 2016 InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1637683 Title: ubuntu 10.16 internal speakers don't work, but headphones do Status in alsa-driver package in Ubuntu: New Bug description: Under sound settings only headphone output is listed as an option, no internal speakers are listed. Headphone playback does work. In alsamixer, speaker output was at 0 and muted, but unmuting and increasing volume does not produce playback in speakers. ASUS X550LB laptop ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 28 20:42:56 2016 InstallationDate: Installed on 2016-10-29 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: austinclem1 1647 F pulseaudio /dev/snd/controlC0: austinclem1 1647 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.403:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1637683/+subscriptions -- Mailing list: https://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 883272] Re: Mouse navigation not working in fullscreen mode
This is still an issue with Trusty (14.04.3). I have found that the controls do not show up when using the trackpad, but do work if you swipe on a touch screen. Once the controls are up, moving the mouse with the trackpad keeps them visible, but after they disappear from inactivity, moving the trackpad will not bring the controls back up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/883272 Title: Mouse navigation not working in fullscreen mode Status in Totem: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: After upgrading to oneric navigation in full screen mode is not working anymore. Moving the mouse used to bring up a navigation area at the bottom of the window containing the progress bar and basic player controls such as pause and play. Now moving the mouse doesn't trigger any action at all and the is no way to bring up the navigation area. Right clicking does bring up the context menu but left clicking doesn't even stop the movie. Also the mouse pointer is not visible at all in full screen mode. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: totem 3.0.1-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Fri Oct 28 23:00:59 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to oneiric on 2011-10-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/883272/+subscriptions -- Mailing list: https://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 371897]
Maarten's initial patches (+ fixes by Andrew et al) are now in Wine: https://source.winehq.org/git/wine.git/commitdiff/3fe0c08992db43155677f02ec0cca423b9278f89 https://source.winehq.org/git/wine.git/commitdiff/84d1de17ebe381772880d3785af25a869205ea15 https://source.winehq.org/git/wine.git/commitdiff/6f632affa75ae27ce6a40f0c2f0cc25254400395 https://source.winehq.org/git/wine.git/commitdiff/d7eb9090b73b35b16c4bb281f13fea1ac615be70 https://source.winehq.org/git/wine.git/commitdiff/8f443077416fd820375b1bc0d1276286d23348fc remaining issues should be in new bug reports -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in wine package in Ubuntu: Fix Released Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- Mailing list: https://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 1409956] [NEW] nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build
Public bug reported: Error occurred whilst upgrading ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Tue Jan 13 07:49:23 2015 InstallationDate: Installed on 2014-04-22 (265 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (80 days ago) modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1409956 Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: Error occurred whilst upgrading ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-29-generic Date: Tue Jan 13 07:49:23 2015 InstallationDate: Installed on 2014-04-22 (265 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (80 days ago) modified.conffile..etc.modprobe.d.nvidia.331.updates.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1409956/+subscriptions -- Mailing list: https://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 1164939] Re: Google Talk account in empathy refuses to sign in
#2 worked for me, thanks -- 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/1164939 Title: Google Talk account in empathy refuses to sign in Status in empathy package in Ubuntu: Confirmed Bug description: I've got 3 Google accounts in my online accounts. Empathy refuses to sign in with them citing "Google Talk account requires authorisation" for all three. However, on clicking the button that opens Online Accounts, nothing abnormal shows. Switching the account off, then back on has no impact. There is no option to reauth the accounts, which sometimes appears - when it does, I get the google login screen and then it works, usually until the next reboot. http://pastebin.com/RNHDKfSx is the pastebin of the Auth log from empathy-debugger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1164939/+subscriptions -- Mailing list: https://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 1302668] Re: unity-control-center crashed with signal 5 in _XReply()
I just hit this bug in 14.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1302668 Title: unity-control-center crashed with signal 5 in _XReply() Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: it crashes when changing display options... so strange Ubuntu 14.04 daily iso. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1 Uname: Linux 3.14.0-031400-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 17:21:06 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140403) ProcCmdline: unity-control-center Signal: 5 SourcePackage: unity-control-center StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XOpenDevice () from /usr/lib/x86_64-linux-gnu/libXi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libmouse-properties.so Title: unity-control-center crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302668/+subscriptions -- Mailing list: https://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 1377859] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
I also ran into this bug today. Unfortunately, trying to switch to free drivers and I hit this other bug too: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331/+bug/1369398. I'm currently stuck between bugs on my system :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1377859 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 DKMSKernelVersion: 3.16.0-20-generic Date: Mon Oct 6 09:25:51 2014 InstallationDate: Installed on 2013-03-09 (575 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1377859/+subscriptions -- Mailing list: https://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 1372703] [NEW] xauth locking fails with ssh X11 forwarding
Public bug reported: Appears to be this (fixed) bug https://bugzilla.redhat.com/show_bug.cgi?id=863239 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xauth 1:1.0.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Tue Sep 23 10:58:37 2014 InstallationDate: Installed on 2012-09-01 (751 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: xauth UpgradeStatus: Upgraded to trusty on 2014-06-09 (105 days ago) ** Affects: xauth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xauth in Ubuntu. https://bugs.launchpad.net/bugs/1372703 Title: xauth locking fails with ssh X11 forwarding Status in “xauth” package in Ubuntu: New Bug description: Appears to be this (fixed) bug https://bugzilla.redhat.com/show_bug.cgi?id=863239 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xauth 1:1.0.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Tue Sep 23 10:58:37 2014 InstallationDate: Installed on 2012-09-01 (751 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) SourcePackage: xauth UpgradeStatus: Upgraded to trusty on 2014-06-09 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xauth/+bug/1372703/+subscriptions -- Mailing list: https://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 1372213] Re: system-config-printer.py crashed with TypeError in probe_queue(): 'str' does not support the buffer interface
This bug was marked private by default. I've moved it to public because at quick glance I don't see any personal information in the files or logs uploaded. Please let me know if this is not the case and it really should be private. =) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1372213 Title: system-config-printer.py crashed with TypeError in probe_queue(): 'str' does not support the buffer interface Status in “system-config-printer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. Add a Printer in System Settings 2. Select Network Printer 3. Selected LPD/LPR Host or Printer 4. Enter IP 192.168.1.100 5. Click Probe Crashes every time. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: system-config-printer-gnome 1.5.1+20140911-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Sun Sep 21 20:49:23 2014 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2014-09-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140919) InterpreterPath: /usr/bin/python3.4 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H PackageArchitecture: all Papersize: letter ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic root=UUID=5e6ccdb1-444a-4fe4-a73e-a9ebc02ac771 ro quiet splash PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py'] SourcePackage: system-config-printer Title: system-config-printer.py crashed with TypeError in probe_queue(): 'str' does not support the buffer interface UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GMA-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1372213/+subscriptions -- Mailing list: https://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 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
I am uncertain if HDA retask made permanent changes to the mapping? I chose boot override and then restarted. When relaunching hdajackretask i see that none of the overrides are checked. Is this because changes were already made and are now in effect? I still do not understand which nodes are for which speakers. The other Alienware bug guy said 0x1a is subwoofer? I probably dont need a separate volume control for subwoofer, as I dont even think windows has this. I just need sound to come out of the 2 missing speakers. So, I assume 0x1a is for Subwoofer? How do I get sound out of other speakers? Are they "left" and "right" or "front" and "back"? And are you saying one or two of the pins from hdajackretask is assigned to internal speakers? I read the other bug report, but I do not understand fully how pins work, or how to locate and assign missing speakers. I just want sound to play out of all internal speakers. Right now I can get good sound from Headphones, that is not a problem so far, but sound is bad quality, probably because all of it coming through subwoofer. How does it know how to split sound to the (2) other speakers in addition to subwoofer? Also, what should my .asoundrc file look like for a 2.1 surround setup? And, does daemon.conf make a difference, or that is only related to the controls in PulseAudio? I think I need some sort of simple instructions because I am not a hardware expert, and do not fully understand how the hardware is mapped by default. > Date: Sun, 6 Jul 2014 05:21:52 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021 > > do you get sound from from subwoofer after retasking node 0x1a ? > > since you have two headphone , speakers and subwoofer > > the current driver only create two volume controls for headphone And > speaker > > you may need to retask one headphone Jack to UN connected if you want > the driver to create volume controls for speaker and subwoofer > > https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa > /HD-Audio.txt > > `CONFIG_SND_HDA_HWDEP` is a useful option for debugging the driver. > When this is enabled, the driver creates hardware-dependent devices > (one per each codec), and you have a raw access to the device via > these device files. For example, `hwC0D2` will be created for the > codec slot #2 of the first card (#0). For debug-tools such as > hda-verb and hda-analyzer, the hwdep device has to be enabled. > Thus, it'd be better to turn this on always. > > `CONFIG_SND_HDA_RECONFIG` is a new option, and this depends on the > hwdep option above. When enabled, you'll have some sysfs files under > the corresponding hwdep directory. See "HD-audio reconfiguration" > section below. > > http://git.alsa-project.org/?p=alsa- > tools.git;a=blob;f=hdajackretask/README;hb=HEAD > > > apply now button work only when driver is build with reconfig and the program > can kill pulseaudio and can dynamic receive configure the driver > > the alternative is to use hda analyzer , just set pinctl of the > subwoofer node to out and connected the node to one of the audio output > , unmute the switch along the path and change the volume slider > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F puls
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Update: I reinstalled alsa-daily and I was able to get 'hda jack retask' to function. I choose show unconnected pins and advanced override. Raymond suggested a couple of nodes that might be the internal speakers for this model. I tried experimenting by checking "override" and setting to "speaker", "internal" etc changing various settings. I am not sure what I should set these to or if they are just labels? Does it matter? Regardless, it does not seem to affect anything in speaker-test. One thing I should note though is that somehow now the speaker-test has sound only coming out when displaying "LFE". Previously sound was only coming out of one channel, however sound would come out of that channel while displaying "front-left", "front-right"...etc. Nothing has really changed though in regards to the actual sound, only what is displayed on the screen while testing has changed, so maybe just the config? So, now I have only sound coming out of LFE (as before) but now it only comes out when "LFE" is displayed, rather than playing sound while the other channel names are displayed. Secondly, When I use "override", I see that it adds a control to "alsamixer", however it doesnt add a full bar, but rather just says "00" and is at a fixed position in alsamixer. I am uncertain if this is normal. At this point I dont fully understand if all of these are making up one collective, or if I should be able to adjust each one separate. I would assume because it is a laptop that there should only be one Master control in alsamixer?...and that sound should be automatically mapped to each present speaker. Let me know if that is correct. If that is the case, then I am still hung up with detection of those "missing" speakers. Why are they not detected automatically and am I on the right track using 'hdajackretask' to get them detected/assigned? I could not find a guide on using hdajackretask, so I just need to know what settings to use and i assume I just trial and error by hitting "apply", then doing speaker-test to see if any others show sound? If that is the case, however ...why was i told i was getting sound on (4) of those speakers, but in actuality it only came out of (1) of them, while displaying each one. I am just trying to understand why it does not display the actual speaker which is playing. The only idea i had was that sound is right now mapped only to the subwoofer and so when it does the test right now for each speaker, the subwoofer receives the test for each instead of the missing speakers. So, I need to know how to reassign it so that the subwoofer only receives the test for the subwoofer, and the other 2 speakers receive their own test signal. I hope this makes sense. P.S. - Many of the suggestions have to do with the Headphone jacks, but my problem is related to the internal speakers. As far as I understand, they are separate issues? > Date: Tue, 24 Jun 2014 11:27:26 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > > One other thing I noticed is upon startup/load of Ubuntu, at the top > of the screen it says something about snd hda codec "module has bad > taint". > > This is the alsa daily build module. It is printing an warning message > to inform you that you're running a module that was not compiled with > the rest of the kernel. You can ignore it. > > > tee: /sys/class/sound/hwC0D0/reconfig: No such file or directory > > Hmm, maybe this is related to the daily HDA DKMS too, somehow. There has > been some reorganising upstream w r t the devices. Try uninstalling the > daily DKMS again, reboot, and retry. > > > Are there any guides for this hdajackretask as to how I can do what > you say, otherwise how might I get started experimenting with > hdajackretask? > > Omgubuntu wrote a small introduction here, not sure how helpful it is: > > http://www.omgubuntu.co.uk/2013/12/turn-headphone-jack-microphone-jack- > ubuntu > > > @David : I think you meant modprobe.d (not modprobe.conf) > > Yes, thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > >
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Just got back from vacation and continuing this effort to resolve. In reviewing your notes, Do you understand that My headphone jacks sound fine, however the internal speakers seem to be mapped wrong or unmapped? I just need to know how to find which speakers are on what nodes and also how to group/set them up in 'hda jack retask' so that the sound will split to each of them. I believe it should be 2.1 for the laptop so (2) speakers and (1) subwoofer. > Date: Wed, 25 Jun 2014 10:10:40 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/hda_auto_parser.c?id=1c70a583417e8db1e1d5069d7651ba294e9499de > > using hda Jack retask to add headset mic > > and specify hint by modifying hda-jack-retask.fw generated by hda Jack > retask > > parser_flags = 4 > > to force the parser to find headset Mic which have specific sequence > number 0x0c and set misc bit (bit 8) > > https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa > /HD-Audio.txt > > however the current logic of auto Mic selection won't consider the extra > Mic jack in alienware > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F pulseaudio >/dev/snd/controlC0: phallix1730 F pulseaudio > phallix8573 F alsamixer > CurrentDesktop: Unity > Date: Sat Jun 21 21:02:28 2014 > InstallationDate: Installed on 2014-06-15 (6 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_Type: Only some of outputs are working > Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/23/2014 > dmi.bios.vendor: Alienware > dmi.bios.version: A07 > dmi.board.name: 01W2J2 > dmi.board.vendor: Alienware > dmi.board.version: A02 > dmi.chassis.type: 8 > dmi.chassis.vendor: Alienware > dmi.chassis.version: A07 > dmi.modalias: > dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: > dmi.product.name: Alienware 18 > dmi.product.version: A07 > dmi.sys.vendor: Alienware > mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332900/+subscriptions -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing t
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Update: I have reinstalled alsa-base.conf as instructed. I ran the hdajackretask program with the "show unconnected pins" option. Upon hitting apply, I get the following message: tee: /sys/class/sound/hwC0D0/reconfig: No such file or directory I assume it is looking for a reconfig file in that directory but there is no such file? Let me know. > Date: Mon, 23 Jun 2014 19:10:44 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > @David : I think you meant modprobe.d (not modprobe.conf) > > @Austin: I'm not aware of any guides beyond the links already given. > Install the alsa-tools-gui package and run the hdajackretask program. > Check the option to show unconnected pins, and try setting them to an > internal speaker. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F pulseaudio >/dev/snd/controlC0: phallix1730 F pulseaudio > phallix8573 F alsamixer > CurrentDesktop: Unity > Date: Sat Jun 21 21:02:28 2014 > InstallationDate: Installed on 2014-06-15 (6 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_Type: Only some of outputs are working > Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/23/2014 > dmi.bios.vendor: Alienware > dmi.bios.version: A07 > dmi.board.name: 01W2J2 > dmi.board.vendor: Alienware > dmi.board.version: A02 > dmi.chassis.type: 8 > dmi.chassis.vendor: Alienware > dmi.chassis.version: A07 > dmi.modalias: > dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: > dmi.product.name: Alienware 18 > dmi.product.version: A07 > dmi.sys.vendor: Alienware > mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332900/+subscriptions -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing the bug test, it said sound would alternate between 2 channels, however I only heard one consistent sound. It did not alternate. I bel
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Ok. I will start by trying to install alsa-tools-gui package. One other thing I noticed is upon startup/load of Ubuntu, at the top of the screen it says something about snd hda codec "module has bad taint". It is difficult to read exactly because it flashes only for a second during load. I am unsure if this is related to the same problem but since it has to do with alsa I knew it was worth mentioning. If you know anything about this message please let me know. I appreciate all of the help thus far. Austin > Date: Mon, 23 Jun 2014 19:10:44 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > @David : I think you meant modprobe.d (not modprobe.conf) > > @Austin: I'm not aware of any guides beyond the links already given. > Install the alsa-tools-gui package and run the hdajackretask program. > Check the option to show unconnected pins, and try setting them to an > internal speaker. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F pulseaudio >/dev/snd/controlC0: phallix1730 F pulseaudio > phallix8573 F alsamixer > CurrentDesktop: Unity > Date: Sat Jun 21 21:02:28 2014 > InstallationDate: Installed on 2014-06-15 (6 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_Type: Only some of outputs are working > Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/23/2014 > dmi.bios.vendor: Alienware > dmi.bios.version: A07 > dmi.board.name: 01W2J2 > dmi.board.vendor: Alienware > dmi.board.version: A02 > dmi.chassis.type: 8 > dmi.chassis.vendor: Alienware > dmi.chassis.version: A07 > dmi.modalias: > dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: > dmi.product.name: Alienware 18 > dmi.product.version: A07 > dmi.sys.vendor: Alienware > mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332900/+subscriptions -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Thanks for the response. Are there any guides for this hdajackretask as to how I can do what you say, otherwise how might I get started experimenting with hdajackretask? I am a fast learner, but new to both Ubuntu and Linux-based systems. If you have some information on how I can do this that would be great, and I can post the solution on Ubuntu forums if we are able to figure it out. > Date: Mon, 23 Jun 2014 14:44:06 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > > I tried to re-submit the bug report but I am not really sure what the > alsa-base.conf should look like or how to reinstall/overwrite. > > These commands will replace your alsa-base.conf with the original one: > sudo mv /etc/modprobe.conf/alsa-base.conf ~/alsa-base.conf.old > sudo apt-get install alsa-base --reinstall > > Otherwise I think Raymond is right, you need to experiment a bit with > hdajackretask (in the alsa-tools-gui package) to find the internal > speaker, because BIOS does only indicate 0x14 as speaker - and that's > probably the subwoofer if that's the only thing you hear audio from. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F pulseaudio >/dev/snd/controlC0: phallix1730 F pulseaudio > phallix8573 F alsamixer > CurrentDesktop: Unity > Date: Sat Jun 21 21:02:28 2014 > InstallationDate: Installed on 2014-06-15 (6 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_Type: Only some of outputs are working > Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/23/2014 > dmi.bios.vendor: Alienware > dmi.bios.version: A07 > dmi.board.name: 01W2J2 > dmi.board.vendor: Alienware > dmi.board.version: A02 > dmi.chassis.type: 8 > dmi.chassis.vendor: Alienware > dmi.chassis.version: A07 > dmi.modalias: > dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: > dmi.product.name: Alienware 18 > dmi.product.version: A07 > dmi.sys.vendor: Alienware > mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332900/+subscriptions -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing the bug test, it said sound would alternate between 2 channels, however I only h
Re: [Desktop-packages] [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
I tried to re-submit the bug report but I am not really sure what the alsa-base.conf should look like or how to reinstall/overwrite. It should be noted that I had this problem immediately upon installing Ubuntu, so nothing I have changed has been the cause. I have been attempting to fix it but it is hard to understand why it cannot detect this from a default install. I was though able to update the alsa daily package and now it shows ALC3661 so that part at least shows right now, but still trying to understand how it doesnt register the laptop speakers. Let me know if you have any further troubleshooting I can do... > Date: Sun, 22 Jun 2014 04:02:05 + > From: 1332...@bugs.launchpad.net > To: bluemon...@live.com > Subject: [Bug 1332900] Re: [Alienware 18, Realtek ALC668, Speaker, Internal] > Playback problem > > You have modified /etc/modprobe.d/alsa-base.conf to include these lines: > > " > options snd-hda-intel model=targa-dig > options snd slots=snd-hda-intel > # u1Nb.u_BNWJ+LvyF:82801I (ICH9 Family) HD Audio Controller > alias snd-card-0 snd-hda-intel > " > > Please revert this file to the original configuration (i e remove the > lines quoted above), reboot, and test again. > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1332900 > > Title: > [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > > Status in “alsa-driver” package in Ubuntu: > Incomplete > > Bug description: > Bug seems similar to another reported bug with Alienware 18 laptops. > It should be Realtek ALC3661 however it shows up as ALC668. Sound only > comes out of 1 Channel, which appears to be subwoofer. Unlike the > other bug, closing the lid appears to have no effect on sound. > > When doing the bug test, it said sound would alternate between 2 > channels, however I only heard one consistent sound. It did not > alternate. I believe it is playing from the subwoofer only. I would > love to know more about how to route the sound to the proper speakers. > > I attempted modifications to daemon.conf in pulse and .asoundrc but > have not found the correct configuration yet. > > This laptop is equipped with 2.1 Surround and should play sound > accordingly. Also, alsamixer only shows (1) speaker control, whether > this is normal I am unsure. > > > Ubuntu 14.04 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 > Uname: Linux 3.13.0-29-generic x86_64 > NonfreeKernelModules: wl nvidia > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: phallix1730 F pulseaudio >/dev/snd/controlC0: phallix1730 F pulseaudio > phallix8573 F alsamixer > CurrentDesktop: Unity > Date: Sat Jun 21 21:02:28 2014 > InstallationDate: Installed on 2014-06-15 (6 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_Jack: Speaker, Internal > Symptom_Type: Only some of outputs are working > Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/23/2014 > dmi.bios.vendor: Alienware > dmi.bios.version: A07 > dmi.board.name: 01W2J2 > dmi.board.vendor: Alienware > dmi.board.version: A02 > dmi.chassis.type: 8 > dmi.chassis.vendor: Alienware > dmi.chassis.version: A07 > dmi.modalias: > dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: > dmi.product.name: Alienware 18 > dmi.product.version: A07 > dmi.sys.vendor: Alienware > mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332900/+subscriptions -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing th
[Desktop-packages] [Bug 1333027] [NEW] [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem
Public bug reported: I tried to fix the alsa-base.conf, however I am not sure what the default configuration should be.Either way, I do hear the test tone but it doesnt alternate between speakers/channels. It just sounds one constant tone. The same happens when i do a speaker-test, i get pink noise through the same output, even though it reads front-left, front- right, center, lfe it plays sound while displaying those 4, however the sound comes through the lfe from what it sounds like (the sound only plays through one output). If you have a preferred alsa-base.conf or a way for me to overwrite it, let me know and we can proceed. I modified it due to this problem. Since installing Ubuntu I have not had the sound working properly so I have been trying configuration edits (with no success so far). I noticed no subdevices are displayed. I am not sure how the card decides where to send sound to but the interesting thing is that when testing in Pulseaudio I get sound playing when clicking front-left, front-right but nothing from clicking subwoofer. And again, the front-left and front-right all play the tone through the same speaker..theres no difference and apparently my guess is not all of my speakers are being detected as available options because I also only have (1) speaker control in Alsamixer. Surely there must be some way to get 2.1 speakers correctly configured? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phallix1713 F pulseaudio /dev/snd/controlC0: phallix1713 F pulseaudio CurrentDesktop: Unity Date: Sun Jun 22 16:04:53 2014 InstallationDate: Installed on 2014-06-15 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A07 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A07 dmi.modalias: dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: dmi.product.name: Alienware 18 dmi.product.version: A07 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-22T16:04:27.421233 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1333027 Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: I tried to fix the alsa-base.conf, however I am not sure what the default configuration should be.Either way, I do hear the test tone but it doesnt alternate between speakers/channels. It just sounds one constant tone. The same happens when i do a speaker-test, i get pink noise through the same output, even though it reads front-left, front- right, center, lfe it plays sound while displaying those 4, however the sound comes through the lfe from what it sounds like (the sound only plays through one output). If you have a preferred alsa-base.conf or a way for me to overwrite it, let me know and we can proceed. I modified it due to this problem. Since installing Ubuntu I have not had the sound working properly so I have been trying configuration edits (with no success so far). I noticed no subdevices are displayed. I am not sure how the card decides where to send sound to but the interesting thing is that when testing in Pulseaudio I get sound playing when clicking front-left, front-right but nothing from clicking subwoofer. And again, the front-left and front-right all play the tone through the same speaker..theres no difference and apparently my guess is not all of my speakers are being detected as available options because I also only have (1) speaker control in Alsamixer. Surely there must be some way to get 2.1 speakers correctly configured? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64
[Desktop-packages] [Bug 1332900] [NEW] [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem
Public bug reported: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing the bug test, it said sound would alternate between 2 channels, however I only heard one consistent sound. It did not alternate. I believe it is playing from the subwoofer only. I would love to know more about how to route the sound to the proper speakers. I attempted modifications to daemon.conf in pulse and .asoundrc but have not found the correct configuration yet. This laptop is equipped with 2.1 Surround and should play sound accordingly. Also, alsamixer only shows (1) speaker control, whether this is normal I am unsure. Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phallix1730 F pulseaudio /dev/snd/controlC0: phallix1730 F pulseaudio phallix8573 F alsamixer CurrentDesktop: Unity Date: Sat Jun 21 21:02:28 2014 InstallationDate: Installed on 2014-06-15 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A07 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A07 dmi.modalias: dmi:bvnAlienware:bvrA07:bd04/23/2014:svnAlienware:pnAlienware18:pvrA07:rvnAlienware:rn01W2J2:rvrA02:cvnAlienware:ct8:cvrA07: dmi.product.name: Alienware 18 dmi.product.version: A07 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-06-17T23:18:00.223827 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1332900 Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem Status in “alsa-driver” package in Ubuntu: New Bug description: Bug seems similar to another reported bug with Alienware 18 laptops. It should be Realtek ALC3661 however it shows up as ALC668. Sound only comes out of 1 Channel, which appears to be subwoofer. Unlike the other bug, closing the lid appears to have no effect on sound. When doing the bug test, it said sound would alternate between 2 channels, however I only heard one consistent sound. It did not alternate. I believe it is playing from the subwoofer only. I would love to know more about how to route the sound to the proper speakers. I attempted modifications to daemon.conf in pulse and .asoundrc but have not found the correct configuration yet. This laptop is equipped with 2.1 Surround and should play sound accordingly. Also, alsamixer only shows (1) speaker control, whether this is normal I am unsure. Ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: phallix1730 F pulseaudio /dev/snd/controlC0: phallix1730 F pulseaudio phallix8573 F alsamixer CurrentDesktop: Unity Date: Sat Jun 21 21:02:28 2014 InstallationDate: Installed on 2014-06-15 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC668, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A07 dmi.board.name: 01W2J2 dmi.boar
[Desktop-packages] [Bug 371897]
Bugzilla is not for discussion, as has been pointed out, e.g., http://bugs.winehq.org/show_bug.cgi?id=10495#c251. Please take the discussion somewhere else. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Status in “wine” package in Ubuntu: Fix Released Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- Mailing list: https://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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring) and 13.10 (saucy)
Echoing Doctor Rover here - I can change to A2DP in Trusty, but the profile doesn't actually switch. If you close the sound control panel and open it back up, it remains on Telephony Duplex. #15 seems to be working so far. ** Summary changed: - Failed to change profile to A2DP in 13.04 (Raring) and 13.10 (saucy) + Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer" * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp" I've already added "Enable=Socket" in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+subscriptions -- Mailing list: https://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 1300854] [NEW] PCI/internal sound card not detected
Public bug reported: Again I updated after the last time I fixed the audio but this time the update made it so alsamixer is not working and can't be found, my audioc cards cant be found, no sound what so ever. The thing it says its playing sound through is a "Dummy Output". please fix. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Apr 1 08:13 seq crw-rw---T 1 root audio 116, 33 Apr 1 08:13 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Apr 1 08:26:18 2014 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd11/24/2008:svnTOSHIBA:pnSatelliteA305:pvrPSAG8U-04001W:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A305 dmi.product.version: PSAG8U-04001W dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1300854 Title: PCI/internal sound card not detected Status in “alsa-driver” package in Ubuntu: New Bug description: Again I updated after the last time I fixed the audio but this time the update made it so alsamixer is not working and can't be found, my audioc cards cant be found, no sound what so ever. The thing it says its playing sound through is a "Dummy Output". please fix. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Apr 1 08:13 seq crw-rw---T 1 root audio 116, 33 Apr 1 08:13 timer AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Apr 1 08:26:18 2014 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd11/24/2008:svnTOSHIBA:pnSatelliteA305:pvrPSAG8U-04001W:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A305 dmi.product.version: PSAG8U-04001W dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1300854/+subscriptions -- Mailing list: https://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 1299062] [NEW] [Satellite A305, Realtek ALC268, Speaker, Internal] No sound at all not even with headphones.
Public bug reported:
I downloaded a few software updates this morning through the Update
Manager and after that I have not had any audio in the speakers or
through headphones. I tried messing with audio card selection, tried to
check and see if it was muted but i still go no sound at all.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-18-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: austin 2357 F pulseaudio
/dev/snd/pcmC0D1p: austin 2357 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd680 irq 47'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff1e,0013
HDA:11c11040,11790001,00100200'
Controls : 28
Simple ctrls : 12
Date: Fri Mar 28 08:20:02 2014
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
2357 2357 austinF pulseaudio
/dev/snd/pcmC0D1p: austinF...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Satellite A305, Realtek ALC268, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2008
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDE:bvr1.70:bd11/24/2008:svnTOSHIBA:pnSatelliteA305:pvrPSAG8U-04001W:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite A305
dmi.product.version: PSAG8U-04001W
dmi.sys.vendor: TOSHIBA
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise running-unity
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1299062
Title:
[Satellite A305, Realtek ALC268, Speaker, Internal] No sound at all
not even with headphones.
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
I downloaded a few software updates this morning through the Update
Manager and after that I have not had any audio in the speakers or
through headphones. I tried messing with audio card selection, tried
to check and see if it was muted but i still go no sound at all.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-18-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: austin 2357 F pulseaudio
/dev/snd/pcmC0D1p: austin 2357 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd680 irq 47'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1179ff1e,0013
HDA:11c11040,11790001,00100200'
Controls : 28
Simple ctrls : 12
Date: Fri Mar 28 08:20:02 2014
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386
(20140204)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
2357 2357 austinF pulseaudio
/dev/snd/pcmC0D1p: austinF...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Satellite A305, Realtek ALC268, Speaker, Internal] No sound
[Desktop-packages] [Bug 1238186] Re: Every time after resume, have to unlock/logon twice
This is also affecting me on a fresh install of Ubuntu 14.04, on two separate machines - my HP Compaq 8710W (64-bit + NVIDIA) and my IBM ThinkPad T43 (32-bit). -- 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/1238186 Title: Every time after resume, have to unlock/logon twice Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: My computer suspends after leaving it for 1 hour. When using it again, it resumes and I have to login to unlock. Then right after login, the screen goes black and I'm at the logon prompt again. Settings are both suspend & turn screen off after 1 hour. Note! I cannot reproduce this problem when I lower the timers to screen off after 10 minutes and suspend 30 minutes. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-power-manager 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Thu Oct 10 19:52:20 2013 InstallationDate: Installed on 2012-08-03 (432 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to saucy on 2013-09-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1238186/+subscriptions -- Mailing list: https://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 1263568] [NEW] nvidia-304-updates 304.108-0ubuntu1: nvidia-304-updates kernel module failed to build
Public bug reported: Switching to nvidia-331 produced the attached logs. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: nvidia-304-updates (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 3.11.0-15-generic Date: Sun Dec 22 14:10:43 2013 InstallationDate: Installed on 2012-04-11 (620 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True PackageVersion: 304.108-0ubuntu1 SourcePackage: nvidia-graphics-drivers-304-updates Title: nvidia-304-updates 304.108-0ubuntu1: nvidia-304-updates kernel module failed to build UpgradeStatus: Upgraded to saucy on 2013-11-12 (40 days ago) modified.conffile..etc.modprobe.d.nvidia.304.updates.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1263568 Title: nvidia-304-updates 304.108-0ubuntu1: nvidia-304-updates kernel module failed to build Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: New Bug description: Switching to nvidia-331 produced the attached logs. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: nvidia-304-updates (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 3.11.0-15-generic Date: Sun Dec 22 14:10:43 2013 InstallationDate: Installed on 2012-04-11 (620 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True PackageVersion: 304.108-0ubuntu1 SourcePackage: nvidia-graphics-drivers-304-updates Title: nvidia-304-updates 304.108-0ubuntu1: nvidia-304-updates kernel module failed to build UpgradeStatus: Upgraded to saucy on 2013-11-12 (40 days ago) modified.conffile..etc.modprobe.d.nvidia.304.updates.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1263568/+subscriptions -- Mailing list: https://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 1262060] [NEW] Snapped wrap over to other workspace
Public bug reported: When you snap a window to the right side of the workspace, switch workspaces, and try recalling the window with unity, the window appears underneath unity while the workspace remains stationary. See video for example: http://youtu.be/8b45Izqp6QA ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-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 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Dec 17 18:37:25 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.32, 3.8.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2334] JockeyStatus: xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_304 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_304_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:nvidia_319 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use) xorg:nvidia_319_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use) MachineType: EVGA 122-CK-NF68 MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=02dbc501-c9cd-42e5-8bed-191ffe17cf73 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA version.compiz: compiz 1:0.9.7.12-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1262060 Title: Snapped wrap over to other workspace Status in “xorg” package in Ubuntu: New Bug description: When you snap a window to the right side of the workspace, switch workspaces, and try recalling the window with unity, the window appears underneath unity while the workspace remains stationary. See video for example: http://youtu.be/8b45Izqp6QA ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-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 319.32 Wed Jun 19 15:51:20 PDT 2013 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch
[Desktop-packages] [Bug 1172313] Re: Displays Connected (none)
Seems to only happen on networks using WPA-Enterprise (e.g. my university's wi-fi), but it may be an issue unrelated to that. This is still happening in Ubuntu 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1172313 Title: Displays Connected (none) Status in “network-manager” package in Ubuntu: Confirmed Bug description: Since upgrading to 13.04 when I connect to my wireless network I see a notification that says "Connected (none)" where "(none)" is there instead of the wireless SSID of the network I'm connected to or the name of the wireless connection (from edit connections) in the menu. It still really is connected and the wireless is working. If I go to the connection information it knows what the names are there, though I didn't see the SSID in that information. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Wed Apr 24 07:56:53 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-08 (166 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) IpRoute: default via 192.168.2.1 dev eth8 proto static 169.254.0.0/16 dev eth8 scope link metric 1000 192.168.2.0/24 dev eth8 proto kernel scope link src 192.168.2.195 metric 1 192.168.2.0/24 dev wlan1 proto kernel scope link src 192.168.2.165 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-04-19 (5 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB0cdma disconnected /org/freedesktop/NetworkManager/Devices/23 wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth8 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172313/+subscriptions -- Mailing list: https://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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
@Chhatoi Pritam Baral Thanks for building a fix for this issue, I know I appreciate it. I do have a question though. I can't seem to get the package through apt-get. I put the ppa into my repositories, but when I do sudo apt-get install network-manager-applet it can't find it (am I using the wrong package name?) I feel so close to finally being able to getting wifi working that it really sucks not to be able to get the package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: New Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions -- Mailing list: https://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 1170835] Re: package libsane 1.0.23-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of packa
happens even on Lubuntu 13.04 while trying to Teamviewer -- 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/1170835 Title: package libsane 1.0.23-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of package libsane:i386 Status in “sane-backends” package in Ubuntu: Confirmed Bug description: Trying to install google earth. Keep getting error: "New software can't be installed, because there is a problem with the software currently installed. Do you want to repair this problem now?" I am presented with two buttons: "Cancel" and "Repair". After a few seconds I get this: installArchives() failed: (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 412182 files and directories currently installed.) Unpacking libsane:i386 (from .../libsane_1.0.23-0ubuntu1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsane_1.0.23-0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of package libsane:i386 Errors were encountered while processing: /var/cache/apt/archives/libsane_1.0.23-0ubuntu1_i386.deb Error in function: dpkg: dependency problems prevent configuration of ia32-libs-multiarch: ia32-libs-multiarch depends on libsane; however: Package libsane:i386 is not installed. dpkg: error processing ia32-libs-multiarch (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ia32-libs: ia32-libs depends on ia32-libs-multiarch; however: Package ia32-libs-multiarch is not configured yet. dpkg: error processing ia32-libs (--configure): dependency problems - leaving unconfigured This happens over and over, never resolving. Eventually gave up. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libsane 1.0.23-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 AptOrdering: libsane: Install libsane: Configure ia32-libs-multiarch: Configure ia32-libs: Configure Architecture: amd64 Date: Fri Apr 19 16:14:06 2013 DpkgTerminalLog: Unpacking libsane:i386 (from .../libsane_1.0.23-0ubuntu1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsane_1.0.23-0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of package libsane:i386 ErrorMessage: trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of package libsane:i386 InstallationDate: Installed on 2012-04-15 (369 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: sane-backends Title: package libsane 1.0.23-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/sane.d/kodakaio.conf', which is different from other instances of package libsane:i386 UpgradeStatus: Upgraded to raring on 2013-03-15 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1170835/+subscriptions -- Mailing list: https://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 1209092] Re: network : gnome-control-center crashed with SIGABRT in g_assertion_message
Still affecting me in Ubuntu GNOME 13.10. -- 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/1209092 Title: network : gnome-control-center crashed with SIGABRT in g_assertion_message Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: The problem arised after upgrade to 13.10. To reproduce: 1. Click on System Settings 2. Gnome Control Center window appears 3. Click on Network under Hardware section 4. At this point Gnome Control Center window crashes. Thanks. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu30 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 7 09:30:30 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-03-26 (1229 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) MarkForUpload: True ProcCmdline: gnome-control-center Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so Title: [network]: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to saucy on 2013-08-07 (0 days ago) UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager0.9.7-0ubuntu4 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1 indicator-datetime 12.10.3+13.10.20130731-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1209092/+subscriptions -- Mailing list: https://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 1214564] Re: Disappearing mouse cursor after nvidia packages update.
Hi, I hope this isn't too late but I had the same problem. It was a wired mouse with the circle green plug end. I disconnected that one and plugged in a USB mouse and the pointer showed up and has been working fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1214564 Title: Disappearing mouse cursor after nvidia packages update. Status in “nvidia-graphics-drivers-304” package in Ubuntu: Confirmed Bug description: Hi. After upgrade (Tue Aug 20, 2013) of nVidia related packages such as: nvidia-settings, nvidia-current and after installing two new ones - nvidia-304 and nvidia settings-304, I noticed that after restart, all system fonts were enlarged - terminal fonts, desktop fonts, windows fonts. Generally everywhere. I had to change size by hand. But there is one more problem: mouse cursor. If the mouse is not in use (I mean e.g. no user reaction) from time to time, mouse cursor is disappearing for a one, two seconds. The same thing happens when I'm moving mouse or when I'm trying to open/close a directory, mark a file by one click or simply - clicking on anything. It is pretty strange and annoying. Before today's updates, everything was okay. All installed packages related to nVidia: ,-[ $ dpkg -l | grep nvidia ] | nvidia-304 304.88-0ubuntu0.0.3[1] | nvidia-common 1:0.2.44.2 | nvidia-current 304.88-0ubuntu0.0.3 | nvidia-settings 304.88-0ubuntu0.0.3 | nvidia-settings-304 304.88-0ubuntu0.0.3[1] `- Also, there is no icon for a 'NVIDIA X Server Settings' utility (available via menu). When I'm trying to open this application, I'm seeing warning message, that I'm not using a 'nvidia' driver and I should run 'nvidia-xconfig' as root and restart X11, which I did, but after X11 restart, everything was so huge. I could not choose 1024x768 resolution, because there was not such option - only three were available: 800x600 and lower etc. Earlier, I was able to open X Server Settings and view/set many options. I have had to remove '/etc/X11/xorg.conf' file created by nvidia-xconfig command, and change name of 'xorg.conf.backup' file to 'xorg.conf'. After restart, everything seems return to normal, but still there is a problem with mouse cursor. * Architecture: i386 * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant) * Uname: Linux 3.2.0-52-generic-pae i686 * ApportVersion: 2.0.1-0ubuntu17.4 * NonfreeKernelModules: nvidia * Xorg version: 1:7.6+12ubuntu2 (xserver-xorg) * xserver-xorg-core: 2:1.11.4-0ubuntu10.13 I'm using Xubuntu 12.04.2 LTS. After/during installation there were no need to configure anything related to my nVidia graphics card (GeForce 7100). Everything worked out-of-the-box. Till today. Even during system booting and/or closing (I don't use bootsplash), fonts are changed. Now they are... slimmer. It seems like, that today's upgrade, affects all fonts on the system. There is also problem with X11. After - for example - 30 minutes without any user reaction, monitor goes black. After moving a mouse, Desktop looks really horrible. Colors, windows decorations, fonts etc. It looks very, very bad. I don't see anything worrying in '/var/log/Xorg.0.log' file. Also '.xsession-errors' file seems to be okay. ,-[ $ lspci | grep VGA ] | 00:10.0 VGA compatible controller: NVIDIA Corporation C73 [GeForce 7100 / nForce 630i] (rev a2) `- ,-[ $ lsb_release -rd ] | Description:Ubuntu 12.04.2 LTS | Release:12.04 `- Best regards. _ [1] I have to notice, that nvidia-304 and nvidia-settings-304 packages are new and were installed during upgrade. Maybe these packages are responsible for all mentioned problems? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1214564/+subscriptions -- Mailing list: https://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 371897]
(In reply to comment #396) > I was waiting to ask this as well... Since wine 1.6 is out now, will winepulse > be one of 1.8's goals? I haven't seen many references to this on the mailing > list either lately The patch was last sent before the code freeze, back in May: http://www.winehq.org/pipermail/wine-patches/2013-May/124406.html it hasn't been sent since the code freeze ended. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Status in “wine” package in Ubuntu: Triaged Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- Mailing list: https://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 902852] Re: Timed autologin feature not working
Confirmed that after upgrade to 1.2.3-0ubuntu1, autologin settings have no effect. Downgrading to 1.2.1-0ubuntu1 gets autologin working again. Ubuntu 12.04.2 i386. -- 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/902852 Title: Timed autologin feature not working Status in Light Display Manager: Fix Released Status in Unity Greeter: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “lightdm” source package in Precise: Fix Released Status in “unity-greeter” source package in Precise: Fix Committed Status in “lightdm” source package in Quantal: Fix Released Status in “unity-greeter” source package in Quantal: Fix Released Bug description: [Impact] Not able to set an automatic login with a timeout on Ubuntu 12.04.1 [Test Case] 1. Enable automatic login in /etc/lightdm/lightdm.conf: [SeatDefaults] autologin-user=bob autologin-user-timeout=10 2. Restart machine 3. Wait on greeter Expected result: Greeter automatically logs in as bob after 10 seconds Observed result: Remain on login screen, nothing happens after 10 seconds. [Regression potential] Other authentication may be affected. Tested with lightdm regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/902852/+subscriptions -- Mailing list: https://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 1102445] [NEW] [i915gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000010 IPEHR: 0x01000000
Public bug reported: GPU hangs occasionally under Compiz and Unity. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 Chipset: i915gm Date: Mon Jan 21 09:31:53 2013 DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Several times a week InstallationDate: Installed on 2013-01-01 (19 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) InterpreterPath: /usr/bin/python3.3 MachineType: IBM 1871W5G MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=b9dfb8f2-b843-467d-8586-716606675b68 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.18-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 IPEHR: 0x0100 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1871W5G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1871W5G:pvrThinkPadT43:rvnIBM:rn1871W5G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1871W5G dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash freeze i386 raring third-party-packages 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/1102445 Title: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: GPU hangs occasionally under Compiz and Unity. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 Chipset: i915gm Date: Mon Jan 21 09:31:53 2013 DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Several times a week InstallationDate: Installed on 2013-01-01 (19 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) InterpreterPath: /usr/bin/python3.3 MachineType: IBM 1871W5G MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-0-generic root=UUID=b9dfb8f2-b843-467d-8586-716606675b68 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.18-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [i915gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 IPEHR: 0x0100 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1871W5G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1871W5G:pvrThinkPadT43:rvnIBM:rn1871W5G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1871W5G dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1102445/+subscriptions -- Mailing list: https://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 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
Problem is present on my hardware as well (ThinkPad T43 with Intel GM915) under Ubuntu 12.10 and 13.04 Alpha. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) Status in Unity: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in Debian GNU/Linux: New Status in “mesa” package in Fedora: Unknown Bug description: Unity 5.8.0 (Ubuntu 12.04 Beta) crashes (or hanged up) on Fujitsu-Siemens S7020 (Intel 915GM Express Chipset) very often during attempt to use Dash or switch between applications when many winsows are opened with following error: intel_do_flush_locked failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Apr 10 11:25:45 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120314) MachineType: FUJITSU SIEMENS LIFEBOOK S7020 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=e6a4deb8-3e53-4afb-aed8-997537309262 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2005 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.07 dmi.board.name: FJNB19C dmi.board.vendor: FUJITSU dmi.board.version: CP234410-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7020 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd09/16/2005:svnFUJITSUSIEMENS:pnLIFEBOOKS7020:pvr:rvnFUJITSU:rnFJNB19C:rvrCP234410-02:cvnFUJITSUSIEMENS:ct10:cvrS7020: dmi.product.name: LIFEBOOK S7020 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 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 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+subscriptions -- Mailing list: https://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 987034] Re: Unity Dash freezes Xorg when opened over chrome
Same exact problem for me, only with Firefox in 12.10. ** Changed in: unity (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/987034 Title: Unity Dash freezes Xorg when opened over chrome Status in “unity” package in Ubuntu: Confirmed Bug description: Fresh upgrade to 12.04 today. Unity Dash works fine, but if I attempt to open it when chrome is focused, Xorg freezes. My setup is pretty standard with the exception that I am running a vertical screen. Identical setup on 11.10 was solid with this same setup, so this must be a regression. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,neg,snap,gnomecompat,mousepoll,place,grid,vpswitch,move,compiztoolbox,wall,resize,imgpng,regex,session,unitymtgrabhandles,animation,expo,fade,workarounds,ezoom,scale,unityshell] Date: Sun Apr 22 18:44:06 2012 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/987034/+subscriptions -- Mailing list: https://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 626321]
*** Bug 18386 has been marked as a duplicate of this bug. *** -- 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/626321 Title: X.org server should keep track of and restore its initial (desktop) resolution and refresh rate Status in Wine: Won't Fix Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Triaged Bug description: Applications like games change desktop resolution (graphics mode) for their needs. Unfortunately when such applications crash then X.org server doesn't revert the resolution back to its initial mode. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/626321/+subscriptions -- Mailing list: https://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 371897]
(In reply to comment #392) > So, it's been a month since the last update about this... How are things > going? > Will winepulse make it into upstream? Has there been an actual collaboration > between Maarten and the devs? Patches have been sent, people posted reviews/comments. E.g.,: http://www.winehq.org/pipermail/wine-devel/2012-October/097482.html http://www.winehq.org/pipermail/wine-devel/2012-October/097485.html http://www.winehq.org/pipermail/wine-devel/2012-October/097486.html http://www.winehq.org/pipermail/wine-devel/2012-October/097487.html http://www.winehq.org/pipermail/wine-devel/2012-October/097602.html etc. (check http://www.winehq.org/pipermail/wine-devel/2012-October/ and look for dsound). One of the patches was resent yesterday: http://www.winehq.org/pipermail/wine-patches/2012-November/119914.html > Also, just for the record: > http://www.phoronix.com/scan.php?page=news_item&px=MTIxOTg > By the way, I think this should be changed to major, since the lack of sound > in > most (if not all) applications should be probably considered a "major loss of > functionality for a wide range of applications" Check the first comment, it's a feature request => enhancement. Pulseaudio is supposed to be compatible with ALSA, which Wine already supports, and sound does work for a lot of use cases.* *Note: This is not meant to restart the debate about Pulseaudio/Wine/etc. I'm explaining why, as a bugzilla admin, I'm not marking it major. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Status in “wine” package in Ubuntu: Triaged Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- Mailing list: https://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 207135] Re: pulseaudio uses too much CPU
This is happening for me on Precise. Still not fixed. I get stuttering sound and a slow system until I kill pulseaudio and let it restart. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/207135 Title: pulseaudio uses too much CPU Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64 Processor 3500+) when I'm just listening music using Rhythmbox. Seems too much IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/+subscriptions -- Mailing list: https://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 1075792] [NEW] Slow Unity performance in 12.10 Quantal Quetzal
Public bug reported: My ThinkPad T43 works quite well with Ubuntu 12.04, but with a clean install of 12.10, Unity is slow (I can type in the Unity Dash Home and then count the seconds as my letters slowly appear in sequence), sometimes freezes (when I close an application, the icon becomes faded in the Dash but doesn't disappear, and the application window just stays on the screen but I can't interact with it), and text develops little lines through it after suspend and resume (this was also present in 12.04 and can be fixed with a modification to the xorg.conf... something about debug-wait... but it would be nice if I didn't have to make that change on the whole batch of T43's I'm going to sell). Help appreciated :-) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Nov 6 18:10:30 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM Device [1014:0582] Subsystem: IBM Device [1014:0582] InstallationDate: Installed on 2012-11-06 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 1871W5G MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-18-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1871W5G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1871W5G:pvrThinkPadT43:rvnIBM:rn1871W5G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1871W5G dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 performance quantal running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1075792 Title: Slow Unity performance in 12.10 Quantal Quetzal Status in “xorg” package in Ubuntu: New Bug description: My ThinkPad T43 works quite well with Ubuntu 12.04, but with a clean install of 12.10, Unity is slow (I can type in the Unity Dash Home and then count the seconds as my letters slowly appear in sequence), sometimes freezes (when I close an application, the icon becomes faded in the Dash but doesn't disappear, and the application window just stays on the screen but I can't interact with it), and text develops little lines through it after suspend and resume (this was also present in 12.04 and can be fixed with a modification to the xorg.conf... something about debug-wait... but it would be nice if I didn't have to make that change on the whole batch of T43's I'm going to sell). Help appreciated :-) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: No value set for `/apps
[Desktop-packages] [Bug 1070677] Re: Xorg fails to start because of Radeon Issue
This is the dmesg output when the error occurs. (The dmesg from ubuntu-bug is from a successful boot, so this file may be more useful.) ** Attachment added: "fullbaddmesg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1070677/+attachment/3411166/+files/fullbaddmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1070677 Title: Xorg fails to start because of Radeon Issue Status in “xorg” package in Ubuntu: New Bug description: Roughly 30% of the time I boot my system X does not start, instead I boot into a shell. Looking at the Xorg.log I see: [19.593] (EE) RADEON(0): [drm] failed to set drm interface version. [19.593] (EE) RADEON(0): Kernel modesetting setup failed [19.593] (II) UnloadModule: "radeon" [19.593] (II) Unloading radeon [19.593] (EE) Screen(s) found, but none have a usable configuration. [19.593] Fatal server error: [19.593] no screens found ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Oct 24 01:40:51 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] [1002:68d8] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Device [1545:5670] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-33-generic root=UUID=e50fd3cf-9c17-4365-845e-1eb7d14d512e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GMA-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 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 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1070677/+subscriptions -- Mailing list: https://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 1070677] [NEW] Xorg fails to start because of Radeon Issue
Public bug reported: Roughly 30% of the time I boot my system X does not start, instead I boot into a shell. Looking at the Xorg.log I see: [19.593] (EE) RADEON(0): [drm] failed to set drm interface version. [19.593] (EE) RADEON(0): Kernel modesetting setup failed [19.593] (II) UnloadModule: "radeon" [19.593] (II) Unloading radeon [19.593] (EE) Screen(s) found, but none have a usable configuration. [19.593] Fatal server error: [19.593] no screens found ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Oct 24 01:40:51 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] [1002:68d8] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Device [1545:5670] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-33-generic root=UUID=e50fd3cf-9c17-4365-845e-1eb7d14d512e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-880GMA-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 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 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 precise referred-by-support running-unity ubuntu ** Attachment added: "bad Xorg log" https://bugs.launchpad.net/bugs/1070677/+attachment/3411143/+files/fullbadXorg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1070677 Title: Xorg fails to start because of Radeon Issue Status in “xorg” package in Ubuntu: New Bug description: Roughly 30% of the time I boot my system X does not start, instead I boot into a shell. Looking at the Xorg.log I see: [19.593] (EE) RADEON(0): [drm] failed to set drm interface version. [19.593] (EE) RADEON(0): Kernel modesetting setup failed [19.593] (II) UnloadModule: "radeon" [19.593] (II) Unloading radeon [19.593] (EE) Screen(s) found, but none have a usable configuration. [19.593] Fatal server error: [19.593] no screens found ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Oct 24 01:40:51 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] [1002:68d8] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Device [1545:5670] I
[Desktop-packages] [Bug 847001] Re: Adjusting display brightness is very slow on several Dell laptops
Thought I would post a confirmation a HP as well. Dv6t QE 7000 with HD4000+GT650m Optimus and Ubuntu 12.04 x64, this same issues is noticeable from a clean install all the way to installing Bumblebee. Adjusting brightness via the brightness and lock window introduces lag only momentarily and while the brightness is actually changing. Adjusting via the laptop's keyboard has prolonged (10s?) effects on the mouse cursor and delay to the on-screen display pop-up. -- 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/847001 Title: Adjusting display brightness is very slow on several Dell laptops Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: Changing the brightness via FN key combination or via the brightness applet is very slow. the CPUs don't seem to go to 100%, but the adjustment process seems relatively slow. The mouse cursor is also sluggish. Reinstalled the OS twice, but not because of this issue and the problem seems to persist. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-power-manager 2.32.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Sun Sep 11 15:29:02 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) MachineType: Dell Inc. Latitude E5410 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=0dfaacc9-c19d-425b-963d-dabb87ae18bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 05C67D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd01/28/2011:svnDellInc.:pnLatitudeE5410:pvr0001:rvnDellInc.:rn05C67D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/847001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 780117] Re: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04)
> Does that mean you burned an ISO image file from hard disk onto CD ? > (Not composing the CD content from various files on hard disk.) Yes, that's correct. > Could you try for confirmation with any ISO 9660 image file: > > cdrskin -tao padsize=300k -v dev=/dev/sr0 blank=as_needed -eject image.iso Done, worked great. Stdout attached. ** Attachment added: "cdrskin-tao_output" https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/780117/+attachment/3266272/+files/cdrskin-tao_output -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/780117 Title: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04) Status in A disc burning application for gnome 2: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “brasero” package in Ubuntu: In Progress Status in Baltix GNU/Linux: Incomplete Status in “brasero” package in Fedora: New Bug description: Binary package hint: brasero When I burn a DVD (4,7 and 8,5 GB) Brasero show the progressbar till about 30-40% (exact point is randomly) and than says, that it is finalizing the media. This finalizing messages is showing for the rest of the burning process (~10min @8x 8,5GB). After that, it ejects the media without any error. But when I insert the media again, nothing happens, except, that the DVD-Drive disappears from the "computer:///" location in nautilus. This problem only exists when burning On-The-Fly. Burning ISO Images or automatic creation of ISO Images before burning works without problems. The burning speed doesn't matter to this problem. I test 8x, 4x and 2x. All the same problem. On-The-Fly burning using K3B works quite well @8x speed. One thing I also notice is, that Brasero uses 100% CPU on one core, while K3B uses just about 5-15%. I attached the last Brasero log. I don't know, why it just says, that it was only at 49% and then says it's finished. The burning took about 28 minutes. The media was unusable on all my three devices (Linux/Windows). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: brasero 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon May 9 22:10:24 2011 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (brasero:2453): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()' (brasero:2453): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed (:4557): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/780117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 780117] Re: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04)
I'm not sure if my problem was exactly the same bug (Brasero was producing coasters without any errors, but I was burning ISOs, not data CDs), but the patched version in the PPA fixed the problem for me nonetheless. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/780117 Title: Brasero finishes without error but unusable media [on-the-fly mode] (Ubuntu 11.04 ->12.04) Status in A disc burning application for gnome 2: New Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “brasero” package in Ubuntu: In Progress Status in Baltix GNU/Linux: Incomplete Status in “brasero” package in Fedora: New Bug description: Binary package hint: brasero When I burn a DVD (4,7 and 8,5 GB) Brasero show the progressbar till about 30-40% (exact point is randomly) and than says, that it is finalizing the media. This finalizing messages is showing for the rest of the burning process (~10min @8x 8,5GB). After that, it ejects the media without any error. But when I insert the media again, nothing happens, except, that the DVD-Drive disappears from the "computer:///" location in nautilus. This problem only exists when burning On-The-Fly. Burning ISO Images or automatic creation of ISO Images before burning works without problems. The burning speed doesn't matter to this problem. I test 8x, 4x and 2x. All the same problem. On-The-Fly burning using K3B works quite well @8x speed. One thing I also notice is, that Brasero uses 100% CPU on one core, while K3B uses just about 5-15%. I attached the last Brasero log. I don't know, why it just says, that it was only at 49% and then says it's finished. The burning took about 28 minutes. The media was unusable on all my three devices (Linux/Windows). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: brasero 2.32.1-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon May 9 22:10:24 2011 ExecutablePath: /usr/bin/brasero InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (brasero:2453): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()' (brasero:2453): GLib-CRITICAL **: g_variant_get: assertion `valid_format_string (format_string, TRUE, value)' failed (:4557): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/780117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 697279] Re: Jerky playback of mov file in totem
This occurs for me in 12.04 with quicktime videos taken with a Nikon D5100. (The supplied files appears to play okay though, but it's hard to tell because it is so short, my clips are at 30 frames per second vs 24) CPU use goes through the roof. Is this just a bug with ffmpeg not being able to access the graphics card for decoding these files? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/697279 Title: Jerky playback of mov file in totem Status in “gstreamer0.10” package in Ubuntu: Fix Released Status in “vlc” package in Ubuntu: Invalid Bug description: I have some 1080p .mov files recorded on a Nikon D3100 If I try to play these in Totem or VLC playback is jerky/laggy Playback works fine in WMP and Quicktime on Windows Sample file attached. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libgstreamer0.10-0 0.10.28-1 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Jan 4 15:55:22 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/697279/+subscriptions -- Mailing list: https://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 1005636] Re: Amazon store does not open, no streaming internet radio
Actually I don't think the "DAAP Proxy" bit has anything to do with this, but that means that in debug mode, it isn't outputting any errors from the Amazon extension, the only thing it mentions is "[Info 23:21:14.678] AmazonMP3 store redirect URL: https://one.ubuntu.com/music/store/amz/";. Is Banshee using an external browser's engine to load the store? Is it possible that there would be another log somewhere for such an external browser? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1005636 Title: Amazon store does not open, no streaming internet radio Status in “banshee” package in Ubuntu: Confirmed Bug description: 1-Description:Ubuntu 12.04 LTS Release: 12.04 2-banshee: Installed: 2.4.0-2ubuntu1 Candidate: 2.4.0-2ubuntu1 Version table: *** 2.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages 100 /var/lib/dpkg/status 3-Streaming internet radio non responsive 4-Amazon music store Error message: Unable to load page Problem occurred while loading the URL https://one.ubuntu.com/music/store/amz/geo/home/ Cannot resolve proxy hostname () ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: banshee 2.4.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Mon May 28 11:54:31 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1005636/+subscriptions -- Mailing list: https://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 1005636] Re: Amazon store does not open, no streaming internet radio
This bug also effects me. I get the same error message when trying to access the Amazon MP3 store from within Banshee. When I run it in debug mode from the terminal I also see the line "[15 Debug 23:12:15.908] DAAP Proxy listening for connections on port 8089". Why is Banshee trying to use a proxy in the first place? This feature used to work, and I have used it many times before. It must be related to some recent change. ** Changed in: banshee (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1005636 Title: Amazon store does not open, no streaming internet radio Status in “banshee” package in Ubuntu: Confirmed Bug description: 1-Description:Ubuntu 12.04 LTS Release: 12.04 2-banshee: Installed: 2.4.0-2ubuntu1 Candidate: 2.4.0-2ubuntu1 Version table: *** 2.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages 100 /var/lib/dpkg/status 3-Streaming internet radio non responsive 4-Amazon music store Error message: Unable to load page Problem occurred while loading the URL https://one.ubuntu.com/music/store/amz/geo/home/ Cannot resolve proxy hostname () ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: banshee 2.4.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Mon May 28 11:54:31 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: banshee UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1005636/+subscriptions -- Mailing list: https://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 937114] Re: gnome-settings-daemon crashed with signal 5 in g_settings_schema_get_value()
The reason it was doing that was because it was loading a schema from another directory which must have been forgotten about during the upgrade process. I deleted it and I haven't had a problem since. On May 4, 2012 12:30 AM, "Robert Ancell" wrote: > Does this still occur? The stacktrace shows gnome-settings-daemon > trying to access a "screenshot" key which is not in your schema for some > reason (/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins > .media-keys.gschema.xml). > > ** Visibility changed to: Public > > ** Changed in: gnome-settings-daemon (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/937114 > > Title: > gnome-settings-daemon crashed with signal 5 in > g_settings_schema_get_value() > > Status in “gnome-settings-daemon” package in Ubuntu: > Incomplete > > Bug description: > Gnome-settings-daemon crashes on logon every time and causes certain > services to not run. > > ProblemType: Crash > DistroRelease: Ubuntu 12.04 > Package: gnome-settings-daemon 3.3.5-0ubuntu3 > ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 > Uname: Linux 3.2.0-17-generic x86_64 > NonfreeKernelModules: nvidia > ApportVersion: 1.91-0ubuntu1 > Architecture: amd64 > Date: Mon Feb 20 08:50:02 2012 > ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon > ExecutableTimestamp: 1329408875 > InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 > (20110427.1) > ProcCmdline: gnome-settings-daemon > ProcCwd: /home/austin > Signal: 5 > SourcePackage: gnome-settings-daemon > StacktraceTop: > g_settings_schema_get_value (schema=0x1e22a40, key=0x7f67743a27f7 > "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:640 > g_settings_schema_key_init (key=0x7fff8add19d0, schema=0x1e22a40, > name=0x7f67743a27f7 "screenshot") at > /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:751 > g_settings_get_value (settings=0x1f7a4a0, key=0x7f67743a27f7 > "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1059 > g_settings_get_string (settings=, key=) at > /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1539 > ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so > Title: gnome-settings-daemon crashed with signal 5 in > g_settings_schema_get_value() > UpgradeStatus: Upgraded to precise on 2012-02-09 (11 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/937114/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/937114 Title: gnome-settings-daemon crashed with signal 5 in g_settings_schema_get_value() Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: Gnome-settings-daemon crashes on logon every time and causes certain services to not run. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.5-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 20 08:50:02 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1329408875 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcCmdline: gnome-settings-daemon ProcCwd: /home/austin Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: g_settings_schema_get_value (schema=0x1e22a40, key=0x7f67743a27f7 "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:640 g_settings_schema_key_init (key=0x7fff8add19d0, schema=0x1e22a40, name=0x7f67743a27f7 "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettingsschema.c:751 g_settings_get_value (settings=0x1f7a4a0, key=0x7f67743a27f7 "screenshot") at /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1059 g_settings_get_string (settings=, key=) at /build/buildd/glib2.0-2.31.16/./gio/gsettings.c:1539 ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so Title: gnome-settings-daemon crashed with signal 5 in g_settings_schema_get_value() UpgradeStatus: Upgraded to precise on 2012-02-09 (11 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/937114/+subscriptions -- Mailing list: https://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 867682] Re: telepathy-gabble crashed with signal 5 in g_simple_async_result_complete()
Occurred to me on 12.04 beta2 after network connection went down. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/867682 Title: telepathy-gabble crashed with signal 5 in g_simple_async_result_complete() Status in “telepathy-gabble” package in Ubuntu: Confirmed Bug description: empathy crashed once network connection went down ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: telepathy-gabble 0.13.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Tue Oct 4 22:18:37 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/telepathy/telepathy-gabble InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111001) ProcCmdline: /usr/lib/telepathy/telepathy-gabble Signal: 5 SourcePackage: telepathy-gabble StacktraceTop: ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: telepathy-gabble crashed with signal 5 in g_simple_async_result_complete() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/867682/+subscriptions -- Mailing list: https://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 873808] Re: brightness applet needs to support nvidia_backlight
I've installed the latest version of gnome-settings-daemon in precise,
and the new gsd-backlight-helper still prefers the malfunctioning sony
backlight driver to the working nvidia_backlight driver. How does it
determine which driver is the best?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/873808
Title:
brightness applet needs to support nvidia_backlight
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Bug description:
There is a popular third-party backlight driver for Nvidia GPUs that
are not supported by the manufacturers backlight driver, known as
nvidiabl (or nvidia_backlight). See
https://github.com/guillaumezin/nvidiabl for more information. This is
not the same driver as nv_backlight.
In order for this driver to be recognized by the brightness applet,
nvidia_backlight needs to be added to the top of the vendor array in
gsd-backlight-helper so that it looks like this:
/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};
nvidia_backlight needs to be placed at the top of the list because the
non-functioning vendor module (sony, in my case) is still present in
/sys/class/backlight, so nvidia_backlight needs to be recognized
before sony.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/873808/+subscriptions
--
Mailing list: https://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 311911]
Removing deprecated 'All' Platform. -- 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/311911 Title: StartupWMClass does not work for desktop entries Status in Wine: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Bug description: The freedesktop.org desktop entry spec and startup notification spec both describe a line in .desktop files called StartupWMClass that can be used for startup notifications. On at least Ubuntu 8.10, this only works on .desktop entries in menus, not those on the desktop. More details at http://bugs.winehq.org/show_bug.cgi?id=6334#c2 I will most likely be rewriting the startup notification support in Wine to use the full startup notification spec, but some applications still use StartupWMClass, and they will break. My attempts to figure out which Gnome package starts applications from the menus and desktop and how, have been unsuccessful so far. To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/311911/+subscriptions -- Mailing list: https://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 835975] Re: Drag to bookmark in side pane does not work
*** This bug is a duplicate of bug 827049 *** https://bugs.launchpad.net/bugs/827049 This IS NOT a duplicate of 827049. 827409 deals with creating Bookmarks, this deals with how the cannot be used in an expected manor. -- 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/835975 Title: Drag to bookmark in side pane does not work Status in “nautilus” package in Ubuntu: Confirmed Bug description: When I drag drop a file to a bookmarked folder in the side pane, the drag is not accepted and the file stays where it is. Expected it to be moved to the bookmarked folder. * Drag is not accepted, folder does not highlight/select as drag target when the drag icon is over it, releasing the mouse the drag icons floats back to drag start located * The folder in question is "Downloads" which is on the local file system and opens fine when clicked. * Copy pasting with keyboard shortcuts to do the same move works fine. * Drag to a folder in the "Computer" or "Devices" sections of the side pane (E.g. Desktop) is accepted, so issue seems limited to "Bookmarks" section Ubuntu 11.10 alpha -- nautilus 3.1.4 (1:3.1.4-0ubuntu4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/835975/+subscriptions -- Mailing list: https://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 478601] Re: Menu entries in sub-menus cannot be created
Confirmed for Xubuntu 11.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/478601 Title: Menu entries in sub-menus cannot be created Status in “alacarte” package in Ubuntu: Confirmed Bug description: Binary package hint: alacarte Reproduction: 1. Open Alacarte (right-click on Ubuntu-Icon in panel) 2. open a menu entry 3. select a sub-menu 4. create a new menu entry in this sub-menu Result: the new menu entry does not appear in the sub-menu (as expected) but in the parent menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/478601/+subscriptions -- Mailing list: https://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 881523] Re: Buttons in alacarte don't do anything under xfce4
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/881523 Title: Buttons in alacarte don't do anything under xfce4 Status in “alacarte” package in Ubuntu: New Bug description: when trying to use alacarte to edit the system menu under xfce4, none of the buttons other than revert do anything ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alacarte 0.13.2-2ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Oct 25 12:31:28 2011 InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426.1) PackageArchitecture: all ProcEnviron: LC_TIME=mul.UTF-8 PATH=(custom, user) SHELL=/bin/bash LC_NUMERIC=mul.UTF-8 SourcePackage: alacarte UpgradeStatus: Upgraded to oneiric on 2011-10-16 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/881523/+subscriptions -- Mailing list: https://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 881523] [NEW] Buttons in alacarte don't do anything under xfce4
Public bug reported: when trying to use alacarte to edit the system menu under xfce4, none of the buttons other than revert do anything ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alacarte 0.13.2-2ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Oct 25 12:31:28 2011 InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426.1) PackageArchitecture: all ProcEnviron: LC_TIME=mul.UTF-8 PATH=(custom, user) SHELL=/bin/bash LC_NUMERIC=mul.UTF-8 SourcePackage: alacarte UpgradeStatus: Upgraded to oneiric on 2011-10-16 (8 days ago) ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/881523 Title: Buttons in alacarte don't do anything under xfce4 Status in “alacarte” package in Ubuntu: New Bug description: when trying to use alacarte to edit the system menu under xfce4, none of the buttons other than revert do anything ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alacarte 0.13.2-2ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Oct 25 12:31:28 2011 InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426.1) PackageArchitecture: all ProcEnviron: LC_TIME=mul.UTF-8 PATH=(custom, user) SHELL=/bin/bash LC_NUMERIC=mul.UTF-8 SourcePackage: alacarte UpgradeStatus: Upgraded to oneiric on 2011-10-16 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/881523/+subscriptions -- Mailing list: https://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 873808] [NEW] brightness applet needs to support nvidia_backlight
Public bug reported:
There is a popular third-party backlight driver for Nvidia GPUs that are
not supported by the manufacturers backlight driver, known as nvidiabl
(or nvidia_backlight). See https://github.com/guillaumezin/nvidiabl for
more information. This is not the same driver as nv_backlight.
In order for this driver to be recognized by the brightness applet,
nvidia_backlight needs to be added to the top of the vendor array in
gsd-backlight-helper so that it looks like this:
/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};
nvidia_backlight needs to be placed at the top of the list because the
non-functioning vendor module (sony, in my case) is still present in
/sys/class/backlight, so nvidia_backlight needs to be recognized before
sony.
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/873808
Title:
brightness applet needs to support nvidia_backlight
Status in “gnome-settings-daemon” package in Ubuntu:
New
Bug description:
There is a popular third-party backlight driver for Nvidia GPUs that
are not supported by the manufacturers backlight driver, known as
nvidiabl (or nvidia_backlight). See
https://github.com/guillaumezin/nvidiabl for more information. This is
not the same driver as nv_backlight.
In order for this driver to be recognized by the brightness applet,
nvidia_backlight needs to be added to the top of the vendor array in
gsd-backlight-helper so that it looks like this:
/* available kernel interfaces in priority order */
static const gchar *backlight_interfaces[] = {
"nvidia_backlight",
"nv_backlight",
"asus_laptop",
"toshiba",
"eeepc",
"thinkpad_screen",
"acpi_video1",
"mbp_backlight",
"acpi_video0",
"fujitsu-laptop",
"sony",
"samsung",
NULL,
};
nvidia_backlight needs to be placed at the top of the list because the
non-functioning vendor module (sony, in my case) is still present in
/sys/class/backlight, so nvidia_backlight needs to be recognized
before sony.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/873808/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
