[Desktop-packages] [Bug 1929305] [NEW] [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all
Public bug reported: Inserting a headset jack is detected. I can slide the volume. But no sound at all in the headset. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 22 21:46:36 2021 InstallationDate: Installed on 2021-05-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Audio interne - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.release: 11.40 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 11.40 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB3E1E dmi.product.sku: N/A dmi.product.version: C606TWY5 dmi.sys.vendor: Sony Corporation ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1929305 Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Inserting a headset jack is detected. I can slide the volume. But no sound at all in the headset. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 22 21:46:36 2021 InstallationDate: Installed on 2021-05-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Audio interne - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.release: 11.40 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 11.40 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB3E1E dmi.product.sku: N/A dmi.product.version: C606TWY5 dmi.sys.vendor: Sony Corporation To manage notifications about this
[Desktop-packages] [Bug 1795808] [NEW] Xorg freeze
Public bug reported: Hi, Since the installation of Ubuntu 18.10, I get the login screen but once logged in I get a black screen. It happens only with the proprietary nvidia driver 390. If I remove the nvidia driver to use nouveau, it works. My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] So the automatic report in attachement will show you no nvidia driver installed. It's because I am doing this bug report after removing the nvidia driver to be able to get a desktop. In attachement I add the journalctl of the preview boot which failed with nvidia driver. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 3 09:19:03 2018 DistUpgraded: 2018-10-03 00:59:01,660 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070 Ti] [1043:8620] InstallationDate: Installed on 2017-09-17 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-8-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-02 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Wed Oct 3 09:03:39 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu ** Attachment added: "journalctl.failed_screen_nvidia.log" https://bugs.launchpad.net/bugs/1795808/+attachment/5196411/+files/journalctl.failed_screen_nvidia.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/1795808 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hi, Since the installation of Ubuntu 18.10, I get the login screen but once logged in I get a black screen. It happens only with the proprietary nvidia driver 390. If I remove the nvidia driver to use nouveau, it works. My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] So the automatic report in attachement will show you no nvidia driver installed. It's because I am doing this bug report after removing the nvidia driver to be able to get a desktop. In attachement I add the journalctl of the preview boot which failed with nvidia driver. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64
[Desktop-packages] [Bug 1725949] [NEW] nouveau drivers fails to start a wayland session and fallback to x11
Public bug reported: I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a unusual long time then finally shows me gdm3 and everything is working after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I can see that after multiple failures to launch wayland, it falls back to X11. I added an attachement of journalctl -b -1 where it fails with nouveau (I'm filling the bug after reinstalling nvidia proprietary driver). lspci -v 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f600 (32-bit, non-prefetchable) [size=16M] Memory at e800 (64-bit, prefetchable) [size=128M] Memory at f000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: automatic crash report generation. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 11:37:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] [3842:2678] InstallationDate: Installed on 2017-09-17 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Oct 22 11:26:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Attachment added: "nouveau-fails-wayland.log"
[Desktop-packages] [Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
Hey guys, go to the mentionned link : https://bugs.launchpad.net/hundredpapercuts/+bug/1296895 And click on the top of the page to say it also affects you: This bug affects you and 2 other people. I'm also hit by the bug although I'm on a TOWER and have no battery in it ... -- 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/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! As suggested by the upstream Gnome bug report, this is an issue pertaining to Ubuntu's lack of systemd integration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 893031] Re: Empathy is not working behind the proxy servers SINCE Ubuntu 11.10
I'm so surprised that nobody from the UBUNTU team can't take care of this problem which is: - old - confirmed - should be a staple feature of any OS Probably that you are busy working on mobile features that nobody use? I'm sorry, I love free softwares, but sometimes, it is really frustrating. Nicolas -- 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/893031 Title: Empathy is not working behind the proxy servers SINCE Ubuntu 11.10 Status in Jabber/XMPP connection manager: Unknown Status in “libproxy” package in Ubuntu: Fix Released Status in “telepathy-gabble” package in Ubuntu: Confirmed Status in “libproxy” source package in Precise: Fix Released Status in “telepathy-gabble” source package in Precise: Confirmed Bug description: Empathy is unable to connect behind the proxy servers whatever way we try. It doesn't utilize the proxy settings given globally to the system. There is no proxy option in the program also. I tried connecting to empathy from Ubuntu 11.10 in three systems behind a proxy server and in all cases it failed. I tried all of the following but none worked: 1. Changing settings with gconf-editor ( Walk down the tree to system - http_proxy . Search for use_http_proxy and check it. ) Even after doing that there is no change in behaviour of empathy 2. gksudo gedit /etc/bash.bashrc export http_proxy=http://proxyhost:port/ export ftp_proxy=http://proxyhost:port/ save and exit This also didnt help anything 3. Using tsocks and editing its config files also. In that case the result was: tsocks dbus-launch empathy fails to retrieve the accounts list. tsocks empathy launches empathy, but it is unable to connect.. Please generate a patch for this problem and release new version of the program. To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/893031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
