[Desktop-packages] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c
I'm wondering if the anti-aliasing mode is a bit of a red hearing here, or only partially related. In my case, the app that triggers this is CLion 2023.3. Except in my case, I can reproduce it consistently simply by *changing* the anti-aliasing setting between subpixel and grayscale (in *either* direction) and clicking "apply." But once I log back in and re-launch the app, the system works fine and doesn't crash (regardless of the setting). Outside of that action, the bug behaves more like a time-bomb. There seems to be like a 5% chance that clicking the "debug" icon in the toolbar will take down my X session. Most of the time it works fine, until it doesn't. -- 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/2060354 Title: Segfaults and assertion failures in Xorg's render/glyph.c Status in xorg-server package in Ubuntu: Confirmed Bug description: I just upgraded xserver-xorg-core and xserver-common to 2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate EAP (downloaded from JerBrains website) Xorg server crashes with segfault: X.Org X Server 1.21.1.4 X Protocol Version 11, Revision 0 Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 #0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr 4 20:28:35 UTC x86_64 Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 6 15:28:18 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" malloc(): unaligned tcache chunk detected (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc] (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d] (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7ec01c429d90] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7ec01c429e40] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605] (EE) (EE) Fatal server error: (EE) Caught signal 6 (Aborted). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch (EE) Server terminated with error (1). Closing log file. Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like security backports were done incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions -- Mailing list: https://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 1841354] Re: Show a "Confirm" dialog window when deleting files
I'm aware this is a very dated thread, but I absolutely agree with Greg here. As a plasma user making my way to Gnome, I don't expect the full customization that I'm accustomed to; however philosophical ideologies taking a toggle for something like this seems a bit ridiculous and overstepping. -- 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/1841354 Title: Show a "Confirm" dialog window when deleting files Status in nautilus package in Ubuntu: Opinion Bug description: Currently files are deleted instantly when pressing "Del" key. I need a confirmation dialog window. "yes/no" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1841354/+subscriptions -- Mailing list: https://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 1712279] Re: Can't add google account, shows "credentials have expired"
I had this problem in Mint, and what I found is that if there is a conflicting Google account signed in on Chrome (in my case) it won't work. I had to log out of that other account, and it began working. So it seems (as mentioned somewhat, above) that it is very dependent on what you are signed in on with your browser. I run a 2nd Google account out of Chrome for work, and use Brave for my main Google browser -- so each browser uses a different account. Had to switch both to the same that I wanted Gnome to use (although I suspect the only one it really needed to be signed in the same with was Chrome). -- 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/1712279 Title: Can't add google account, shows "credentials have expired" Status in gnome-control-center package in Ubuntu: Invalid Bug description: In Artful, when I try to add my google account, it seems to log in fine. When I have gone through all steps and view the online accounts, the dialog says "credentials have expired". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 09:27:59 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-24 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1712279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Jay, a belated thank-you for that link! It's now a much nicer option until the fix rolls out to regular users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I experience this bug under Wayland in Pop!_OS 21.04, which uses a custom fork of Dash to Dock (Cosmic Dock).[*] I found a clunky workaround: * Select File -> Send Later (ctl-shift-enter): message is saved to Outbox. * Select File -> Send Unsent Messages. This method does not create a "ghost window". But it's nearly as annoying as the bug itself. I had to remove the "Send" button from the Composition toolbar to keep me from reflexively clicking it. (I should really just switch TB to run under Xwayland, but I'm pigheaded.) [*] https://github.com/pop-os/cosmic-dock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Following instructions at: https://wiki.ubuntu.com/DebuggingSoundProblems ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Tags added: kernel-sound ** Description changed: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - - Booting windows first and then rebooting to Ubuntu = sound works fine - - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it + - Booting Windows first and then rebooting to Ubuntu -> sound works fine + - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 - aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] - Subdevices: 1/1 - Subdevice #0: subdevice #0 + Subdevices: 1/1 + Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: derek 1460 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: derek 1460 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Incomplete Bug description: Th
[Desktop-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Adding the alsainfo_good attachment ** Attachment added: "alsainfo_good.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+attachment/5460962/+files/alsainfo_good.txt -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in alsa-driver package in Ubuntu: New Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting windows first and then rebooting to Ubuntu = sound works fine - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+subscriptions -- Mailing list: https://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 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Have collected alsa-info output from non-working and working situations as per the notes at https://bugzilla.kernel.org/show_bug.cgi?id=195457#c11 echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef sudo alsa-info --no-upload --output /home/derek/alsainfo_bad.txt ** Bug watch added: Linux Kernel Bug Tracker #195457 https://bugzilla.kernel.org/show_bug.cgi?id=195457 ** Attachment added: "alsainfo run when sound not working" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+attachment/5460961/+files/alsainfo_bad.txt -- 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in alsa-driver package in Ubuntu: New Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting windows first and then rebooting to Ubuntu = sound works fine - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packa
[Desktop-packages] [Bug 1914881] [NEW] No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Public bug reported: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting windows first and then rebooting to Ubuntu = sound works fine - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description:Ubuntu 20.10 Release:20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in alsa-driver package in Ubuntu: New Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting windows first and then rebooting to Ubuntu = sound works fine - Booting Ubuntu first and then rebooting to Windows - Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices
[Desktop-packages] [Bug 73536]
Once upon a time Firefox had -remote for executing commands on linux like that, but it was removed back in Firefox 39. This also allowed doing useful stuff like telling firefox to reload a url. but also: -remote "xfeDoCommand(close)" Regrettably there's no replacement for this super useful legacy functionality that I know of apart from Selenium Webdriver (have fun) or xdotool scripting. Of those options, xdotool sending commands to window with Firefox name to ctrl-q is probably sanest, with possible confirmation prompt handling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/73536 Title: MASTER Firefox crashes on instant X server shutdown Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Triaged Bug description: Firefox crashes when X server is forcefully torn down (e.g. by pressing ctrl-alt-backspace) and a crash report gets generated on next login. (Original Report: I've reproduced it once on my machine with the following steps. With, oh, about 5 tabs open, I just pressed ctrl-alt-backspace, logged back in when the X server restarted, and FF crashed with a bug report when Gnome tried to restore the session. It's not terribly important, I don't think anyone does this very often, but maybe it'll be helpful. ) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73536/+subscriptions -- Mailing list: https://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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
Old issue, but they reported that by making it visible, then connecting and setting it to auto-connect, then making it hidden again fixes the issue. I haven't tried. https://forums.linuxmint.com/viewtopic.php?t=221456#p1168174 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1542733/+subscriptions -- Mailing list: https://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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
Another from 2014: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1316634 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1542733/+subscriptions -- Mailing list: https://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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
Could this be the reason why my hidden network takes several minutes to auto-connect after a boot? I can actually open the menus and manually connect *well* before the auto-connect bothers to trigger. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in Network Manager Applet: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1542733/+subscriptions -- Mailing list: https://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 1821936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250292/+files/ProcCpuinfoMinimal.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.
[Desktop-packages] [Bug 1821936] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250291/+files/ProcCpuinfo.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.ven
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
I did this yesterday per request and marked it as confirmed. I just completed this for a second time agreeing to send some data which mentioned pulse-audio, etc., to you all. It completed at 16:39 local time, Miami. -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.nam
[Desktop-packages] [Bug 1821936] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250297/+files/WifiSyslog.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.ven
[Desktop-packages] [Bug 1821936] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250295/+files/RfKill.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor:
[Desktop-packages] [Bug 1821936] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250296/+files/UdevDb.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor:
[Desktop-packages] [Bug 1821936] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250294/+files/ProcModules.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.ven
[Desktop-packages] [Bug 1821936] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250293/+files/ProcInterrupts.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi
[Desktop-packages] [Bug 1821936] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250290/+files/Lsusb.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK
[Desktop-packages] [Bug 1821936] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250287/+files/CurrentDmesg.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi
[Desktop-packages] [Bug 1821936] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250288/+files/IwConfig.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor:
[Desktop-packages] [Bug 1821936] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250289/+files/Lspci.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK
[Desktop-packages] [Bug 1821936] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250286/+files/CRDA.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
apport information ** Tags added: apport-collected bionic ** Description changed: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gdm1903 F pulseaudio + derek 2464 F pulseaudio + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-03-23 (5 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash + ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.18.0-16-generic N/A + linux-backports-modules-4.18.0-16-generic N/A + linux-firmware 1.173.3 + Tags: bionic + Uname: Linux 4.18.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/26/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: Z272SD.300 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: Z272SD + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 13 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: + dmi.product.family: Zen AIO + dmi.product.name: Zen AIO 27 Z272SD_Z272SD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821936/+attachment/5250285/+files/AlsaInfo.txt -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver pa
[Desktop-packages] [Bug 1821936] Re: ALC274 unsupported
See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485 It references another Linux variant (eww). But, reading their thread you will find that they made a patch in December 2018 to solve the 294 issue. Then, the bug report for Ubuntu let to y'all doing the same. I've done all the same steps mentioned in both threads. It appears that the same patch is needed for ACL274. Post 28 from December 2018, https://forum.manjaro.org/t/alc294-analog- audio-card-detected-but-no-sound-internaly-or-headphones/54089/28, states: "each one of ASUS new laptop models with Realtek ALC294 have individual hwinfo SubVendor and SubDevice values. They are needed for QUIRK hack directly in /sound/pci/hda/patch_realtek.c file." Additionally, it includes 3 patches for the kernel regarding realtek.c. This makes sense since all other methods to resolve fail. So, what commands should I run to get you all that data to solve this matter? :-) -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://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 1821936] Re: ALC274 unsupported
No, my point is that I tried other kernel versions to see if it was patched. No kernel world with ACL274 on this machine. Windows works great. 4.18, installed with Ubuntu 18.04.2, to 5.0 were tested with the same results. The issue persists. Sorry for the confusion. How do I get this to stop being incomplete? -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://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 1821936] Re: ALC274 unsupported
Apologies my first run of apport was mainline 5.0. I immediately rebooted and use a standard default kernel for 18.04. I deleted both mainlines since they didn't solve my issue anyway. -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://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 1821936] Re: ALC274 unsupported
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://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 1821936] Re: ALC274 unsupported
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821936/+subscriptions -- Mailing list: https://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 1821936] [NEW] ALC274 unsupported
Public bug reported: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alc274 audio driver kernel -- 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/1821936 Title: ALC274 unsupported Status in alsa-driver package in Ubuntu: New Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown To manage notifications about this b
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
I don't see a "Closed" status. The closest thing I see to make it go away is "Invalid", but I would say that you can close it, unless the thing to do is add Crash to the config by default so it isn't a manual step. -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subsc
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
Adding Crash to the config file seems to have done the trick. -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
>From that bug report I followed this step: "It works to edit /etc/apport/crashdb.conf and add 'Crash' to the 'problem_types': ['Bug', 'Package', 'Crash'], or to make that change in a separate file and run". So I'll see how that fares. -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-serv
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
Output of ls -l total 2320 -rw-r- 1 root whoopsie 2373147 Feb 1 13:35 _usr_lib_xorg_Xorg.0.crash -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
1. I'm not sure what you mean by the ID of the bug. The file is owned by root, group whoopsie 2. The contents of the file whoopsie-id are: ad2a60d37ef07a75f5bb69241962893c2ee51bf68be6d93a3b37992aaf2d45370ac7a5094e472b57985c4979bd5355af775f1d483c51977972fa4f743003d70c 3. didn't do this part -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug
[Desktop-packages] [Bug 1814174] [NEW] Xorg crash report after resume
Public bug reported: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1814174 Title: Xorg crash report after resume Status in xorg package in Ubuntu: New Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bio
[Desktop-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
The message is emitted by glib: https://gitlab.gnome.org/GNOME/glib/commit/a919be3d39150328874ff647fb2c2be7af3df996 The commit log description is: "gmain: Warn when g_source_remove() fails". So why is it calling g_critical() instead of g_warning()? Obviously, it's not a critical error, if people are able to live with these annoying messages for five years with no obvious ill effects. Critical errors are often routed to /dev/console, and it's clearly inappropriate to escalate these messages that high. -- 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/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in notification-daemon: New Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-mplayer package in Ubuntu: Confirmed Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- Mailing list: https://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 955327] Re: Spell-check keeps setting itself to Australia (en_au).
This can be closed. On Tue, Aug 28, 2018, 8:35 AM Paul White <955...@bugs.launchpad.net> wrote: > Derek (and anyone else affected), > > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu and Firefox since that time. > > Do you still see a problem related to the one that you reported? Please > let us know if you do. > > If we do not hear from you this bug report will expire in approximately > 60 days time. > > Thank you for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: firefox (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/955327 > > Title: > Spell-check keeps setting itself to Australia (en_au). > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > Summary says it all. I frequently have to change spell-check languge > from australia to us, over and over. I don't even know why au is > installed... > > ProblemType: Bug > DistroRelease: Ubuntu 10.10 > Package: firefox 10.0.2+build1-0ubuntu0.10.10.1 > ProcVersionSignature: Ubuntu 2.6.35-32.66-generic 2.6.35.14 > Uname: Linux 2.6.35-32-generic x86_64 > NonfreeKernelModules: fglrx > AddonCompatCheckDisabled: False > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. > Architecture: amd64 > ArecordDevices: > List of CAPTURE Hardware Devices >card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] > Subdevices: 2/2 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: derek 1960 F pulseaudio > BuildID: 20120216081259 > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'SB'/'HDA ATI SB at 0xf050 irq 16' > Mixer name : 'IDT 92HD81B1X5' > Components : 'HDA:111d7605,103c1697,00100105' > Controls : 18 > Simple ctrls : 12 > Card1.Amixer.info: >Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf041 irq 19' > Mixer name : 'ATI RS690/780 HDMI' > Components : 'HDA:1002791a,00791a00,0010' > Controls : 4 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined penum > Playback channels: Mono > Mono: Playback [on] > Channel: release > Date: Wed Mar 14 14:17:09 2012 > EcryptfsInUse: Yes > EtcFirefoxSyspref: Cannot parse /etc/firefox/syspref.js - [Errno 2] No > such file or directory: '/etc/firefox/syspref.js' > ForcedLayersAccel: False > IfupdownConfig: >auto lo >iface lo inet loopback > IncompatibleExtensions: LastPass - ID=supp...@lastpass.com, > Version=1.90.6, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, > Type=extension, Active=Yes > InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 > (20101007) > IpRoute: >192.168.2.0/26 dev wlan0 proto kernel scope link src 192.168.2.47 > metric 2 >169.254.0.0/16 dev wlan0 scope link metric 1000 >default via 192.168.2.1 dev wlan0 proto static > ProcEnviron: >LANG=en_US.utf8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216081259 > (Running) > RunningIncompatibleAddons: True > SourcePackage: firefox > dmi.bios.date: 07/01/2011 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.25 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 1697 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: KBC Version 16.24 > dmi.chassis.asset.tag: CNU1082GRY > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.25:bd07/01/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059A1020461020100:rvnHewlett-Packard:rn1697:rvrKBCVersion16.24:cvnHewlett-Packard:ct10:cvrN/A: > dmi.product.name: HP Pavilion g6 Notebook PC > dmi.product.version: 059A1020461020100 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/955327/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in U
Re: [Desktop-packages] [Bug 946792] Re: Downloads window looses all window decorations when restored via add-on toolbar button.
This can be closed. On Mon, Aug 20, 2018, 11:25 AM Paul White <946...@bugs.launchpad.net> wrote: > Derek, > > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu and Firefox since that time. > > Do you still see a problem related to the one that you reported? Please > let us know if you do. > > If we do not hear from you this bug report will close in approximately > 60 days time. > > Thank you for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: firefox (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/946792 > > Title: > Downloads window looses all window decorations when restored via add- > on toolbar button. > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > Have "Downloads" icon in add-on toolbar at bottom of window. > Open and minimize "Downloads" window. > Click "Downloads" icon in add-on toolbar. > > Expect to happen: > Downloads window re-appears in same place it was before being > minimized and with window decorations intact. > > What happens intead: > Downloads window appears at the top-left of screen and has no window > decorations. Cannot be moved with Alt+Mouse1. Can only be closed using > dock/task manager. > > > Only tested in Gnome Classic session. > > ProblemType: Bug > DistroRelease: Ubuntu 11.10 > Package: firefox 10.0.2+build1-0ubuntu0.11.10.1 > ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 > Uname: Linux 3.0.0-16-generic x86_64 > NonfreeKernelModules: fglrx > AddonCompatCheckDisabled: False > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. > ApportVersion: 1.23-0ubuntu4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: derek 2148 F pulseaudio > BuildID: 20120216115113 > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' > Mixer name : 'Realtek ALC888' > Components : 'HDA:10ec0888,1458a002,0011' > Controls : 38 > Simple ctrls : 21 > Card1.Amixer.info: >Card hw:1 'Generic'/'HD-Audio Generic at 0xfdefc000 irq 49' > Mixer name : 'ATI R6xx HDMI' > Components : 'HDA:1002aa01,00aa0100,00100200' > Controls : 4 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined penum > Playback channels: Mono > Mono: Playback [on] > Channel: release > CheckboxSubmission: 880f1cef728a67d1a58407cc143447d4 > CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 > Date: Sun Mar 4 20:50:06 2012 > ForcedLayersAccel: False > IfupdownConfig: >auto lo >iface lo inet loopback > IncompatibleExtensions: >LastPass - ID=supp...@lastpass.com, Version=1.90.0, minVersion=1.9a2, > maxVersion=1.9.6, Location=app-profile, Type=extension, Active=Yes >Selenium IDE: Perl Formatter - ID=perlformatt...@seleniumhq.org, > Version=1.0.1, minVersion=3.0, maxVersion=5.0.*, Location=app-profile, > Type=extension, Active=Yes >Selenium IDE: PHP Formatters - ID=phpformatt...@seleniumhq.org, > Version=1.0.2, minVersion=3.0, maxVersion=5.0.*, Location=app-profile, > Type=extension, Active=Yes > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) > IpRoute: >default via 10.10.10.1 dev eth0 proto static >10.10.10.0/26 dev eth0 proto kernel scope link src 10.10.10.10 > metric 1 >169.254.0.0/16 dev eth0 scope link metric 1000 > IwConfig: >lono wireless extensions. > >eth0 no wireless extensions. > >vboxnet0 no wireless extensions. > Profiles: Profile0 (Default) - LastVersion=10.0.2/20120216115113 > (Running) > RfKill: > > RunningIncompatibleAddons: True > SourcePackage: firefox > UpgradeStatus: Upgraded to oneiric on 2011-11-04 (121 days ago) > dmi.bios.date: 01/06/2010 > dmi.bios.vendor: Award Software International, Inc. > dmi.bios.version: F1 > dmi.board.name: GA-770T-USB3 > 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: > d
[Desktop-packages] [Bug 1244369] Re: Keeps pausing for ages whilst downloading IMAP
Hi Paul Please close this report. You are quite correct that it doesn't relate to Ubuntu. I obviously didn't realise this wasn't a general Thunderbird forum. Regards Derek -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1244369 Title: Keeps pausing for ages whilst downloading IMAP Status in thunderbird package in Ubuntu: Incomplete Bug description: Running 24.0.1 on Windows 7 x64 Ultimate. I'm trying to download my brother's Hotmail e-mai for him, so that I can then copy it to the Local folders as an offline backup. However, it's taking ages because TB keeps pausing for ages and no apparent reason. My brother has a number of folders for his e-mail on Hotmail and for example, on the folder 2009 it stopped for several minutes at 144 out of 272. Then it get to 153 and paused again for several minutes, then it went to 269 and paused again for several minutes. It's probably taken at least 15 minutes so far just to do that one folder. When it got to 272 out of 272, it again paused for ages and then when it had finished, just didn't do anything for a while. Now it's start on the folder "2010" and has got to 14 out of 1420 and paused again. When it's paused, Task Manager shows that TB is not doing anything. Under Account Settings I have "Keep messages for this account on the computer" and have all his folders except for Deleted ticked. However, if I right-click on the Account in the main window and select Subscribe, it shows all the folders, including Deleted, ticked so obviously these settings are for different uses. If I disable "Keep messages" and then drag each IMAP folder to Local Folders to copy it, it doesn't seem to pause and although slow (no doubt a limitation of IMAP) it steadily downloads the messages and Task Manager shows around 2-3% CPU. However, if I drag multiple folders to copy instead of a single one, it does seem to start pausing quite often again, even though it's only copying one folder at a time, perhaps the others being queued triggers the problem. Actually, I just tried again only dragging one of the folders "Newsletters", which was the first one it was copying when dragging multiple folders and that's having problems, currently paused at 41 out of 151. Several of the folders I'd copied previous to this one had the same amount of e-mails and didn't pause, so it doesn't appear to be the number of e-mails in a folder that's the issue. Testing on my own system the other day, with both Hotmail and Gmail accounts, I found that when copying the mail from the IMAP folders to the Local Folders, it appeared to be downloading it all again, despite it already being stored on my PC, which doesn't seem right. It also seemed to make no difference to the size of the TB data files when disabling "Keep messages for this account on the computer" with Inbox being around 600MB and Sent around 550MB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1244369/+subscriptions -- Mailing list: https://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 1726643] Re: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory)
Upstream bug link:- https://gitlab.gnome.org/GNOME/nautilus/issues/335 On 26/03/18 16:15, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. The issue you are reporting is an upstream one and it > would be nice if somebody having it could send the bug to the developers > of the software by following the instructions at > https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please > tell us the number of the upstream bug (or the link), so we can add a > bugwatch that will inform us about its status. Thanks in advance. > -- 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/1726643 Title: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory) Status in nautilus package in Ubuntu: New Bug description: Moved 1.2GB .mp4 from Desktop to Home. Nautilus crashed (apparently after the move was complete) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 24 01:00:40 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-02 (82 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcCmdline: /usr/bin/nautilus file:///home/username ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_directory_async_state_changed () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726643/+subscriptions -- Mailing list: https://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 1220764] Re: Rhythmbox does not add VBR headers when ripping CDs to MP3
This problem still occurs in 17.10. I just ripped a kids music disc via
Rhythmbox using MP3 default settings (=VBR/medium). Files are perceived
(by RB and nautilus) as 32Kbps:
% file 19\ -\ Five\ Days\ Old.mp3
19 - Five Days Old.mp3: Audio file with ID3 version 2.3.0, contains:MPEG ADTS,
layer III, v1, 32 kbps, 44.1 kHz, JntStereo
% mp3val 19\ -\ Five\ Days\ Old.mp3
Analyzing file "19 - Five Days Old.mp3"...
WARNING: "/home/ddl/Music/Laurie Berkner/Lullabies/19 - Five Days Old.mp3": VBR
detected, but no VBR header is present. Seeking may not work properly.
INFO: "/home/ddl/Music/Laurie Berkner/Lullabies/19 - Five Days Old.mp3": 7087
MPEG frames (MPEG 1 Layer III), +ID3v2, no VBR header
I can partly "fix" file metadata (via vbrfix and mp3val -f), but
nautilus and RB then display bitrate as "unknown".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1220764
Title:
Rhythmbox does not add VBR headers when ripping CDs to MP3
Status in rhythmbox package in Ubuntu:
Confirmed
Bug description:
When ripping CDs to MP3 using Rhythmbox, by default they are VBR,
because this is the default preset that is used in
/usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs (cbr=false). The
problem is that the VBR headers aren't added to the MP3 files, for
example:
$ mp3val 01\ -\ Gregory\ Alan\ Isakov\ -\ Dandelion\ Wine.mp3
Analyzing file "01 - Gregory Alan Isakov - Dandelion Wine.mp3"...
WARNING: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": VBR detected, but no
VBR header is present. Seeking may not work properly.
INFO: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": 9559 MPEG frames
(MPEG 1 Layer III), +ID3v2, no VBR header
Done!
This causes most programs to report incorrect track lengths, including
Rhythmbox itself and Ubuntu's default Nautilus file manager. This
seems to be a huge oversight considering this is the default behavior
using the default apps. I'm not sure when this started because I only
use the LTS versions of Ubuntu, but I know it wasn't a problem in
10.04, because it was using a gstreamer pipeline with xingmux as
opposed to gstreamer presets, which from what I understand don't
support xingmux (which I believe adds the VBR headers).
I currently have to fix any MP3s that I generate with Rhythmbox like
so:
sudo apt-get install vbrfix
cd /path/to/mp3s
find . -type f -iname '*.mp3' -exec vbrfix {} {} \;
rm vbrfix.log vbrfix.tmp
This bug is related to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/945987
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rhythmbox-data 2.96-0ubuntu4.3 [modified:
usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs
usr/share/rhythmbox/rhythmbox.gep]
ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
Uname: Linux 3.5.0-39-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Wed Sep 4 09:54:54 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-07-09 (12 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: rhythmbox 3.0.2-0ubuntu2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Tags: trusty
Uname: Linux 3.13.0-32-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/rhythmbox/+bug/1220764/+subscriptions
--
Mailing list: https://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 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
Is an SRU fixing this likely to get pushed to artful? It bites me several times a week (it's filling my syslog with errors as I write this). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Invalid Status in snapd-glib package in Ubuntu: In Progress Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions -- Mailing list: https://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 1720725] [NEW] Enable multiarch in libsndfile1-dev
Public bug reported: Release: Artful Aardvark 17.10 Package version: 1.0.28-4 The current version of libsndfile1-dev is not able to be marked Multi- Arch: same, because the examples it provides includes an autoheader (?) generated config.h file, which has architecture-specific defines like SIZEOF_INT. However, as far as I can tell, this header, as well as common.h and sfconfig.h aren't actually used in any of the examples, despite being included sometimes. So if they were removed, it should be possible to mark the dev package as Multi-Arch: same. I was able to install both amd64 and i386 versions of libsndfile1-dev after removing the examples. For a more long-term solution, the header includes in debian/libsndfile1-dev.examples can probably be removed once those extra includes are removed. A change on the github repo for libsndfile was recently merged to get rid of the extra includes, as it's also probably a bad idea to (unnecessarily) include internal header files in example code. ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1720725 Title: Enable multiarch in libsndfile1-dev Status in libsndfile package in Ubuntu: New Bug description: Release: Artful Aardvark 17.10 Package version: 1.0.28-4 The current version of libsndfile1-dev is not able to be marked Multi- Arch: same, because the examples it provides includes an autoheader (?) generated config.h file, which has architecture-specific defines like SIZEOF_INT. However, as far as I can tell, this header, as well as common.h and sfconfig.h aren't actually used in any of the examples, despite being included sometimes. So if they were removed, it should be possible to mark the dev package as Multi-Arch: same. I was able to install both amd64 and i386 versions of libsndfile1-dev after removing the examples. For a more long-term solution, the header includes in debian/libsndfile1-dev.examples can probably be removed once those extra includes are removed. A change on the github repo for libsndfile was recently merged to get rid of the extra includes, as it's also probably a bad idea to (unnecessarily) include internal header files in example code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1720725/+subscriptions -- Mailing list: https://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 1720723] [NEW] Add multiarch metadata to gir1.2-gstreamer-1.0
Public bug reported: Release: Artful Aardvark 17.10 Package version: 1.12.3-1 I modified the debian/gir1.2-gstreamer-1.0.install file to put its girepository-1.0 files under the architecture-dependent directory, by removing the target specifier (usr/lib). As far as I can tell, the non- architecture specific files are just doc files, and should be the same on other architectures. I then successfully installed the modified package and imported Gst using python3-gi. Changing the install directory plus adding Multi-Arch: same to gir1.2-gstreamer-1.0 should make it multiarch-compatible. It's also likely that libgstreamer1.0-dev could also be Multi-Arch: same if it weren't for the binaries in the package, although I don't know an easy solution to that - for instance gst-codec-info-1.0 loads plugins dynamically, which fails (with an accurate warning message) if used on the wrong architecture. Renaming it/giving it an architecture-dependent path (e.g. x86_64-linux-gnu-gcc) would probably break backwards compatibility, and there are about 20 rdepends for libgstreamer1.0-dev, which as gst-codec-info-1.0 and dh_gstscancodecs seem designed for use by packagers are probably the only places to check for usage. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720723 Title: Add multiarch metadata to gir1.2-gstreamer-1.0 Status in gstreamer1.0 package in Ubuntu: New Bug description: Release: Artful Aardvark 17.10 Package version: 1.12.3-1 I modified the debian/gir1.2-gstreamer-1.0.install file to put its girepository-1.0 files under the architecture-dependent directory, by removing the target specifier (usr/lib). As far as I can tell, the non-architecture specific files are just doc files, and should be the same on other architectures. I then successfully installed the modified package and imported Gst using python3-gi. Changing the install directory plus adding Multi-Arch: same to gir1.2-gstreamer-1.0 should make it multiarch-compatible. It's also likely that libgstreamer1.0-dev could also be Multi-Arch: same if it weren't for the binaries in the package, although I don't know an easy solution to that - for instance gst-codec-info-1.0 loads plugins dynamically, which fails (with an accurate warning message) if used on the wrong architecture. Renaming it/giving it an architecture- dependent path (e.g. x86_64-linux-gnu-gcc) would probably break backwards compatibility, and there are about 20 rdepends for libgstreamer1.0-dev, which as gst-codec-info-1.0 and dh_gstscancodecs seem designed for use by packagers are probably the only places to check for usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1720723/+subscriptions -- Mailing list: https://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 1720701] [NEW] Add multiarch metadata to libpixman-1-dev
Public bug reported: Release: Artful Aardvark 17.10 Package version: 0.34.0-1 After modifying libpixman-1-dev to be Multi-Arch: same, and checking that it installs architecture-specific files appropriately, and successfully building and installing both the amd64 and i386 versions simultaneously, it seems like libpixman-1-dev can be upgraded to get multiarch support fairly easily. ** Affects: pixman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/1720701 Title: Add multiarch metadata to libpixman-1-dev Status in pixman package in Ubuntu: New Bug description: Release: Artful Aardvark 17.10 Package version: 0.34.0-1 After modifying libpixman-1-dev to be Multi-Arch: same, and checking that it installs architecture-specific files appropriately, and successfully building and installing both the amd64 and i386 versions simultaneously, it seems like libpixman-1-dev can be upgraded to get multiarch support fairly easily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1720701/+subscriptions -- Mailing list: https://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 1720692] Re: Add multiarch metadata to libxkbcommon*dev packages
** Description changed: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. + + Also, tests/x11comp is actually deactivated, and seems to be the only + place that uses one of the x11-xkb-utils binaries, so maybe this + dependency can just be removed? ** Description changed: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. - Also, tests/x11comp is actually deactivated, and seems to be the only - place that uses one of the x11-xkb-utils binaries, so maybe this - dependency can just be removed? + Also, tests/x11comp is actually deactivated (since Mar 13, 2016 + upstream), and seems to be the only place that uses one of the x11-xkb- + utils binaries, so maybe this dependency can just be removed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1720692 Title: Add multiarch metadata to libxkbcommon*dev packages Status in libxkbcommon package in Ubuntu: New Bug description: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. Also, tests/x11comp is actually deactivated (since Mar 13, 2016 upstream), and seems to be the only place that uses one of the x11 -xkb-utils binaries, so maybe this dependency can just be removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1720692/+subscriptions -- Mailing list: https://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 1720692] [NEW] Add multiarch metadata to libxkbcommon*dev packages
Public bug reported: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. ** Affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New ** Description changed: + Release: Artful Aardvark 17.10 + Package Version: 0.7.1-2 + As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1720692 Title: Add multiarch metadata to libxkbcommon*dev packages Status in libxkbcommon package in Ubuntu: New Bug description: Release: Artful Aardvark 17.10 Package Version: 0.7.1-2 As far as I can tell (after creating a local patch and building and installing them as Multi-Arch: same) libxkbcommon-dev and libxkbcommon-x11-dev can be safely marked as Multi-Arch: same with no additional changes. Note that in order to cross-build the package, I also patched the build dependency x11-xkb-utils as Multi-Arch: allowed, and then used an :any dep. The use of :any as a dep is possibly appropriate, as I successfully built the package this way, I think only the tests depend on it, and they seem to call the binaries at runtime rather than compiling against them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1720692/+subscriptions -- Mailing list: https://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 1376903] Re: Caps lock delay
It appears this would also affect numlock as well. (and yes, it's a problem that's affecting me as well--which makes it impossible to type stuff in Linux since I routinely use the caps lock key for a lot of different scenarios). -- 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/1376903 Title: Caps lock delay Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I'm having a problem with Ubuntu, to be precise I have problem with its CAPS LOCK DELAY. I have a habit to use caps lock when I need a capital letter in my sentence, but problem is that I changing Caps lock in Ubuntu is slow, so I end up with sentence like this: - THis is a test. CAn you see how the first two letters are capital. THis happens only on UBuntu, not on my WIndows! Instead of holding shift like a normal person to capitalize my works, I hit Caps Lock, then hit the letter, then hit Caps Lock again. I know this is a strange habit, but I tried to change it to use Shift but I just can't. I want to contiunue using Caps lock, but the delay on Ubuntu is causing to have two capital letters in one word, and that is a problem, specially if you are typing very fast (like I). In 5 out of 10 cases I enter my password wrong beacuse of this delay. I'm guessing this may have somthing with X org or something. IS there a fix? If not, this should be reported as a BUG! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1376903/+subscriptions -- Mailing list: https://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 1689825] Re: gnome-keyring not unlocked on boot
I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and NetworkManager still have problems though. On Google Chrome and likely Chromium I fixed the 2 minute start wait by adding --password-store=basic the command line. You can add it the Exec entry in your desktop file or by editing the menu entry with menu-libre or equivalent. You will have to sign in to Chrome again if you use their syncing functionality. I like syncing because I can see history and open tabs from my phone on my desktop and vice versa. It seems Chromium uses a plain text password store with the basic option so you may not prefer this option. I don't use Chromium password storage since I use KeePass so it works for me. https://chromium.googlesource.com/chromium/src/+/lkcr/docs/linux_password_storage.md I have read that PAM is supposed to unlock the keyring as configured in LightDM (My current display manager) but that's not being done apparently. There is alot of garbage on Google about incompatibilities with autologin. My account is not set to autologin and requires a password to login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- Mailing list: https://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 1165609] Re: There is no apparent way to stop Orca
Behavior still exists... `killall orca; apt remove gnome-orca` was my approach. Would've kept it installed if there was some way to stop it without resorting to killall. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1165609 Title: There is no apparent way to stop Orca Status in OEM Priority Project: Invalid Status in gnome-orca package in Ubuntu: Confirmed Bug description: The "Orca Screen Reader" icon in the Dash is a trap. If a user accidentally opens it, the only apparent recourse for the incessant jabber is to either mute the volume system-wide or log out. This makes for a very poor user experience. Orca could avoid this situation by providing at least one of the following: 1) A notification of how to stop it, if there is a way to stop it. 2) A confirmation prompt prior to starting. 3) A quit option in a standard location such as the indicator menu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-orca 3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sat Apr 6 18:35:02 2013 InstallationDate: Installed on 2013-04-06 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-orca UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1165609/+subscriptions -- Mailing list: https://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 1637333] [NEW] gnome-terminal crashes when tab is dragged onto another tab's terminal area
Public bug reported: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages spyro@julep:~$ 3. Expected behavior: Tab should split into a new window (as it does if you drop it onto someplace that's not a gnome-terminal window). At the worst, it should go back to where it was on the tab bar instead of crashing. 4. Actual behavior: The whole gnome-terminal window crashes, losing any activity or work on other tabs. Other open gnome-terminal windows also crash and close. >From /var/log/syslog: Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: ** Oct 27 14:54:03 julep org.gnome.Terminal[2217]: Gtk:ERROR:/build/gtk+3.0-j0Vp0u/ gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion fail ed: (window != NULL) Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Contacts.SearchProvider' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Documents' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Nautilus' I've also saved the apport-generated crash report if that would be helpful to upload. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area Status in gnome-terminal package in Ubuntu: New Bug description: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog
⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] ↳ BisonCam, NB Pro id=11 [slave keyboard (3)] Affects me too, Ubuntu 16.04, but this only affected me after a recent kernel update (it worked before, now it's broken). The lxinput program works for setting mouse-settings, but it does not provide any settings for the touchpad. -- 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/1132063 Title: Mouse settings missing from Mouse & Touchpad dialog Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: In Progress Bug description: On up to date Raring alpha, on System Settings > Mouse & Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://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 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze
I'm having the same issue on 14.04.4, and I think the solution in #40 will work for me. However, I am having trouble downgrading the xserver- xorg-video-intel version from lts-wily (2:2.99.917+git20150808-0ubuntu4~trusty2). When I try and install the specific version mentioned in #40 I get unmet dependencies: xorg-video-abi-15 and xserver-xorg-core (>= 2:1.14.99.902), followed by "Unable to correct problems, you have held broken packages". Any advice or ideas? -- 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/1362848 Title: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-355 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89 from Additional Drivers application then reboot, it shows black screen, no login window, I even can't use ctrl+alt+F2 to switch to text mode, then I reboot and go to recovery mode, use 'prime-select intel' to switch to intel GPU and reboot, everything is fine, but as soon as I switch to nvidia GPU, still same issue. OS: Ubuntu 14.04 64bit Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600 Desktop: Unity Kernel: 3.13.0 CPU: Intel® Core™ i7-4700MQ Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+subscriptions -- Mailing list: https://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 1534932] [NEW] package apport 2.19.1-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: either python or software center not sure ProblemType: Package DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Sat Jan 16 08:53:00 2016 DuplicateSignature: package:apport:2.19.1-0ubuntu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-12-28 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: apport Title: package apport 2.19.1-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1534932 Title: package apport 2.19.1-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: either python or software center not sure ProblemType: Package DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Sat Jan 16 08:53:00 2016 DuplicateSignature: package:apport:2.19.1-0ubuntu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-12-28 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: apport Title: package apport 2.19.1-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1534932/+subscriptions -- Mailing list: https://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 41738] Re: confusing error message when connection via ssh fails, because host key verification failed
confirm in Ubuntu-15.10 this bug still exists. in gnome3 nautilus how to invalidate the ssh host cache? I can remove ~/.ssh/known_hosts (or by ssh-keygen -R ... that particular host) that resolved ssh command line login only; but in the file manager (nautilus) it prompts this error message, and I don't know where nautilus save the ssh host key cache? and how to invalidate Oops! Something went wrong. Unhandled error message: Host key verification failed -- 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/41738 Title: confusing error message when connection via ssh fails, because host key verification failed Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Bug description: If I connect to a server via "ssh://hostname" the connection fails, when the key changed. But the error message isn't "Host key verification failed" or something simmiliar, it's: Nautilus cannot display "ssh://hostname". Please select another viewer and try again. This is totally confusing, because you try solutions which won't fit the problem (changed or wrong host key). To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/41738/+subscriptions -- Mailing list: https://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 1527829] [NEW] displayport MST external monitors don't return from sleep mode
Public bug reported: When displays go to sleep, upon return from sleep the two monitors attached to a belkin mini displayport to 2x HDMI, do not return from sleep. This results in part of the desktop being inaccessible, until the external displays are unplugged, and then plugged back in. Sometimes, Xorg will also back down to one monitor. The data accompanying this report is for an instance where the power save mode caused Xorg to drop to the primary monitor only. This is on Ubuntu 15.10 on a Dell XPS 13 (9333) with integrated intel HD 4400 graphics. There are two external monitors connected by HDMI to a belkin DP-MST adapter which connects to the mini-displayport. A single- HDMI-to-mini-displayport belkin adapter works as expected (coming out of power save). xserver-xorg-video-intel: Installed: 2:2.99.917+git20150808-0ubuntu4 Expected behavior: Displays go to sleep, and upon returning all displays are still present and all wake. Xorg.0.log, relevant happenings: [ 189.711] (II) intel(0): Disabled output DP1-1 [ 189.711] (II) intel(0): Disabled output DP1-2 [ 189.739] (II) intel(0): resizing framebuffer to 1920x1080 [ 189.745] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 190.339] (II) intel(0): Enabled output DP1-1 [ 190.351] (II) intel(0): Enabled output DP1-2 dmesg relevant happenings: [ 190.031929] [ cut here ] [ 190.032008] WARNING: CPU: 1 PID: 1114 at /build/linux-1vdNXv/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:476 intel_pipe_will_have_type.isra.41+0x6e/0x80 [i915]() [ 190.032015] WARN_ON(num_connectors == 0) [ 190.032019] Modules linked in: [ 190.032025] drbg ansi_cprng ctr ccm rfcomm vmw_vsock_vmci_transport vsock vmw_vmci bnep snd_hda_codec_hdmi arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_wmi hid_rmi sparse_keymap kvm dell_laptop crct10dif_pclmul dcdbas crc32_pclmul dell_smm_hwmon aesni_intel iwlmvm aes_x86_64 lrw mac80211 gf128mul glue_helper ablk_helper cryptd iwlwifi uvcvideo serio_raw videobuf2_vmalloc videobuf2_memops videobuf2_core cfg80211 v4l2_common videodev media snd_hda_codec_realtek hid_multitouch snd_hda_codec_generic lpc_ich shpchp joydev input_leds snd_soc_rt5640 btusb btrtl snd_soc_rl6231 btbcm btintel snd_soc_core bluetooth snd_compress snd_hda_intel mei_me mei snd_hda_codec snd_hda_core ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi [ 190.032158] snd_seq snd_seq_device snd_timer snd acpi_als kfifo_buf dw_dmac industrialio dw_dmac_core soundcore snd_soc_sst_acpi 8250_dw i2c_designware_platform dell_rbtn i2c_designware_core spi_pxa2xx_platform intel_smartconnect mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 hid_generic usbhid uas usb_storage i915 i2c_algo_bit drm_kms_helper psmouse drm ahci libahci wmi video sdhci_acpi sdhci i2c_hid hid [ 190.032287] CPU: 1 PID: 1114 Comm: Xorg Not tainted 4.2.0-21-generic #25-Ubuntu [ 190.032293] Hardware name: Dell Inc. XPS13 9333/0GFTRT, BIOS A04 03/19/2014 [ 190.032298] 187f4872 880212327ad8 817e9449 [ 190.032309] 880212327b30 880212327b18 8107b3d6 [ 190.032318] 8802119e1800 8801f0382d80 6667 [ 190.032327] Call Trace: [ 190.032342] [] dump_stack+0x45/0x57 [ 190.032354] [] warn_slowpath_common+0x86/0xc0 [ 190.032364] [] warn_slowpath_fmt+0x55/0x70 [ 190.032420] [] intel_pipe_will_have_type.isra.41+0x6e/0x80 [i915] [ 190.032474] [] intel_modeset_compute_config.part.90+0x460/0xb80 [i915] [ 190.032496] [] ? drm_atomic_helper_check_modeset+0x62/0x970 [drm_kms_helper] [ 190.032600] [] intel_modeset_compute_config+0x42/0x50 [i915] [ 190.032667] [] intel_crtc_set_config+0x28f/0x580 [i915] [ 190.032736] [] ? drm_modeset_lock_all_crtcs+0x90/0xa0 [drm] [ 190.032783] [] drm_mode_set_config_internal+0x66/0x100 [drm] [ 190.032839] [] drm_mode_setcrtc+0x3e9/0x500 [drm] [ 190.032879] [] drm_ioctl+0x125/0x610 [drm] [ 190.032889] [] ? fsnotify+0x316/0x4a0 [ 190.032922] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [ 190.032937] [] do_vfs_ioctl+0x295/0x480 [ 190.032946] [] ? __sb_end_write+0x35/0x70 [ 190.032953] [] ? vfs_write+0x15a/0x1a0 [ 190.032962] [] SyS_ioctl+0x79/0x90 [ 190.032986] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 190.033013] ---[ end trace 9834aabfe51525cf ]--- [ 190.033036] [ cut here ] (so on) Other warnings: [ 190.068878] WARNING: CPU: 0 PID: 1114 at /
[Desktop-packages] [Bug 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
I got this message on trusty 14.04: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:31711): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. As instructed, I tried and got: # gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache The program 'gdk-pixbuf-query-loaders' is currently not installed. You can install it by typing: apt-get install libgdk-pixbuf2.0-dev Taking that hint, if I install libgdk-pixbuf2.0-dev first, then hicolor-icon-theme.postinst no longer complains. So, maybe /usr/bin/gdk-pixbuf-query-loaders belongs in the libgdk-pixbuf2.0 rather than the libgdk-pixbuf2.0-dev package. Furthermore, libgtk-3-bin (which owns the /usr/bin/gtk-update-icon-cache-3.0 command that hicolor-icon-theme.postinst calls) should declare a dependency on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/619003 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib /gdk-pixbuf-2.0/2.10.0/loaders.cache' Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Debian: New Bug description: During installation of updated version of libgdk-pixbuf2.0-0 on August 10th 2010, the apt term.log contained multiple (>300) copies of the following warning: (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Nevertheless, the file complained about exists, and is readable in gedit. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 Architecture: amd64 CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Aug 16 18:13:29 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+subscriptions -- Mailing list: https://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 911622] Re: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefu
*** This bug is a duplicate of bug 619003 *** https://bugs.launchpad.net/bugs/619003 ** This bug has been marked a duplicate of bug 619003 GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/911622 Title: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden (file not found) Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: after the latest dist-upgrade on 12.04 there are a lot of these messages (Datei oder Verzeichnis not found == file not found) GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgdk-pixbuf2.0-0 2.25.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Wed Jan 4 07:30:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf UpgradeStatus: Upgraded to precise on 2011-12-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/911622/+subscriptions -- Mailing list: https://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 270018] Re: command-line option --zoom=ZOOMFACTOR fails when called with multiple tabs
when I run this command line to open a new window, and in the new window open a new tab, it's disappointing that the zoom factor is not inherited; although upstream has obsolete, can this still be fixed? to keep zoom factor applying to all tabs in the same window? gnome-terminal --geometry=132x43 --window --active --zoom=1.5 this bug is still reproducing in ubuntu 15.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/270018 Title: command-line option --zoom=ZOOMFACTOR fails when called with multiple tabs Status in GNOME Terminal: Expired Status in gnome-terminal package in Ubuntu: Triaged Bug description: Binary package hint: gnome-terminal GNOME gnome-terminal 2.22.1 on Hardy. The following command open two tabs in a new terminal window but seems to ignore the zoom factors gnome-terminal --tab --zoom=3 --tab --zoom=3 gnome-terminal --tab --zoom=3 --tab also produces two tabs with no zoom. However, the command gnome-terminal --tab --zoom=3 works ... producing one tab with the proper zoom factor. Importance: If zoom doesn't work then the whole command line aspect of gnome-terminal is not very useful since opening several tabs with a script only to have to manually fix the size is a real pain. The zoom factor is properly inherited from manually opened (ctrl-shift-t) tabs. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/270018/+subscriptions -- Mailing list: https://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 1468834] Re: lightdm does not source .xsession
I don't follow the reason for closing this... It seems like maybe you're thinking I said this bug is all wrong, but it's not. The point is that instead of *sourcing* $HOME/.xsession, the Xsession system script should *exec* it if it exists, completely bypassing the rest of the system Xsession script. The debian manual I linked to actually describes that behavior. The point is, Ubuntu appears to ignore it entirely. -- 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/1468834 Title: lightdm does not source .xsession Status in xorg package in Ubuntu: Invalid Bug description: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions -- Mailing list: https://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 1468834] Re: lightdm does not source .xsession
>From the debian manual: > any user who defines "~/.xsession" or "~/.Xsession" is able to customize the action of "/etc/X11/Xsession" by completely overriding the system code. It does (or did) that by executing the script via exec... -- 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/1468834 Title: lightdm does not source .xsession Status in xorg package in Ubuntu: Invalid Bug description: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions -- Mailing list: https://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 1468834] Re: lightdm does not source .xsession
It may well have, but it's a change that's bad. For what it's worth, the Debian manuals still document this: https://www.debian.org/doc/manuals/debian- reference/ch07.en.html#_customizing_the_x_session_classic_method I've been a member of the Linux community for 20 years--Take comfort in the fact that these shell scripts have often changed rather arbitrarily over the years on many different distributions, and the owners of those changes seemingly do not understand the consequences of the changes they have made. This stuff was designed this way for a reason... It's supposed to make it easy for the user to customize their X window system session regardless of what shell they use or how they have their environment set up. This change is one of several that actually work against that goal. -- 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/1468834 Title: lightdm does not source .xsession Status in xorg package in Ubuntu: New Bug description: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions -- Mailing list: https://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 1468832] Re: lightdm sources .profile
Which is a good point actually... what if the user is a C shell user? How does sourcing .profile help them? The "classic" way of setting this up is clearly far superior. -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1468832] Re: lightdm sources .profile
In point of fact .xsession is supposed to be an executable shell script with a shebang line, it's not supposed to be sourced at all, or at least historically that has always been the case. Theoretically the .xsession file could be a C shell script so as long as it is executed instead of sourced, this is not very interesting. -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1468832] Re: lightdm sources .profile
Also slight correction: BASH does NOT automatically source .bashrc on login shells; so .profile would need to source the environment file as well. -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1468832] Re: lightdm sources .profile
@Myself: in my description I repeatedly used "interactive shell" when I meant "login shell" instead. The distinction is important, (and thus the shell makes the distinction)--the user's .profile is only sourced in the latter case. On all other interactive shells it sources .bashrc instead. This is so that .profile can initialize the user's terminal settings, whereas this should NOT be done for all other interactive shells. @Anders: it need not be .bashrc, and I explicitly addressed the case where your shell was not BASH. It seems you did not read the whole report. @Gunnar: So your argument is basically, "This is designed wrong, but we shouldn't fix it, because some people might have to learn the right way to do it." That is a pretty bad argument. The "mess" is that some percentage of users *might* need to modify their shell start-up files to do it the right way. That doesn't seem like much of a mess to me; it's fixing a mess. It seems clear to me that .profile and the other shell start-up files belong to the shell, and hence no program other than the shell has any business reading them. Regardless, if you don't care to fix this, what's your proposed fix for lightdm barfing on errors from terminal commands that quite rightly belong in .profile? At the very least, session start-up should not be interrupted by the fact that lightdm does this badly. That behavior is a regression, in the sense that Ubuntu 12.x did not do this until some random update somewhere between six months and a year ago, and no previous Ubuntu release did it. I have not run a pristine 14.04 Ubuntu--I've only been running it for a couple of months with all current updates applied, so I can't say whether it has or has not changed there. In the past, some distributions (including Ubuntu, if I'm not mistaken) have sourced $HOME/.profile in the system Xsession script. That solution is wrong too; but it has the nice property that if there are errors caused by the shell not running on a terminal, they are silently ignored (since there's nowhere to send them). -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1468834] Re: lightdm does not source .xsession
Try: man xsession The X window system has been reading this file since forever. -- 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/1468834 Title: lightdm does not source .xsession Status in xorg package in Ubuntu: Incomplete Bug description: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468834/+subscriptions -- Mailing list: https://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 794315] Re: lightdm forgets to source /etc/profile and ~/.profile
See also Bug #1468834. -- 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/794315 Title: lightdm forgets to source /etc/profile and ~/.profile Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm package in Debian: Confirmed Bug description: Binary package hint: lightdm /etc/gdm/Xsession had this code: # First read /etc/profile and .profile test -f /etc/profile && . /etc/profile test -f "$HOME/.profile" && . "$HOME/.profile" # Second read /etc/xprofile and .xprofile for X specific setup test -f /etc/xprofile && . /etc/xprofile test -f "$HOME/.xprofile" && . "$HOME/.xprofile" so that, for example, ~/bin gets added to the path (by the default ~/.profile), and any user-customized environment setup gets run. After switching from gdm to lightdm, this no longer happens. This is going to be a regression now that lightdm is becoming the default display manager. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.3.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic x86_64 NonfreeKernelModules: openafs Architecture: amd64 Date: Tue Jun 7 19:27:11 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.utf8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/794315/+subscriptions -- Mailing list: https://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 1468832] Re: lightdm sources .profile
See also Bug #1468834. -- 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/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 1468834] [NEW] lightdm does not source .xsession
Public bug reported: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1468834 Title: lightdm does not source .xsession Status in lightdm package in Ubuntu: New Bug description: There is a decades-old standard protocol for starting up a user's X session, which requires display managers to source the user's ~/.xsession file. lightdm fails to do this. See also Bug #1468832. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468834/+subscriptions -- Mailing list: https://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 1468832] [NEW] lightdm sources .profile
Public bug reported: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go--this is the entire point of differentiating interactive shells from non- interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1468832 Title: lightdm sources .profile Status in lightdm package in Ubuntu: New Bug description: It is a bug for any display manager to read .profile--you guys are absolutely killing me with this. The user's .profile is to be read by the shell, on interactive shell (i.e. terminal) logins ONLY. The man page for bash explains this in detail; it's also discussed in the dash man page. The problem with display managers reading .profile is that it is the place where commands to set up your terminal (i.e. stty) go --this is the entire point of differentiating interactive shells from non-interactive shells, and it's the reason only interactive shells read .profile at all. Currently, if you have any such commands in your .profile, lightdm barfs on them, delaying the login session and forcing you to click on a prompt. This is extremely annoying (and wrong)! It would be satisfactory to make lightdm not display the errors, but that's the wrong solution. There's already a decades-established method of getting X display managers to source your environment settings: the .xsession file. It should be read by ALL display managers (or the session file that starts them). If you have common environment settings you want set in all your shells, the correct way to handle this is: .bashrc: # set all common environment vars here ENV_VAR=foo ... .profile: # set up terminal stty erase # BASH already sources .bashrc by default on interactive sessions .xsession: if [ -f .bashrc ] source .bashrc If you're not using BASH, you can still use this method without changing anything, except in .profile you need to explicitly source the .bashrc file. Of course you can change the name of the file that contains the common settings to reflect that your shell is not BASH; since the file is sourced by your other files explicitly, it does not matter what the user calls it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1468832/+subscriptions -- Mailing list: https://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 794315] Re: lightdm forgets to source /etc/profile and ~/.profile
Sigh. Display managers should NEVER source .profile at all... that file is exclusively for interactive shells, as is explicitly stated in all of the man pages of every shell ever. I just opened Bug #1468832 about this, where I also explained how to properly accomplish what people want here. -- 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/794315 Title: lightdm forgets to source /etc/profile and ~/.profile Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm package in Debian: Confirmed Bug description: Binary package hint: lightdm /etc/gdm/Xsession had this code: # First read /etc/profile and .profile test -f /etc/profile && . /etc/profile test -f "$HOME/.profile" && . "$HOME/.profile" # Second read /etc/xprofile and .xprofile for X specific setup test -f /etc/xprofile && . /etc/xprofile test -f "$HOME/.xprofile" && . "$HOME/.xprofile" so that, for example, ~/bin gets added to the path (by the default ~/.profile), and any user-customized environment setup gets run. After switching from gdm to lightdm, this no longer happens. This is going to be a regression now that lightdm is becoming the default display manager. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.3.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic x86_64 NonfreeKernelModules: openafs Architecture: amd64 Date: Tue Jun 7 19:27:11 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.utf8 LC_MESSAGES=en_US.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/794315/+subscriptions -- Mailing list: https://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 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
Awesome. it's finally working. Added the trusty proposed repo and updated( it updated quite a lot of other stuff). I was able to install the amd drivers for my Radeon hd 8600 m series with the catalyst center. I am on Ubuntu 14.04.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in fglrx-installer source package in Precise: In Progress Status in fglrx-installer-updates source package in Precise: In Progress Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] fglrx cannot be installed correctly together with the new lts stacks. [Test case] Installing the xserver from lts-utopic will prevent the current fglrx from being installed. The new fglrx will install correctly [Regression potential] Low. This fglrx release is already in use in 15.04 without any major issues. -- Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Attempting to install xserver-xorg-core instead yields: zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but
[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
Affects me too. Ubuntu gnome 14.04.2 AMD A6-5200 APU with Radeon(TM) HD Graphics × 4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: Invalid Status in fglrx-installer-updates package in Ubuntu: Invalid Status in fglrx-installer source package in Precise: Triaged Status in fglrx-installer-updates source package in Precise: Triaged Status in fglrx-installer source package in Trusty: In Progress Status in fglrx-installer-updates source package in Trusty: In Progress Bug description: SRU Request: [Impact] fglrx cannot be installed correctly together with the new lts stacks. [Test case] Installing the xserver from lts-utopic will prevent the current fglrx from being installed. The new fglrx will install correctly [Regression potential] Low. This fglrx release is already in use in 15.04 without any major issues. -- Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Attempting to install xserver-xorg-core instead yields: zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: lib
[Desktop-packages] [Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
Hi,
I was wondering if someone could help me out on this.
I would like to apply the patch, but have very little ubuntu knowledge.
I am running ubuntu 14.04 and have found I get this problem.
The workaround in #22 works for me, but makes the fonts hard to read.
This is why I would like to use Alexander's patch.
However, I am not sure how to do it.
I checked my system for xfsettingsd and displays.c but could not find either
sudo . -name displays.c -print
returns nothing (run from the root dir)
I assume that if I can find displays.c all I need to do is go to that directory
and do:
patch < {patchname}
Any/All help appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1308105
Title:
Xfce resets TV mode to NULL when power cycled
Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
Confirmed
Status in xfce4-settings:
Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
Invalid
Status in xfce4-settings package in Ubuntu:
Confirmed
Bug description:
I had an HTPC with Mythbuntu 12.04 installed. Upon upgrading a new
behavior that if the TV is power cycled it no longer detects a link
with the HTPC.
When this happens I can find in the xorg log that there is an
accompanying log item:
[ 39829.509] (II) NVIDIA(0): Setting mode "NULL"
After debugging with NVIDIA at
https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
detected/ we've deteremined it's a X client that reacts to the RANDR
events causing the mode to be set to NULL.
Working through the list in an Xfce environment, the culprit is
xfsettingsd. If xfsettingsd is running, it causes the TV to come up
in a NULL mode. If it's killed, it remains in the mode it was
previously running in.
Until this is fixed, this behavior can be worked around with a simple shell
script:
==
#!/bin/sh
#Fix TV state when HDMI link is lost.
#By Mario Limonciello
OUTPUT="HDMI-0"
BAD_MODE="1280x720"
GOOD_MODE="1920x1080"
for MODE in $BAD_MODE $GOOD_MODE; do
DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
sleep 2
done
==
To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions
--
Mailing list: https://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 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
Confirmed in 14.04.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/505278 Title: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added? Status in GNOME keyring services: New Status in Portable OpenSSH: Fix Released Status in “gnome-keyring” package in Ubuntu: Confirmed Status in “openssh” package in Ubuntu: Invalid Bug description: ssh-add -D seems to NOT remove my identities, even though it says it did. Also, why are all possible identities auto-added right away (on start?) rafal@lcwood(22:11:48)~$ ssh-add -l 8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA) 8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA) 8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood (RSA) 8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood (RSA) rafal@lcwood(22:11:50)~$ ssh-add -D All identities removed. rafal@lcwood(22:11:51)~$ ssh-add -l 8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA) 8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA) 8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood (RSA) 8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood (RSA) rafal@lcwood(22:11:53)~$ apport-bug ssh-ad ProblemType: Bug Architecture: amd64 Date: Sat Jan 9 22:12:25 2010 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: ssh (not installed) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: openssh Uname: Linux 2.6.31-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/505278/+subscriptions -- Mailing list: https://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 1026046] Re: Missing support for thumb resting on bottom of clickpad
I'll just add that this problem (not surprisingly) also exists on my Lenovo Helix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1026046 Title: Missing support for thumb resting on bottom of clickpad Status in xf86-input-synaptics: Unknown Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Status in “xserver-xorg-input-synaptics” source package in Precise: Confirmed Status in “xserver-xorg-input-synaptics” package in Debian: New Bug description: When using the trackpad on the MacBook Pro In Mac OS X it is possible to have the thumb resting (ready to click) on the bottom part of the touchpad while moving the mouse pointer around with your index or middle finger. Likewise it is also possible to use two finger scrolling with the index and middle finger on the upper part on the track pad while resting the thumb on the lower part of the trackpad. This behaviour is not currently supported with the synaptics driver in 12.04. It wil register a two finger scroll when the thumb is resting in the bottom part and index finger moves around in the upper part. I have tried playing aroud with the setting AreaBottomEdge that disables all motion on the bottom part of the touchpad. Unfortunately when this setting is enabled it still detects a finger in the area, so it wil register a two finger scroll like before. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad
Where is this problem originating? Is it a bug in the synaptics driver or is it just a missing feature? Is there something making is particularly hard to fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1026046 Title: Missing support for thumb resting on bottom of clickpad Status in xf86-input-synaptics: Unknown Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Status in “xserver-xorg-input-synaptics” source package in Precise: Confirmed Status in “xserver-xorg-input-synaptics” package in Debian: New Bug description: When using the trackpad on the MacBook Pro In Mac OS X it is possible to have the thumb resting (ready to click) on the bottom part of the touchpad while moving the mouse pointer around with your index or middle finger. Likewise it is also possible to use two finger scrolling with the index and middle finger on the upper part on the track pad while resting the thumb on the lower part of the trackpad. This behaviour is not currently supported with the synaptics driver in 12.04. It wil register a two finger scroll when the thumb is resting in the bottom part and index finger moves around in the upper part. I have tried playing aroud with the setting AreaBottomEdge that disables all motion on the bottom part of the touchpad. Unfortunately when this setting is enabled it still detects a finger in the area, so it wil register a two finger scroll like before. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1320371] [NEW] Removing Pulseaudio deletes System Settings icons
Public bug reported: Ubuntu 14.04 64-bit installed on home theater PC, replacing 12.04. As usual, having problems getting Pulseaudio and XBMC to cooperate on passthrough audio over SPDIF. So I removed Pulseaudio and switched to Alsa for sound processing. This fixed the problem with passthrough audio, but unlike previous versions of Ubuntu, this action deleted most of the icons from the Systems Settings panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D7p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri May 16 16:15:54 2014 InstallationDate: Installed on 2014-05-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/21/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-EM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "System Settings panel after Pulseaudio removal" https://bugs.launchpad.net/bugs/1320371/+attachment/4114103/+files/SystemSettings.png -- 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/1320371 Title: Removing Pulseaudio deletes System Settings icons Status in “alsa-driver” package in Ubuntu: New Bug description: Ubuntu 14.04 64-bit installed on home theater PC, replacing 12.04. As usual, having problems getting Pulseaudio and XBMC to cooperate on passthrough audio over SPDIF. So I removed Pulseaudio and switched to Alsa for sound processing. This fixed the problem with passthrough audio, but unlike previous versions of Ubuntu, this action deleted most of the icons from the Systems Settings panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D7p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri May 16 16:15:54 2014 InstallationDate: Installed on 2014-05-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-EM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/21/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-EM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor:
[Desktop-packages] [Bug 1311617] [NEW] After suspending, shift key is stuck down
Public bug reported: When using the sticky keys accessibility feature and returning from suspend, the right shift key is logically "stuck". Note that I do not use the right shift key, so it must be switching states on suspend/resume. Entering a password will fail, and through trial and error I found it is the right shift key. Pressing this key "resets" the feature and allows entering of a password normally. This problem doesn't occur on my computer when the sticky key feature is off. This problem did not occur before release 14.04, so I assume it has to do with the new "unified" log in screen that replaced the prior screen on resuming from standby. Other relevant info: Dell XPS 9333 Description:Ubuntu 14.04 LTS Release:14.04 lightdm: Installed: 1.10.0-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 07:23:06 2014 InstallationDate: Installed on 2014-04-17 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.lightdm.conf: 2014-04-17T19:18:51.313854 ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1311617 Title: After suspending, shift key is stuck down Status in “lightdm” package in Ubuntu: New Bug description: When using the sticky keys accessibility feature and returning from suspend, the right shift key is logically "stuck". Note that I do not use the right shift key, so it must be switching states on suspend/resume. Entering a password will fail, and through trial and error I found it is the right shift key. Pressing this key "resets" the feature and allows entering of a password normally. This problem doesn't occur on my computer when the sticky key feature is off. This problem did not occur before release 14.04, so I assume it has to do with the new "unified" log in screen that replaced the prior screen on resuming from standby. Other relevant info: Dell XPS 9333 Description:Ubuntu 14.04 LTS Release:14.04 lightdm: Installed: 1.10.0-0ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 23 07:23:06 2014 InstallationDate: Installed on 2014-04-17 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.lightdm.conf: 2014-04-17T19:18:51.313854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1311617/+subscriptions -- Mailing list: https://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 1280613] Re: Nvidia Optimus + bumblebee configuration not optimized by default
Same problem for me on a Lenovo with a Nvidia 550M graphics card. Ubuntu 13.10 && 14.04, plain ole Unity variants. -- 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/1280613 Title: Nvidia Optimus + bumblebee configuration not optimized by default Status in Bumblebee: NVIDIA Optimus for Linux!: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: Hardware configuration is a ThinkPad T540p with GeForce GT 730M. I understand that this graphics chip as some new fangled "Nvidia Optimus" technology involved. I began testing with Xubuntu 13.10 x64, then re-imaged the system with the Alpha build of Xubuntu 14.04 x64 of 20140214. I have had to do extensive hand editing to the configuration of selecting both nvidia-graphics-drivers-331-updates and the bumblebee packages in order to at least see the Nvidia driver "active" in the Nvidia Settings applet. I have been updating the modprobe configuration: /etc/modprobe.d/bumblebee.conf commenting out the exclusions for the 331 version driver I have updated the bumblebee configuration: /etc/bumblebee/bumblebee.conf according to the example found here: http://elementaryforum.org/forum/support-assistance/how-to_aa/3996-nvidia-optimus-drivers-and-tools-installation#post3997 To get the NVIDIA Settings to show the board finally... I found this command here: "Nvidia Optimus on Linux" \ "How to use Bumblebee." http://www.linux.org/threads/nvidia-optimus-on-linux.4415/ optirun -b none nvidia-settings -c :8 However starting an additional instance of the NVIDIA Settings applet via the Xubuntu menu system shows that instance not being able to detect the Nvidia drivers being loaded. So it seems that one must use the optirun command to start individual programs that the Nvidia drivers are requested to service the video for?! This makes absolutely no sense. Shortly I am seeking automatic configuration of the latest Nvidia binary drivers to be used 100% of the time. Even the old Envy Nvidia binary driver installer worked far more simply than dealing with this "Nvidia Optimus" technology. "Needs improvement." To manage notifications about this bug go to: https://bugs.launchpad.net/the-bumblebee-project/+bug/1280613/+subscriptions -- Mailing list: https://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 993187] Re: ubuntu 12.04 completely freezes frequently.
I am also having an issue where my system completely locks up. Mouse / keyboard are unresponsive and I am unable to ssh in from another system. This is a new build with all new hardware: ASUS H81I-PLUS Socket 1150 w/ Intel H81 Chipset Intel Pentium G3220 Dual-Core Processor @ 3.0 GHz Team Vulcan 8GB (2 x 4GB) 240-Pin DDR3 1600 (under clocked to 1333 by the BIOS) Intel 330 Series 60GB SSD on-board Intel graphics connected via HDMI to a 24" Samsung LCD TV I was originally running openSuSE 13.3 w/KDE, but as this system is meant to be a multimedia system, it was causing more trouble that I wanted to deal with. I do not recall it freezing at any time. I then installed Kubuntu 13.10 64bit as the multimedia support is better than SuSE. This is when I started to get multiple lock ups. I thought maybe it was due to something not being happy with 13.10, so I installed 12.04.3 LTS w/ KDE 4.12. I also removed the 8GB 'Team' memory and installed a single 4GB ADATA 1333MHz DIMM. This appeared to have resolved the issue, but it locked up on me three times yesterday. Once while using Amarok (remote mySQL database & collection on a FreeNAS NFS share), once while just using the desktop and another while attempting to play an 800MB .MKV file in XBMC standalone (remote mySQL, file located on a FreeNAS NFS share). I've checked the various logs, and there does not appear to be anything of any relevance as nothing 'crashes' exactly, the entire system just locks. I've disabled all power management features & functions. No wi-fi hardware installed / enabled. Cat 6 gigabit network connection. Microsoft Sculpt bluetooth keyboard w/ ASUS bluetooth dongle - paired with bluemon Microsoft ARC wireless mouse w/ MS wireless dongle -- 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/993187 Title: ubuntu 12.04 completely freezes frequently. Status in “linux” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Released Status in “xserver-xorg-video-intel” source package in Precise: Fix Released Bug description: Update: 6/12/2012 This bug is about a complete system lock-up. No other TTYs can be started. Mouse doesn't move. Keyboard doesn't react. The only solution is hard reset. Seems to happen on a variety of configurations, including nVidia, ATI and Intel graphics. If you are still able to TTY or SSH into other sessions, move the mouse or use the keyboard, file another bug. Thx. Joris V. (brains). Update: 5/21/2012 Updating the kernel to 3.3.6 as suggested by Michael in #91, the system seems stable, no freezes yet in 5-6 hrs of using and watching videos for couple of hrs. Original description: I recently installed newly released ubuntu 12.04 LTS 64 bit version on my desktop. And it is frequently freezing, for the first few hours it ran smoothly and when I started watching videos it started freezing randomly. I have to use hard restart every time. Initially it was only during videos but now even during normal browsing it is freezing. I am using on board graphics and do not have any graphics card installed. Can someone please help me here, I really love the new looks of 12.04 and it bugs me not being able to use :( Below is my hardware configuration: Processor: Intel CORE i3 processor (2nd generation) Board: Intel® Desktop Board DH67BL Ram: 4GB Graphics: On board HDD: 500 GB Please let me know if you need more information, or any specific logs I can capture (and how). Thanks, Ketan Patil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/993187/+subscriptions -- Mailing list: https://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 1254837] [NEW] Window gets shorter when restoring.
Public bug reported: This happened with 12.04 when I was trying Unity. And, apparently it is still going on... Open pidgin. It should now be in the Messenger notification tray area with a triangle indicating it is running. Click envelope icon. Click Pidgin. Pidgin window should now be open. Stretch the widow tall. Repeat: Close the window using the X. Click envelope icon. Click Pidgin. As you repeat, you will notice the Pidgin window gets shorter and shorter. FYI: Does not happen with 12.04+Gnome+AWN. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pidgin 1:2.10.7-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 25 14:04:44 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-08 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1254837 Title: Window gets shorter when restoring. Status in “pidgin” package in Ubuntu: New Bug description: This happened with 12.04 when I was trying Unity. And, apparently it is still going on... Open pidgin. It should now be in the Messenger notification tray area with a triangle indicating it is running. Click envelope icon. Click Pidgin. Pidgin window should now be open. Stretch the widow tall. Repeat: Close the window using the X. Click envelope icon. Click Pidgin. As you repeat, you will notice the Pidgin window gets shorter and shorter. FYI: Does not happen with 12.04+Gnome+AWN. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pidgin 1:2.10.7-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 25 14:04:44 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-08 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: pidgin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1254837/+subscriptions -- Mailing list: https://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 1244369] [NEW] Keeps pausing for ages whilst downloading IMAP
Public bug reported: Running 24.0.1 on Windows 7 x64 Ultimate. I'm trying to download my brother's Hotmail e-mai for him, so that I can then copy it to the Local folders as an offline backup. However, it's taking ages because TB keeps pausing for ages and no apparent reason. My brother has a number of folders for his e-mail on Hotmail and for example, on the folder 2009 it stopped for several minutes at 144 out of 272. Then it get to 153 and paused again for several minutes, then it went to 269 and paused again for several minutes. It's probably taken at least 15 minutes so far just to do that one folder. When it got to 272 out of 272, it again paused for ages and then when it had finished, just didn't do anything for a while. Now it's start on the folder "2010" and has got to 14 out of 1420 and paused again. When it's paused, Task Manager shows that TB is not doing anything. Under Account Settings I have "Keep messages for this account on the computer" and have all his folders except for Deleted ticked. However, if I right-click on the Account in the main window and select Subscribe, it shows all the folders, including Deleted, ticked so obviously these settings are for different uses. If I disable "Keep messages" and then drag each IMAP folder to Local Folders to copy it, it doesn't seem to pause and although slow (no doubt a limitation of IMAP) it steadily downloads the messages and Task Manager shows around 2-3% CPU. However, if I drag multiple folders to copy instead of a single one, it does seem to start pausing quite often again, even though it's only copying one folder at a time, perhaps the others being queued triggers the problem. Actually, I just tried again only dragging one of the folders "Newsletters", which was the first one it was copying when dragging multiple folders and that's having problems, currently paused at 41 out of 151. Several of the folders I'd copied previous to this one had the same amount of e-mails and didn't pause, so it doesn't appear to be the number of e-mails in a folder that's the issue. Testing on my own system the other day, with both Hotmail and Gmail accounts, I found that when copying the mail from the IMAP folders to the Local Folders, it appeared to be downloading it all again, despite it already being stored on my PC, which doesn't seem right. It also seemed to make no difference to the size of the TB data files when disabling "Keep messages for this account on the computer" with Inbox being around 600MB and Sent around 550MB. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1244369 Title: Keeps pausing for ages whilst downloading IMAP Status in “thunderbird” package in Ubuntu: New Bug description: Running 24.0.1 on Windows 7 x64 Ultimate. I'm trying to download my brother's Hotmail e-mai for him, so that I can then copy it to the Local folders as an offline backup. However, it's taking ages because TB keeps pausing for ages and no apparent reason. My brother has a number of folders for his e-mail on Hotmail and for example, on the folder 2009 it stopped for several minutes at 144 out of 272. Then it get to 153 and paused again for several minutes, then it went to 269 and paused again for several minutes. It's probably taken at least 15 minutes so far just to do that one folder. When it got to 272 out of 272, it again paused for ages and then when it had finished, just didn't do anything for a while. Now it's start on the folder "2010" and has got to 14 out of 1420 and paused again. When it's paused, Task Manager shows that TB is not doing anything. Under Account Settings I have "Keep messages for this account on the computer" and have all his folders except for Deleted ticked. However, if I right-click on the Account in the main window and select Subscribe, it shows all the folders, including Deleted, ticked so obviously these settings are for different uses. If I disable "Keep messages" and then drag each IMAP folder to Local Folders to copy it, it doesn't seem to pause and although slow (no doubt a limitation of IMAP) it steadily downloads the messages and Task Manager shows around 2-3% CPU. However, if I drag multiple folders to copy instead of a single one, it does seem to start pausing quite often again, even though it's only copying one folder at a time, perhaps the others being queued triggers the problem. Actually, I just tried again only dragging one of the folders "Newsletters", which was the first one it was copying when dragging multiple folders and that's having problems, currently paused at 41 out of 151. Several of the folders I'd copied previous to this one had the same amount of e-mails and didn't pause, so it doesn't appear to be the number of e-mails in a folder tha
[Desktop-packages] [Bug 1233799] [NEW] "Skip Backup" didn't skip the backup.
Public bug reported: Turned on computer for first time in about a week. Backup started going, but I was using my internet connection and didn't want the backup to go. Right click icon in classic gnome shell and selected "Skip Backup". Within 10 minutes, it was trying to prepare another backup... selected skip again and reported this bug. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: deja-dup 22.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 CheckboxSubmission: 880f1cef728a67d1a58407cc143447d4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Tue Oct 1 14:36:46 2013 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: Upgraded to precise on 2012-06-15 (473 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1233799 Title: "Skip Backup" didn't skip the backup. Status in “deja-dup” package in Ubuntu: New Bug description: Turned on computer for first time in about a week. Backup started going, but I was using my internet connection and didn't want the backup to go. Right click icon in classic gnome shell and selected "Skip Backup". Within 10 minutes, it was trying to prepare another backup... selected skip again and reported this bug. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: deja-dup 22.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-53.81-generic 3.2.50 Uname: Linux 3.2.0-53-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 CheckboxSubmission: 880f1cef728a67d1a58407cc143447d4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Tue Oct 1 14:36:46 2013 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: deja-dup UpgradeStatus: Upgraded to precise on 2012-06-15 (473 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1233799/+subscriptions -- Mailing list: https://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 1045353] Re: LibreOffice commands are not displayed in the HUD
I have this issue with 13.04 and LO 4.1 - just confirming it is present in newest versions. Opening a "fresh instance" does not enable HUD for me, either, as with other users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1045353 Title: LibreOffice commands are not displayed in the HUD Status in “hud” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Ubuntu Release: Ubuntu 12.10 Quantal Quetzal beta1 Package version: libreoffice-gtk Package version: 1:3.6.1~rc2-1ubuntu3 Expected behavior: It should be possible to launch LO actions from the HUD. Actual behavior: Libreoffice commands are not shown in the HUD. According to comments, this is the case for: - Ubuntu 12.10 and 13.04 - LibreOffice cycles 3.6 and 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1045353/+subscriptions -- Mailing list: https://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 951585] Re: gvfsd-afp consumes 100% of processor cycles
same thing with mint 15 on kernel 3.10 ** Tags added: 15 mint -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/951585 Title: gvfsd-afp consumes 100% of processor cycles Status in “gvfs” package in Ubuntu: Confirmed Bug description: Happens on an irregular basis on 12.04 and I think I've experienced it on 11.10. For no reason gvfsd-afp starts up. Cooling fan kicks in, system becomes laggy. Easily cured using system monitor and killing the process. Someone on the Ubuntu Forum asked if I have a Mac on the network and the answer is yes, an iMac and there are shares on that machine I can access. Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions -- Mailing list: https://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 1159411] Re: Some online accounts cannot be added
I also experience this bug. I can temporarily add and edit configurations in Ubuntu Online Accounts (a.k.a. credentials- preferences) again by killing all empathy and telepathy processes, then loading the panel, but this behaviour recurs shortly after restarting empathy. The problem first started after I performed a release upgrade to 13.04 from 12.10. It happens under both Unity and Gnome. Blowing away the contents of ~/.config/libaccounts-glib allowed me to enter new account details again, but the bug returned later. (I also upgraded to gnome 3.8 via the Gnome team PPA, without any improvement.) I see some errors in kern.log when reloading the accounts panel after restarting empathy: kernel: [ 526.559946] empathy-auth-cl[3249]: segfault at 20028 ip 7f909fb0261e sp 7fff2c7dee10 error 4 in libaccounts- glib.so.0.1.3[7f909faf6000+19000] Also various other warning messages (not sure how relevant): (credentials-preferences:6073): credentials-cc-panel-WARNING **: cc-credentials-account-details-page.vala:346: Error looking up theme color (gnome-control-center:8668): credentials-cc-panel-WARNING **: cc-credentials-login-capture.vala:61: Could not register service. (gnome-control-center:8668): credentials-cc-panel-WARNING **: cc-credentials-login-capture.vala:33: Could not acquire name. In addition to this bug, since upgrading to 13.04, I've been unable to connect to my AIM account in Empathy (which works fine in pidgin). Jabber connectivity seems okay, although sometimes Empathy fails to display anything at all in its Contact List until it's been killed and restarted a few times. I'm attaching an apport crash report which hopefully contains more relevant details about the empathy-auth-client crash. telepathy-mission-control-5 Version: 1:5.14.0-0ubuntu2 empathy Version: 3.6.4-0ubuntu4.1 ** Attachment added: "_usr_lib_empathy_empathy-auth-client.501.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1159411/+attachment/3687530/+files/_usr_lib_empathy_empathy-auth-client.501.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1159411 Title: Some online accounts cannot be added Status in “gnome-control-center-signon” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Go to "System settings -> Online accounts". 2. Select to add a "AIM" new account. 3. Click on the "done" button. *** BEHAVIOUR *** - EXPECTED: An account to be created. - REAL: No account is added, because the screen for entering the information is never shown. WORKAROUND You can write the following line into the Terminal to get a fully working instant messaging client: sudo apt-get install pidgin -y && pidgin ** RELEVANT DETAILS ** - It affects AIM, ICQ, Salut, Jabber and Yahoo! accounts. - AIM and Yahoo!' never work. - Salut and Jabber' work a few times, not clear when they do. - Affects both existing accounts and the creation of new ones. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 Date: Sun Mar 24 14:08:46 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-03-23 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130323) MarkForUpload: True ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=es_ES.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8c10069809 :mov0x38(%rdi),%rax PC (0x7f8c10069809) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: empathy_account_widget_apply_and_log_in () from /usr/lib/empathy/libempathy-gtk-3.6.4.so g_cclosure_marshal_VOID(int0_t, void) () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in empathy_account_widget_apply_and_log_in() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (gnome-terminal:2352): Vte-2.90-WARNING **: No se pueden convertir caracteres de UTF-8 a actual. (gnome-terminal:2352): Gtk-WARNING **: Unknown property: GtkHScal
[Desktop-packages] [Bug 903422] Re: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0)
There was recently a change to the adb tool. It now does authentication; the user is prompted to "allow" a new computer when the phone is connected to it. The old adb is not compatible. This change is probably why it fails, even though MTP on the Samsung Galaxy Nexus previously worked. I used the new adb (with the authentication) to manually push files. That worked fine. Trying the other forum posts (like changing the udev rules) did not work for me. It was very aggravating to get the cool new phone (Nexus 4) and then not be able to transfer files to it. (This comment reposted from duplicate bug 1092621.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/903422 Title: Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0) Status in GVFS: Fix Released Status in “gmtp” package in Ubuntu: Invalid Status in “gvfs” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “gmtp” source package in Precise: Invalid Status in “gvfs” source package in Precise: Confirmed Status in “udev” source package in Precise: Invalid Status in “gmtp” source package in Quantal: Invalid Status in “gvfs” source package in Quantal: Confirmed Status in “udev” source package in Quantal: Invalid Bug description: If your device is not supported please open a new bug specifying: * device in question (make / model / release) * output of `mtp-detect` when the device is attached * output of `lsusb` when the device is attached This bug will be a catch all for recent Samsung Nexus & Nexus 7, or please comment what other recent Andorid 4.x devices are affected. Yes there is a lag in providing support for the most recent devices. As soon as the fixes are available, SRUs will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions -- Mailing list: https://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 312722] Re: Connect to FTP with Login > Error "The file is not a directory"
Same problem on Ubuntu 12.10 ** This bug is no longer a duplicate of bug 290703 ssh connection should open the user directory by default -- 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/312722 Title: Connect to FTP with Login > Error "The file is not a directory" Status in Nautilus: New Status in “nautilus” package in Ubuntu: Confirmed Bug description: Ubuntu 8.04 & 8.10 Using Nautilus Connect to server, and choosing FTP (with login), entering (domain/IP) address, user, and hitting "Connect". Prompts for password, and then displays: "The folder contents could not be displayed" "Sorry, couldn't display all the contents of "/ on [host-address/IP]": The file is not a directory" To me it seems to be a problem with the directory on the server. the folder for the user is not the root / folder of the server it is: "/d:/www/edvl/domain.ch/html" when i connect with FireFTP or other clients. So Nautilus tries to connect to domain.ch/ where it has no permission! When connecting with the ftp> (Terminal) to "domain.ch/" there is also an error "ftp: domain.ch/: Unknown host Opening "domain.ch" leads to prompting the Username and afterwards the pw Perhaps Nautilus automatically adds the / at the end of the URL and this causes problems. Connecting directly to domain.ch/d:/www/edvl/domain.ch/html does not work neither. Consider: http://ubuntuforums.org/showthread.php?p=6468035 BTW: This is my first Bug Report, To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/312722/+subscriptions -- Mailing list: https://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 1026858] Re: flashplugin-installer can't find adobe-flashplugin_11.2.202.233.orig.tar.gz
The file IS missing. 404. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1026858 Title: flashplugin-installer can't find adobe- flashplugin_11.2.202.233.orig.tar.gz Status in “flashplugin-nonfree” package in Ubuntu: Expired Bug description: The following command silently fails to install the adobe flash plugin. $ sudo apt-get install --reinstall flashplugin-installer Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/8408 B of archives. After this operation, 0 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 167772 files and directories currently installed.) Preparing to replace flashplugin-installer 11.2.202.233ubuntu2 (using .../flashplugin-installer_11.2.202.233ubuntu2_i386.deb) ... Unpacking replacement flashplugin-installer ... Processing triggers for update-notifier-common ... flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.233.orig.tar.gz Setting up flashplugin-installer (11.2.202.233ubuntu2) ... If I use wget to try and download adobe-flashplugin_11.2.202.233.orig.tar.gz I get a 404 error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1026858/+subscriptions -- Mailing list: https://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 1159609] Re: random freeze
I'm sorry I forgot to mention it, but I had the same problem with random locking up when I used the ATI graphics that came with the computer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1159609 Title: random freeze Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: The system locks up at random. It may not lock for a day after booting up the machine. It may lock up after a few minutes of booting up the machine. Sometimes the display just freezes, displaying whatever was last being displayed on the monitor. Sometimes the monitor displays a solid color when locking up. The machine does not respond to pings nor any of the key combinations involving sysrq. The only way to recover is a hard reset. The machine is running Kubuntu 12.04.2 LTS Release:12.04 The computer is a HP Pavilion p6-2003w Desktop PC. The url giving its specs is below. http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03052733&lang=en&cc=us&contentType=SupportFAQ&prodSeriesId=5151865&prodTypeId=12454 Motherboard AAHD2-HY (Holly) Manufacturer: Pegatron Form factor: uATX: 24.38 cm (9.6 inches) x 24.38 cm (9.6 inches) Chipset: AMD Hudson-D2 FCH Memory sockets: 2 x DDR3 Front side bus speeds: 100 MHz UMI (Unified Media Interface) Processor socket: FM1 Expansion Slots: PCI-Express Generation 2 speed 1 PCI Express x16 3 PCI Express x1 1 PCI Express Mini Card x1 Processor AMD E2 3200 Processor TDP: 65W Operating speed: Up to 2.4 GHz Number of cores: 2 Socket: FM1 Bus speed: 4.0 GT/s HT3 Memory 4 GB Amount: 4 GB Speed: PC3-10600 MB/sec Type: DDR3-1333 The above is the memory it came with. I have since added another identical 4GB. This upgrade did not affect the random lockup problem. Built in graphics AMD E-Series Processors E2-3200 HD 6370D65W This is the on board graphics. I have added an NVIDIA geforce 210 1024MB card. This upgrade did not affect the random lockup problem. Sound/Audio Integrated Realtek ALC 656 Audio *Integrated audio is not available if a sound card is installed. Built-in High Definition 5.1 channel audio Audio codec: Realtek ALC 656 Networking LAN: 1000-Base-T Interface: PCI Express x1 Technology: Realtek RTL8111E gigabit ethernet controller Data transfer speeds: up to 10/100/1000 Mb/s Transmission standards: 1000-Base-T Ethernet I added an additional RTL8111 PCIe nic. This also did not affect the locking up issue. The machine came with windows7. I soon replaced it with XP. The random lockup bug didn't show itself until I replaced windows with Kubuntu. For a few weeks I tried Slackware 14.0 64bit and did not experience any problem with randome freezes during this time. When I reinstalled Kubuntu, the random lockup bug returned. Thanks for your help. Derek ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Sun Mar 24 20:01:49 2013 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) MarkForUpload: True ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1159609/+subscriptions -- Mailing list: https://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 1159609] [NEW] random freeze
Public bug reported: The system locks up at random. It may not lock for a day after booting up the machine. It may lock up after a few minutes of booting up the machine. Sometimes the display just freezes, displaying whatever was last being displayed on the monitor. Sometimes the monitor displays a solid color when locking up. The machine does not respond to pings nor any of the key combinations involving sysrq. The only way to recover is a hard reset. The machine is running Kubuntu 12.04.2 LTS Release:12.04 The computer is a HP Pavilion p6-2003w Desktop PC. The url giving its specs is below. http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03052733&lang=en&cc=us&contentType=SupportFAQ&prodSeriesId=5151865&prodTypeId=12454 Motherboard AAHD2-HY (Holly) Manufacturer: Pegatron Form factor: uATX: 24.38 cm (9.6 inches) x 24.38 cm (9.6 inches) Chipset: AMD Hudson-D2 FCH Memory sockets: 2 x DDR3 Front side bus speeds: 100 MHz UMI (Unified Media Interface) Processor socket: FM1 Expansion Slots: PCI-Express Generation 2 speed 1 PCI Express x16 3 PCI Express x1 1 PCI Express Mini Card x1 Processor AMD E2 3200 Processor TDP: 65W Operating speed: Up to 2.4 GHz Number of cores: 2 Socket: FM1 Bus speed: 4.0 GT/s HT3 Memory 4 GB Amount: 4 GB Speed: PC3-10600 MB/sec Type: DDR3-1333 The above is the memory it came with. I have since added another identical 4GB. This upgrade did not affect the random lockup problem. Built in graphics AMD E-Series Processors E2-3200 HD 6370D65W This is the on board graphics. I have added an NVIDIA geforce 210 1024MB card. This upgrade did not affect the random lockup problem. Sound/Audio Integrated Realtek ALC 656 Audio *Integrated audio is not available if a sound card is installed. Built-in High Definition 5.1 channel audio Audio codec: Realtek ALC 656 Networking LAN: 1000-Base-T Interface: PCI Express x1 Technology: Realtek RTL8111E gigabit ethernet controller Data transfer speeds: up to 10/100/1000 Mb/s Transmission standards: 1000-Base-T Ethernet I added an additional RTL8111 PCIe nic. This also did not affect the locking up issue. The machine came with windows7. I soon replaced it with XP. The random lockup bug didn't show itself until I replaced windows with Kubuntu. For a few weeks I tried Slackware 14.0 64bit and did not experience any problem with randome freezes during this time. When I reinstalled Kubuntu, the random lockup bug returned. Thanks for your help. Derek ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Sun Mar 24 20:01:49 2013 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) MarkForUpload: True ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu precise -- 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/1159609 Title: random freeze Status in “xorg” package in Ubuntu: New Bug description: The system locks up at random. It may not lock for a day after booting up the machine. It may lock up after a few minutes of booting up the machine. Sometimes the display just freezes, displaying whatever was last being displayed on the monitor. Sometimes the monitor displays a solid color when locking up. The machine does not respond to pings nor any of the key combinations involving sysrq. The only way to recover is a hard reset. The machine is running Kubuntu 12.04.2 LTS Release:12.04 The computer is a HP Pavilion p6-2003w Desktop PC. The url giving its specs is below. http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03052733&lang=en&cc=us&contentType=SupportFAQ&prodSeriesId=5151865&prodTypeId=12454 Motherboard AAHD2-HY (Holly) Manufacturer: Pegatron Form factor: uATX: 24.38 cm (9.6 inches) x 24.38 cm (9.6 inches) Chipset: AMD Hudson-D2 FCH Memory sockets: 2 x DDR3 Front side bus speeds: 100 MHz UMI (Unified Media Interface) Processor socket: FM1 Expansion Slots: PCI-Express Generation 2 speed 1 PCI Express x16 3 PCI Express x1 1 PCI Express Mini Card x1 Processor AMD E2 3200 Processor TDP: 65W Operating speed: Up to 2.4 GHz Number of cores: 2 Socket: FM1 Bus speed: 4.0 GT/s HT3 Memory 4 GB Amount: 4 GB Speed: PC3
[Desktop-packages] [Bug 1085392] Re: Merge Chromebook UCM profiles into ALSA packages
Updated again today. Just checked alsa-utils. I have 1.0.25-1ubuntu5.1 (precise-proposed) Still no sound in ubuntu, sound works fine in chromeos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1085392 Title: Merge Chromebook UCM profiles into ALSA packages Status in Cross distro support for Samsung Chromebook (ARM based): Triaged Status in “alsa-lib” package in Ubuntu: Fix Released Status in “alsa-utils” package in Ubuntu: Fix Released Status in “alsa-lib” source package in Precise: Fix Committed Status in “alsa-utils” source package in Precise: Fix Committed Status in “alsa-lib” source package in Quantal: Fix Committed Status in “alsa-utils” source package in Quantal: Fix Committed Status in “alsa-lib” package in Fedora: New Bug description: SRU test case in comment 13 below https://bugs.launchpad.net/chromebook-arm/+bug/1085392/comments/13 === Samsung Chromebook has UCM profiles which handle automatic switching speakers<>headphones (and probably <>hdmi but not checked under Ubuntu yet). We need to ship them to save users from frying speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/chromebook-arm/+bug/1085392/+subscriptions -- Mailing list: https://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 1130427] [NEW] package libreoffice-writer 1:3.6.2~rc2-0ubuntu3 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr
Public bug reported: Using Ubuntu 12.10, This error occured upon first update of libreoffice since installation of Ubuntu 12.10 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libreoffice-writer 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Tue Feb 19 16:46:13 2013 ErrorMessage: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr/lib/libreoffice/program/libmswordlo.so.dpkg-new': unexpected end of file or stream InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: libreoffice Title: package libreoffice-writer 1:3.6.2~rc2-0ubuntu3 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr/lib/libreoffice/program/libmswordlo.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1130427 Title: package libreoffice-writer 1:3.6.2~rc2-0ubuntu3 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr/lib/libreoffice/program/libmswordlo.so.dpkg-new': unexpected end of file or stream Status in “libreoffice” package in Ubuntu: New Bug description: Using Ubuntu 12.10, This error occured upon first update of libreoffice since installation of Ubuntu 12.10 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libreoffice-writer 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Tue Feb 19 16:46:13 2013 ErrorMessage: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr/lib/libreoffice/program/libmswordlo.so.dpkg-new': unexpected end of file or stream InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: libreoffice Title: package libreoffice-writer 1:3.6.2~rc2-0ubuntu3 failed to install/upgrade: cannot copy extracted data for './usr/lib/libreoffice/program/libmswordlo.so' to '/usr/lib/libreoffice/program/libmswordlo.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1130427/+subscriptions -- Mailing list: https://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 1085392] Re: Merge Chromebook UCM profiles into ALSA packages
Welp. In that case. Just pulled latest updates, rebooted, tried playing audio in a few apps. Nothing. The usual channels seem unmuted in alsamixer - is there one I should look for? I'm worried about melting this thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1085392 Title: Merge Chromebook UCM profiles into ALSA packages Status in Cross distro support for Samsung Chromebook (ARM based): Triaged Status in “alsa-lib” package in Ubuntu: Fix Released Status in “alsa-utils” package in Ubuntu: Fix Released Status in “alsa-lib” source package in Precise: Fix Committed Status in “alsa-utils” source package in Precise: Fix Committed Status in “alsa-lib” source package in Quantal: Fix Committed Status in “alsa-utils” source package in Quantal: Fix Committed Status in “alsa-lib” package in Fedora: New Bug description: SRU test case in comment 13 below https://bugs.launchpad.net/chromebook-arm/+bug/1085392/comments/13 === Samsung Chromebook has UCM profiles which handle automatic switching speakers<>headphones (and probably <>hdmi but not checked under Ubuntu yet). We need to ship them to save users from frying speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/chromebook-arm/+bug/1085392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
