[Desktop-packages] [Bug 1987528] Re: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white
*** This bug is a duplicate of bug 1971242 *** https://bugs.launchpad.net/bugs/1971242 I suspect this problem is caused by this issue (https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups where the option print-color-mode is set to monochrome when the printer PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500 uses CMYK as its ColorModel: CMYK) We were trying to use lpadmin -p -o print-color-mode-default=colour lpadmin -p -o print-color-mode=colour and this worked the first time we printed to the printer and then it would reset to "monochrome" which I suspect is caused by this report typo: https://github.com/OpenPrinting/cups/pull/687 Cheers, Ian. PS Failed to note this was a duplicate bug before posting. Apologies. And I see it is already know in #1971242 that the latest version of cups fixes the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1987528 Title: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Printer ( in my context ) is Ricoh Aficio mpc 3002 and most Ricoh's drivers are open-source ( https://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C3002 ) Since I « upgraded » my installation from 20.04 → 22.04, I'm unable to print in colors, only black and white, whatever I set in driver. I tried what's suggested in ⋅ https://askubuntu.com/questions/1410583/upgrading-to-22-04-printer-doesnt-works-in-color ⋅ https://discourse.ubuntubudgie.org/t/22-04-unable-to-add-printer-which-perfectly-worked-in-20-04/6209 I might go wrong somewhere cause I still can't manage to print in color. → the snap thing ( Gutenprint Printer Application ) does not detect my ( network ) printer, → I'm not sure of the name for PRINTER I should input in command « lpadmin -p PRINTER -o print-color-mode-default=color » ( and is this as normal user or sudo ? ) It seems related to ⋅ https://github.com/OpenPrinting/cups/issues/421 It's a regression ( as it used to work out of the box before 22.04 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1987528/+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 1971242] Re: printing PDF appears always grey, no color
I suspect this problem is caused by this issue (https://github.com/OpenPrinting/cups/pull/500) that is fixed in cups where the option print-color-mode is set to monochrome when the printer PPD file has ColorModel: CMYK and not ColorModel: RGB (Our Ricoh C4500 uses CMYK as its ColorModel: CMYK) We were trying to use lpadmin -p -o print-color-mode-default=colour lpadmin -p -o print-color-mode=colour and this worked the first time we printed to the printer and then it would reset to "monochrome" which I suspect is caused by this reported typo: https://github.com/OpenPrinting/cups/pull/687 Cheers, Ian. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: New Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
I'm having the same problem (on multiple systems). I've remove'd firefox as a snap nut the snap still gets installed at some later point (when a new one is available?) despite the fact that my apt preferences are set to use the mozillateam-ubuntu-ppa-kinetic PPA. -- 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/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: Confirmed Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap snapd_8542.snap snap-store_467.snap https://ubuntuhandbook.org/index.php/2021/10/prevent-installing-firefox-snap-ubuntu-mate-21-10/ claims that a similar issue affects Ubuntu MATE 21.04 and the solution was to type "sudo apt-mark manual firefox", which I have done, but that has not resolved the problem. I'm not here to explain why I wouldn't want the snap version, it is clearly a bug for snap to accept a command to uninstall something and then automatically reinstall it days later without the permission of the user, and especially galling that it removes the real version at the same time. I have lost data (passwords and history) because of this bug, because one of the many faults of the snap version is that it ignores the user's real ~/.mozilla profile and creates a shadow profile instead inside of the snap system. Please disable this behavior. It's obnoxious, it ignores EXPLICITY stated user preferences, and it causes the loss of data. I am unclear on what package is causing the behavior so for now marking it against Firefox, but it could be against some other piece of infrastructure related to snap: affects ubuntu/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1999308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
A video showing the problem is attached. ** Attachment added: "VID20221209190801.gif" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+attachment/5635281/+files/VID20221209190801.gif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Currently after the last update, the screen dims and does not turn off. ** Attachment added: "log2.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+attachment/5635280/+files/log2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor Status in linux-raspi package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 1998716] [NEW] Ubuntu 22.10 does not turn off monitor
Public bug reported: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image kinetic raspi-image ** Attachment added: "LogRPi4.txt" https://bugs.launchpad.net/bugs/1998716/+attachment/5634373/+files/LogRPi4.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1998716 Title: Ubuntu 22.10 does not turn off monitor Status in gnome-shell package in Ubuntu: New Bug description: I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a strange behaviour of the screen saver. In settings -> energy -> power saving options I selected Screen Blank after 5 minutes. After 5 minutes of inactivity, the screen goes blank, the monitor says No Signal and turns off, but a few seconds after it turns on again, showing a completely black screen. The desired behaviour here is that Ubuntu sends no signal to the monitor, so the monitor goes into low-consumption mode. But this is not happening, the monitor is on and showing a black screen. I wonder how to solve this problem, especially given the current energy situation in Europe. This bug is related to the Ubuntu 22.04 LTS and 22.10 version. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7 Uname: Linux 5.19.0-1009-raspi aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Dec 4 21:31:27 2022 DisplayManager: gdm3 GsettingsChanges: ImageMediaBuild: 20221018.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998716/+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 1989224] [NEW] Display powersave only blanks, but does not turn off - RPi4
Public bug reported: I used Ubuntu 22.04 (with wayland) on Raspberry Pi 4, and it seems like the power-saving feature in gnome does not properly turn off the screen. My attached display does not go into a low power standby mode. Although the screen after X minutes is dark but still has backlight. OS: Ubuntu 22.04 jammy Kernel: aarch64 Linux 5.15.0-1014-raspi DE: GNOME 41.7 X: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-1014.16-raspi 5.15.46 Uname: Linux 5.15.0-1014-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 9 22:09:30 2022 ImageMediaBuild: 20220809 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image jammy raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1989224 Title: Display powersave only blanks, but does not turn off - RPi4 Status in gnome-power-manager package in Ubuntu: New Bug description: I used Ubuntu 22.04 (with wayland) on Raspberry Pi 4, and it seems like the power-saving feature in gnome does not properly turn off the screen. My attached display does not go into a low power standby mode. Although the screen after X minutes is dark but still has backlight. OS: Ubuntu 22.04 jammy Kernel: aarch64 Linux 5.15.0-1014-raspi DE: GNOME 41.7 X: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build2 ProcVersionSignature: Ubuntu 5.15.0-1014.16-raspi 5.15.46 Uname: Linux 5.15.0-1014-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri Sep 9 22:09:30 2022 ImageMediaBuild: 20220809 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1989224/+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 1867668] Re: Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver
I had *exactly* the (very well) described issues here: o Really weird corrupted font artifacts. o Bizarre semi-tiled blocks on my background screen. Occurred after doing an upgrade of Ubuntu 20.04 on an Dell XPS 7590. Running the suggested command: sudo apt remove xserver-xorg-video-intel And rebooting fixed everything. Thanks very much. -- 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/1867668 Title: Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-04 (12 days ago) UserGroups: microk8s sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1867668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1941752]
(In reply to Lukáš Karas from comment #24) > Here is my proposed fix in Gwenview: > https://invent.kde.org/graphics/gwenview/-/merge_requests/125 Do we need a prod on the libexiv2 package as well to indicate that it needs an update to fix the cause of the crash? (The fix for gwenview to handle such crashes better is welcome, but not sufficient). I can't see any bug report with libexiv2 as the product. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1955087] [NEW] bluetooth cannot transfer files to phone although connected
Public bug reported: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1955087 Title: bluetooth cannot transfer files to phone although connected Status in bluez package in Ubuntu: New Bug description: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1955087/+subscriptions -- Mailing
[Desktop-packages] [Bug 1941752]
(In reply to Gordon Lack from comment #21) Seems to be related to how old the jpegs are. 2016 and earlier it crashes. 2017 and late its OK. Roughly. If I run gwenview on the command line for a failing one this is what I see reported: [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
Created attachment 144559 New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: Browsing through images with Dolphin. Select to open one in Gwenview. Crashes every time. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140466192913600) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140466192913600) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140466192913600, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fc0dafab476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc0daf917b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1950912]
The **NOT** part was feedback on my comment 4: > I'll wait to see whether 91.3.2+ also fixes the drop-down menus. -- 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/1950912 Title: [upstream] Drop-down Calendar menus unreadable in Thunderbird Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: New Bug description: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1950912/+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 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Bug report submitted at Mozilla. https://bugzilla.mozilla.org/show_bug.cgi?id=1742202 ** Bug watch added: Mozilla Bugzilla #1742202 https://bugzilla.mozilla.org/show_bug.cgi?id=1742202 -- 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/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+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 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
The previous entry wasn't entirely correct. 91.2.1 was *also* using the configured Light Theme colours (for the colour of the "quote bar" in HTML messages). What has happened on the update to 91.3.1 is that it is now using the Light background colours for the Dark Theme. (In 91.2.1 it was, correctly, using the Dark Theme colours). -- 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/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+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 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Also (just noticed) that 91.3.1 has introduced *another* bug. I use the "Quote Colors" extension. It has the option to to set the text and background colours for quoted text. You can configure them separately for Light and Dark Themes. At 91.3.1 it is now using the text and background colours configured for a Light Theme, even though I am using a Dark Theme. It's seems that in many places Thunderbird (where many is a growing number) has lost track of the fact it is using a Dark Theme! -- 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/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+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 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Today's update to 91.3.1 has made things WORSE!!! Now the (left hand) sidebar in the Preferences menu and Add-ons manager are ALSO displayed with a light background (and light text!!) when I'm using the Dark Theme!!! The drop-down menus are *still* totally wrong (and unreadable). -- 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/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+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 1950912] [NEW] Drop-down Calendar menus unreadable in Thunderbird
Public bug reported: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. - The drop-down menus for editing events (such as options for Repeat: and - Reminder:) have light text on a light background, and are hence - unreadable. + The drop-down menus for editing Calendar events (such as options for + Repeat: and Reminder:) have light text on a light background, and are + hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: gml44103277 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: - default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp64s0 scope link metric 1000 - 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 + default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp64s0 scope link metric 1000 + 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name:
[Desktop-packages] [Bug 1931799] Re: audio not working on Raspberry Pi 4
When pulseaudio crashed: daniel@RPi4:~$ systemctl --user restart pulseaudio.service [Child 10555, AudioIPC0] WARNING: 8d8426b0 StateCallback() state 2 cubeb error: file /build/firefox-vFiRwG/firefox-89.0.1+build1/dom/media/AudioStream.cpp:654 [Child 10555, MediaDecoderStateMachine #1] WARNING: Decoder=99667c00 [OnMediaSinkAudioError]: file /build/firefox-vFiRwG/firefox-89.0.1+build1/dom/media/MediaDecoderStateMachine.cpp:3916 This is log after restart. ** Attachment added: "pulseaudio_restart.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+attachment/5507135/+files/pulseaudio_restart.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+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 1931799] Re: audio not working on Raspberry Pi 4
This is log. ** Attachment added: "pulseaudio.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+attachment/5507134/+files/pulseaudio.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+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 1931799] Re: audio not working on Raspberry Pi 4
Pulseaudio crashes, but not regularly. Usually a failure occurs when I listen music (via VLC, Rhythmbox) or I watch youtube. I heard only noise in the headphones when this app is crashed. Only restarting the pulseaudio service helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+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 1931799] [NEW] audio not working on Raspberry Pi 4
Public bug reported: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+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 1931527] Re: I have artifacts on Youtube videos in Firefox.
Heavy artifacts on youtube videos ** Attachment added: "Firefox Bug.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+attachment/5503776/+files/Firefox%20Bug.png -- 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/1931527 Title: I have artifacts on Youtube videos in Firefox. Status in firefox package in Ubuntu: New Bug description: I use a Raspberry Pi 4, and now I have artifacts on Youtube videos in Firefox after update. Ubuntu 20.10, Firefox 89.0+build2-0ubuntu0.20.10.1 arm64 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 89.0+build2-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1398 F pulseaudio /dev/snd/pcmC1D0p: daniel 1398 F...m pulseaudio /dev/snd/controlC0: daniel 1398 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable Date: Thu Jun 10 07:55:19 2021 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 default via 192.168.1.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 600 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+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 1931527] [NEW] I have artifacts on Youtube videos in Firefox.
Public bug reported: I use a Raspberry Pi 4, and now I have artifacts on Youtube videos in Firefox after update. Ubuntu 20.10, Firefox 89.0+build2-0ubuntu0.20.10.1 arm64 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 89.0+build2-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1398 F pulseaudio /dev/snd/pcmC1D0p: daniel 1398 F...m pulseaudio /dev/snd/controlC0: daniel 1398 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable Date: Thu Jun 10 07:55:19 2021 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 default via 192.168.1.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 600 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image -- 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/1931527 Title: I have artifacts on Youtube videos in Firefox. Status in firefox package in Ubuntu: New Bug description: I use a Raspberry Pi 4, and now I have artifacts on Youtube videos in Firefox after update. Ubuntu 20.10, Firefox 89.0+build2-0ubuntu0.20.10.1 arm64 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 89.0+build2-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1398 F pulseaudio /dev/snd/pcmC1D0p: daniel 1398 F...m pulseaudio /dev/snd/controlC0: daniel 1398 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable Date: Thu Jun 10 07:55:19 2021 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 default via 192.168.1.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 600 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+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 1930312] Re: USB disks and SD cards mount for wrong user
For the record, this is not specific to Ubuntu or Ubuntu MATE at all -- I see this on Gentoo regularly, for example. It seems to be caused by a race condition in Caja and UDisks which didn't appear until UDisks started mounting volumes under user-specific subdirectories of `/media` -- so for example `user1` has volumes mounted under `/media/user1` and `user2` has volumes mounted under `/media/user2`. In ye olden days, `user1`'s UDisks-utilizing process (such as Caja) would mount the volume; `user2`'s instance of Caja would wait for the volume to get mounted by `user1`'s Caja, then open the shared mountpoint at `/media/[volume]`. Nowadays this doesn't work in any case, since `user1` puts in the request to mount the volume first and the volume is mounted under `user1`'s private mount directory -- `/media/user1/[volume]`. I'm not sure how to fix this yet, though. Maybe (but just a WAG) UDisks needs some kind of integration with the display manager or logind? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+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 1919100] [NEW] Composition window doesn't keep IMAP connexion open
Public bug reported: If you are writing a message and have only the Composition window open (not the main reading pane) then when this tries to save the current state of the reply in the Drafts folder (you've taken a short break whilst writing it) the save will fail. The reason is that there is no connexion to the IMAP server (and the Drafts folder is on the IMAP server). If you then start-up the main reading pane the save to the Drafts folder works. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.10.4 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44102927 F pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Mon Mar 15 00:17:42 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (213 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-10-25 (140 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1919100 Title: Composition window doesn't keep IMAP connexion open Status in thunderbird package in Ubuntu: New Bug description: If you are writing a message and have only the Composition window open (not the main reading pane) then when this tries to save the current state of the reply in the Drafts folder (you've taken a short break whilst writing it) the save will fail. The reason is that there is no connexion to the IMAP server (and the Drafts folder is on the IMAP server). If you then start-up the main reading pane the save to the Drafts folder works. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.10.4 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44102927 F pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Mon Mar 15 00:17:42 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (213 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-10-25 (140 days ago) dmi.bios.date:
[Desktop-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
> If you don't want to this fuse fs to be created I probably don't, but have no idea want it actually does. > then either remove xdg-desktop-portal package or mask xdg-document- portal.service with: Thanks. The masking worked fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
>> You can silence this with "df -x fuse.portal" I can, but that's not the point. Whatever is putting the mountpoint there (it's not my choice) should be putting it there in such a way that this does not happen. I *own* the mountpoint directory and file-system. Why should I get an EPERM error that I cannot remove? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
>> Thanks, that's being discussed upstream on https://github.com/flatpak /xdg-desktop-portal/issues/512 No, it's not, as that issue has been closed. Note that I'm seeing this WITHOUT having flatpak installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+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 1906744] [NEW] xdg-document-portal creates a mountpoint which produces an error report from df
Public bug reported: If I run "df" it starts with an error message: [parent]: df df: /run/user/4410/doc: Operation not permitted Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1630320 1604 1628716 1% /run . The /run/user/4410/doc (mode r-x--) has been created by: /usr/libexec/xdg-document-portal started by: /lib/systemd/systemd --user using: /usr/lib/systemd/user/xdg-document-portal.service I'm not sure why this is there, but i appear to have no control over it. It should not result in simple tools such as df producing error messages just because it exists. /proc/mounts shows it as: portal /run/user/4410/doc fuse.portal rw,nosuid,nodev,relatime,user_id=4410,group_id=1001 0 0 If it is a required mount then perhaps df should be made to ignore portal mounts by default? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xdg-desktop-portal 1.8.0-1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 4 02:09:11 2020 InstallationDate: Installed on 2020-05-03 (214 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to groovy on 2020-10-26 (39 days ago) ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1906744 Title: xdg-document-portal creates a mountpoint which produces an error report from df Status in xdg-desktop-portal package in Ubuntu: New Bug description: If I run "df" it starts with an error message: [parent]: df df: /run/user/4410/doc: Operation not permitted Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1630320 1604 1628716 1% /run . The /run/user/4410/doc (mode r-x--) has been created by: /usr/libexec/xdg-document-portal started by: /lib/systemd/systemd --user using: /usr/lib/systemd/user/xdg-document-portal.service I'm not sure why this is there, but i appear to have no control over it. It should not result in simple tools such as df producing error messages just because it exists. /proc/mounts shows it as: portal /run/user/4410/doc fuse.portal rw,nosuid,nodev,relatime,user_id=4410,group_id=1001 0 0 If it is a required mount then perhaps df should be made to ignore portal mounts by default? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xdg-desktop-portal 1.8.0-1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 4 02:09:11 2020 InstallationDate: Installed on 2020-05-03 (214 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to groovy on 2020-10-26 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1906744/+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 1887683] [NEW] I Have no system settings
Public bug reported: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 15 16:08:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed nvidia, 304.137, 4.15.0-111-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2846 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 15 11:12:03 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887683 Title: I Have no system settings Status in xorg package in Ubuntu: New Bug description: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/co
[Desktop-packages] [Bug 1887685] [NEW] I Have no system settings
Public bug reported: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 15 16:08:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed nvidia, 304.137, 4.15.0-111-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2846 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 15 11:12:03 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887685 Title: I Have no system settings Status in xorg package in Ubuntu: New Bug description: When I start the computer it loads as it always have but when I use the dropdowns to get a program it just flashes and loads the top program three or for times. So I then switch off and reboot, This I do two or three times until it works properly. Best Regards Gordon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/co
Re: [Desktop-packages] [Bug 1886412] Re: $ ubuntu-bug xorg
On 06/07/2020 22:19, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and help make Ubuntu > better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read 'How to report bugs effectively' > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > > Thanks! > > ** Changed in: xorg (Ubuntu) > Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) > Status: New => Incomplete > Hi I was downloading the normal updates that come automatically when finished it told me to restart the computer, the OS opened with no problems no message I left for about 15mins and the screen used to sleep after Five mins. When I returned the screen was still open I clicked on Applications for the drop-down programmes which flashed and returned to the top. When I clicked on the top right of the screen the same thing happened. I then decided to reboot again, the same thing happened seven time before I got a good screen that worked OK except that I could not open system settings from top right icon all the rest worked. I now decided to ask Ubuntu 1 for an answer, it then set up a scan which took some time and asked me to submit the results which I did. When I click on system settings the "About this computer" loads, I have not switched off since but I switch off the screen when not in use. Regards Gordon Wright Thank you. -- 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/1886412 Title: $ ubuntu-bug xorg Status in xorg package in Ubuntu: Incomplete Bug description: I cannot open system settings so I can set up a sleep mode after leaving offfor a spell. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.137 Thu Sep 14 13:51:03 PDT 2017 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 6 11:57:21 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 304.137, 4.15.0-108-generic, x86_64: installed nvidia, 304.137, 4.15.0-109-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4] InstallationDate: Installed on 2012-09-29 (2837 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-LE-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1
[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I had a problem with a *missing* internal microphone today (well, I spotted it today - probably been like this for ages...). Note that this was PulseAudio saying that there were no input devices. The problem (as I eventually spotted) was that I'd set the Profile to be Analgue Stereo Output (under Configuration in PA Volume Control). Setting this to Analogue Stereo Duplex made the internal mic show up. Might not be the problem for most people, but you never know. I did notice that if I plugged in an *external* mic the Profile switched to Duplex automatically. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()
In my case it did appear to be gTile related also. Just manually disabling the extension on the gnome extensions panel was also sufficient to trigger a crash (presumably triggering the same path as when the screen lock was activated). Presumably other extensions using libst can have the same effect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0 --- This happened when I closed Chrome and moved the curser to "Power Off/Log Out, Settings .." ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 22 11:22:08 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-15 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_font_features () from /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868440/+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 1871580] Re: Session killed instead of suspended on screen lock
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks like it might also be the same thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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 1871580] Re: Session killed instead of suspended on screen lock
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh one. However, a quick bit of experimentation appears to show that this crash only occurs with extensions enabled - after globally disabling extensions it appears to no longer occur. I haven't bisected extensions individually, but I'm guessing `gnome-shell-pomodoro` might be a good candidate since most of the others are javascript only. Still not ideal that extensions can kill the shell. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349454/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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 1871580] Re: Session killed instead of suspended on screen lock
Lots of repetitions of: ``` ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: called for pid 7303, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: debug: session gdbus call: (true,) ERROR: apport (pid 7377) Wed Apr 8 12:22:45 2020: apport: report /var/crash/_usr_bin_gnome-shell.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS ``` I guess a anti-disk filling feature is proving counterproductive here? It's also possible that I manually disabled bits of whoopsie/apport in the past. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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 1871580] Re: Session killed instead of suspended on screen lock
Session lock invoked manually (~11:00:00), lock screen displays, click mouse to get unlock. Screen freezes for ~10 seconds, then blanks briefly and shows login screen. Looks like gnome-shell crashing at about 11:00:26 - interesting lines: Apr 08 11:00:26 kallisti gnome-shell[23758]: clutter_actor_insert_child_at_index: assertion 'child->priv->parent == NULL' failed Apr 08 11:00:28 kallisti kernel: gnome-shell[23758]: segfault at 0 ip 7fce7c55445a sp 7fffada2b230 error 4 in libst-1.0.so[7fce7c532000+4b000] Apr 08 11:00:28 kallisti kernel: Code: 4d 8b 8c 24 28 01 00 00 48 98 eb 0c 0f 1f 40 00 48 83 e8 01 85 c0 78 52 4d 8b 04 c1 b9 16 00 00 00 48 89 ef 49 8b 10 48 8b 12 <48> 8b 32 f3 a6 0f 97 c2 80 da 00 84 d2 75 d7 4d 8b 40 08 49 83 78 ** Attachment added: "journal during session lock" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+attachment/5349407/+files/journal-gnome-crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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 1871580] Re: Session killed instead of suspended on screen lock
There appear to neither be any relevant crash files (there are a couple which predate upgrading this system to focal), nor are there any reports on errors.u.c for this whoopsie-id. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Incomplete Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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 1871580] [NEW] Session killed instead of suspended on screen lock
Public bug reported: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871580 Title: Session killed instead of suspended on screen lock Status in gnome-session package in Ubuntu: Invalid Bug description: Running focal (updated to 2020-04-08), ubuntu-on-wayland session. Trigger: either lock the screen manually (top-right-corner menu -> Lock) or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock). Expected result: after unlock, previous session resumes. Observed: see login dialog instead of unlock dialog, previous session and all processes appear to have been killed. This is a fairly serious usability regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-session 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:35:16 2020 InstallationDate: Installed on 2019-05-27 (316 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871580/+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.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage
[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: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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 COMPUTER INC. To manage notifications about this bug go to:
[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.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
[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 COMPUTER INC. To manage notifications about this bug go to:
[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 COMPUTER INC. To manage notifications about this bug go to:
[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 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I find this to be
[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
[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
@sil2100 it works for me as long as I set AuthType Default for / (which I didn't have to set before but I'm happy to set it now) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Released Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
If I also set "AuthType Default" for "/" then the cups 2.2.7-1ubuntu2.4 works. I did not have this set in 14.04 or 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
cups 2.2.7-1ubuntu2.4 from proposed has exactly the same symptoms for me - prompts for password when printing. So the original issue seems to be different from Esko's. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Fix Released Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Released Status in cups source package in Disco: Fix Released Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every join, instead of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
So this happened essentially from when I upgraded to 18.10 a few months ago; now, after I file the bug, it's stopped happening. I suspect a recent software update. Woohoo! (sorry for any trouble caused) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240526/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240527/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240525/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
apport information ** Tags added: apport-collected ** Description changed: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. - If an extra monitor was plugged in while the laptop was turned off - (scenario: come home, put laptop in docking station with extra monitor - attached, turn on) then often the UI will still fail to respond after - switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot - the laptop. + If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-08-13 (191 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Package: gnome-shell + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 + Tags: cosmic + Uname: Linux 4.18.0-15-generic x86_64 + UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1816896/+attachment/5240524/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-08-13 (191 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-19 (124 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-12-05T11:18:35.863354 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] Re: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
** Package changed: gnome-control-center (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1816896/+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 1816896] [NEW] Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume
Public bug reported: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1816896 Title: Laptop (HP EliteBook 9470m, Ivy Bridge) unresponsive after resume Status in gnome-control-center package in Ubuntu: New Bug description: This problem is new in Ubuntu 18.10; it did not occur with 18.04. When my laptop, an HP EliteBook 9470m, with Intel Ivy Bridge graphics, comes out of resume, often the UI is unresponsive. Typically I get a black screen, a screen with just the GNOME top bar, or what the screen was showing before the laptop was suspended. The mouse cursor moves but the UI is unresponsive to input. If I switch VTs with Ctrl+Alt+F1, the lock screen shows, I can enter my password and after that my GUI session begins to work again, where I left off. The problem appears to increase in frequency when I add external monitors. It occurs on every suspend/resume if one or more external monitors (DisplayPort or VGA) have been used since the laptop was booted, even if they were present at boot, or subsequently removed. If an extra monitor was plugged in while the laptop was turned off (scenario: come home, put laptop in docking station with extra monitor attached, turn on) then often the UI will still fail to respond after switching to the lock screen with Ctrl+Alt+F1 and I will need to reboot the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1816896/+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 1801782]
Yes. CustomizeMyBird seems to be causing the problem. SafeMode is fine.
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Invalid
Status in thunderbird package in Ubuntu:
Invalid
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
OK. I had a thought.
Started in Safe Mode - all is OK.
So I then went around disabling all extensions and *as I disabled one* the
window maximized width-wise.
That extension is: CustomizeMyBird.
So I'll report the issue there instead.
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
New
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
I can't find any way to close this report. Please do so...
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
New
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
I only see this with Thunderbird.
I don't see it with any other application.
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
New
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
FYI: As I shut-down Thunderbird teh .xsessions-erros file gets these
entries.
==
1549728585353 addons.xpi WARNException running bootstrap method
shutdown on menuon...@agrude.com: ReferenceError: windows is not defined
(chrome://shimmenuontopecma/content/menuontop_shim.jsm:30:1) JS Stack trace:
stopWindows@menuontop_shim.jsm:30:1
shutdown@resource://gre/modules/addons/XPIProvider.jsm ->
jar:file:///local/users/gml4410/.thunderbird/448skcjj.default/extensions/menuon...@bootstrap.js:125:2
callbootstrapmet...@xpiprovider.jsm:4446:20
obse...@xpiprovider.jsm:2293:13
goquitapplicat...@globaloverlay.js:56:3
oncomm...@messenger.xul:1:1
JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2733:
TypeError: this._parentMenupopup is null
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46190, resource
id: 81788945, major code: 15 (QueryTree), minor code: 0
kdeinit5: PID 15566 terminated.
==
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
New
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
>> Expected results:
>>
>> The main window should not have been maximised on restart.
The main window should not have been maximized on shut-down in the first
place!
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in Mozilla Thunderbird:
Confirmed
Status in thunderbird package in Ubuntu:
New
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1801782/+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 1801782] Re: Main window maximizes width on the closing appplication.
Yes, this still happens with 60.4.0.
--
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/1801782
Title:
Main window maximizes width on the closing appplication.
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
If I close thunderbird using File->Quit (or ctrl+Q) the window
maximizes to the screen width just before it closes and retains that
max-width on the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather
removes the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1801782/+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 1801782] [NEW] Main window maximizes width on the closing appplication.
Public bug reported:
If I close thunderbird using File->Quit (or ctrl+Q) the window maximizes
to the screen width just before it closes and retains that max-width on
the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather removes
the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44102178 F pulseaudio
/dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to cosmic on 2018-10-24 (12 days ago)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_55SU1,SUW
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Clevo
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnClevo:pnW54_55SU1,SUW:pvrNotApplicable:rvnCLEVO:rnW54_55SU1,SUW:rvrNotApplicable:cvnClevo:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W54_55SU1,SUW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Clevo
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
** Description changed:
If I close thunderbird using File->Quit (or ctrl+Q) the window maximizes
to the screen width just before it closes and retains that max-width on
the next restart.
- This does not happen if I close thunderbird with the window-managers
+ This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't normally run windows full-screen, as to me that rather removes
the usefulness of having a window system.)
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thunderbird 1:60.2.1+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: gml44102178 F pulseaudio
- /dev/snd/controlC1: gml44102178 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: gml44102178 F pulseaudio
+ /dev/snd/controlC1: gml44102178 F pulseaudio
BuildID: 20181011091051
Channel: Unavailable
CurrentDesktop: KDE
Date: Mon Nov 5 19:55:37 2018
ForcedLayersAccel: False
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
IncompatibleExtensions:
- Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
- Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
+ Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
+ Microbird - {59EAEC94-299A-43E3-BBE4-090880139DAA}
InstallationDate: Installed on 2017-11-01 (369 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
IpRoute:
- default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
- 169.254.0.0/16 dev wlp2s0 scope link metric 1000
- 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
+ default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
+ 169.254.0.0/16 dev wlp2s0 scope link metric 1000
+ 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use)
[Desktop-packages] [Bug 1798888] Re: Displays shows only one display
Which is to say this is more of a usability issue than a "this functionality is unavailable." -- 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/179 Title: Displays shows only one display Status in gnome-control-center package in Ubuntu: Opinion Bug description: Upon upgrading from 18.04 to 18.10, only one of my displays is working. Only one display shows in control centre. I have two, one connected via DisplayPort, one via VGA. The VGA works, DP doesn't. If I unplug the VGA display, then the DisplayPort display turns on. Plug it back in, the DisplayPort display turns off. XRANDR shows both displays. Confusingly, the VGA display appears as "DP-2" in XRANDR, and the DisplayPort connected display shows as "HDMI-1." If I manually enable the second display with xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080 then the second display starts to work, and it appears in the Displays section of the control centre, as it used to in Ubuntu 18.04. Here's the output of xrandr prior to manually enabling the second display: donald@silver:~$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS-1 connected (normal left inverted right x axis y axis) 1600x900 60.06 + 59.9959.9459.9559.8240.04 1440x900 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 74.9359.91 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 1600x1200 60.00 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.89 1280x960 60.00 1280x800 74.9359.81 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-3 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 08:10:51 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-08-13 (67 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1798888] Re: Displays shows only one display
OK so I've just found out where my extra displays were hiding. The Button that says 3 Viewsonic Corp ... can be clicked on to choose another monitor. ** Changed in: gnome-control-center (Ubuntu) Status: New => Opinion -- 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/179 Title: Displays shows only one display Status in gnome-control-center package in Ubuntu: Opinion Bug description: Upon upgrading from 18.04 to 18.10, only one of my displays is working. Only one display shows in control centre. I have two, one connected via DisplayPort, one via VGA. The VGA works, DP doesn't. If I unplug the VGA display, then the DisplayPort display turns on. Plug it back in, the DisplayPort display turns off. XRANDR shows both displays. Confusingly, the VGA display appears as "DP-2" in XRANDR, and the DisplayPort connected display shows as "HDMI-1." If I manually enable the second display with xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080 then the second display starts to work, and it appears in the Displays section of the control centre, as it used to in Ubuntu 18.04. Here's the output of xrandr prior to manually enabling the second display: donald@silver:~$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS-1 connected (normal left inverted right x axis y axis) 1600x900 60.06 + 59.9959.9459.9559.8240.04 1440x900 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 74.9359.91 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 1600x1200 60.00 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.89 1280x960 60.00 1280x800 74.9359.81 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-3 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 08:10:51 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-08-13 (67 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center
[Desktop-packages] [Bug 1798888] [NEW] Displays shows only one display
Public bug reported: Upon upgrading from 18.04 to 18.10, only one of my displays is working. Only one display shows in control centre. I have two, one connected via DisplayPort, one via VGA. The VGA works, DP doesn't. If I unplug the VGA display, then the DisplayPort display turns on. Plug it back in, the DisplayPort display turns off. XRANDR shows both displays. Confusingly, the VGA display appears as "DP-2" in XRANDR, and the DisplayPort connected display shows as "HDMI-1." If I manually enable the second display with xrandr --output HDMI-1 --right-of DP-2 --mode 1920x1080 then the second display starts to work, and it appears in the Displays section of the control centre, as it used to in Ubuntu 18.04. Here's the output of xrandr prior to manually enabling the second display: donald@silver:~$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS-1 connected (normal left inverted right x axis y axis) 1600x900 60.06 + 59.9959.9459.9559.8240.04 1440x900 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 74.9359.91 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 1600x1200 60.00 1680x1050 59.95 1280x1024 75.0260.02 1440x900 59.89 1280x960 60.00 1280x800 74.9359.81 1152x864 75.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 DP-3 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 08:10:51 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-08-13 (67 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- 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/179 Title: Displays shows only one display Status in gnome-control-center package in Ubuntu: New Bug description: Upon upgrading from 18.04 to 18.10, only one of my displays is working. Only one display shows in control centre. I have two, one connected via DisplayPort, one via VGA. The VGA works, DP doesn't. If I
[Desktop-packages] [Bug 976638] Re: pkexec does not find any authentication agent
Found the answer - I needed to install lxsession-edit, and that gives me the "Policykit Authentication Agent" tickbox. Now all is well. One oddity though: on a fresh install of Lubuntu 18.04, everything works as expected - yet the Policykit Authentication Agent box is unchecked... Can anyone explain? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in PolicyKit: Unknown Status in policykit-1 package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+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 976638] Re: pkexec does not find any authentication agent
This looks like the problem I have in Lubuntu 18.04 (but only in systems upgraded from 16.04 - new installs seem fine). But I can't find the magic "Policykit Authentication Agent" tickbox in Lubuntu: where is it hiding? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in PolicyKit: Unknown Status in policykit-1 package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+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 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Unfortunately my possible workaround in comments 3 & 4 only partially work - cups stops prompting for a password but its smb backend (/usr/lib/x86_64-linux-gnu/samba/smbspool_krb5_wrapper) does not receive the AUTH_UID is not set and therefore cannot spool the job the a Windows print server. I'm assuming that AUTH_UID can only be set if using a domain socket connection rather than a localhost connection to the cups daemon. The patch I propose in comment 5 does appear to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+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 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Here is my proposed solution (attached) to the problem - I do not claim to fully understand cups' authentication system but it seems to me from looking at the old code to cups/auth.c and the new broken code that this patch would make the unix domain socket authentication work the same as it did before: ** Patch added: "proposed_solution.patch" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+attachment/5170387/+files/proposed_solution.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+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 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
My suggested work around above does not fix the issue (completely) because systemd is in charge of the socket - so as well as commenting out "Listen /run/cups/cups.sock" in /etc/cups/cupsd.conf you have to also do the following: systemctl stop cups.service systemctl stop cups.socket rm /run/cups/cups.sock systemctl disable cups.socket systemctl start cups.service -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+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 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
It appears that it first stops working in cups version 2.2.7 when there is a major change in cups/auth.c. It is still broken in the current cups github repo master branch. I have noticed it works correctly if you disable the unix domain socket, e.g. comment out Listen /run/cups/cups.sock in /etc/cups/cupsd.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+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 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
The above setup work fine in Ubuntu 17.10 as well which uses cups 2.2.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+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 1783298] [NEW] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Public bug reported: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS /hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian.
[Desktop-packages] [Bug 1758761] Re: In 59.0.1 the Bookmarks button on Customize page raises invisible menu
TROUBLESHOOTING INFORMATION:
Application Basics
--
Name: Firefox
Version: 59.0.1
Build ID: 20180316021607
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101
Firefox/59.0
OS: Linux 4.13.0-37-generic
Multiprocess Windows: 1/1 (Enabled by default)
Web Content Processes: 3/4
Stylo: content = true (enabled by default), chrome = false (disabled by default)
Google Key: Found
Mozilla Location Service Key: Missing
Safe Mode: false
Firefox Features
Name: Activity Stream
Version: 2018.02.17.0026-173e2795
ID: activity-str...@mozilla.org
Name: Application Update Service Helper
Version: 2.0
ID: aushel...@mozilla.org
Name: Firefox Screenshots
Version: 25.0.0
ID: screensh...@mozilla.org
Name: Follow-on Search Telemetry
Version: 0.9.6
ID: followonsea...@mozilla.com
Name: Form Autofill
Version: 1.0
ID: formautof...@mozilla.org
Name: Photon onboarding
Version: 1.0
ID: onboard...@mozilla.org
Name: Pocket
Version: 1.0.5
ID: fire...@getpocket.com
Name: Shield Recipe Client
Version: 80
ID: shield-recipe-cli...@mozilla.org
Name: Web Compat
Version: 1.1
ID: webcom...@mozilla.org
Extensions
--
Name: RescueTime for Firefox
Version: 3.1.4
Enabled: true
ID: rescuetime_fire...@rescuetime.com
Name: Video DownloadHelper
Version: 7.1.1
Enabled: true
ID: {b9db16a4-6edc-47ec-a1f4-b86292ed211d}
Security Software
- Type:
Type:
Type:
Graphics
Features
Compositing: Basic
Asynchronous Pan/Zoom: wheel input enabled; scrollbar drag enabled; keyboard
enabled; autoscroll enabled
WebGL 1 Driver WSI Info: GLX 1.4 GLX_VENDOR(client): Mesa Project and SGI
GLX_VENDOR(server): SGI Extensions: GLX_ARB_create_context
GLX_ARB_create_context_profile GLX_ARB_create_context_robustness
GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address
GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info
GLX_EXT_visual_rating GLX_EXT_fbconfig_packed_float GLX_EXT_framebuffer_sRGB
GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile
GLX_MESA_copy_sub_buffer GLX_MESA_multithread_makecurrent
GLX_MESA_query_renderer GLX_MESA_swap_control GLX_OML_swap_method
GLX_OML_sync_control GLX_SGI_make_current_read GLX_SGI_swap_control
GLX_SGI_video_sync GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer
GLX_SGIX_visual_select_group GLX_EXT_texture_from_pixmap GLX_INTEL_swap_event
GLX_EXT_buffer_age
WebGL 1 Driver Renderer: X.Org -- AMD Radeon (TM) R9 390 Series (AMD HAWAII /
DRM 3.20.0 / 4.13.0-37-generic, LLVM 5.0.1)
WebGL 1 Driver Version: 3.0 Mesa 17.2.4-AMD_17.50
WebGL 1 Driver Extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra
GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract
GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture
GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array
GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters
GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters
GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp
GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp
GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture
GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays
GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add
GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord
GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add
GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias
GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent
GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc
GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression
GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc
GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos
GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture
GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3
GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader
GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp
GL_NV_fog_distance GL_APPLE_packed_pixels GL_ARB_draw_buffers
GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects
GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers
GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_depth_bounds_test
GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert
GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow
GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite
GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two
GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate
GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float
GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc
[Desktop-packages] [Bug 1758761] [NEW] In 59.0.1 the Bookmarks button on Customize page raises invisible menu
Public bug reported: When downloading the FF version from "ftp.mozilla.org/pub/firefox/releases/59.0.1/linux-x86_64/en-US/" I get a browser with a normally functioning button. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "attachment.png" https://bugs.launchpad.net/bugs/1758761/+attachment/5090542/+files/attachment.png -- 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/1758761 Title: In 59.0.1 the Bookmarks button on Customize page raises invisible menu Status in firefox package in Ubuntu: New Bug description: When downloading the FF version from "ftp.mozilla.org/pub/firefox/releases/59.0.1/linux-x86_64/en-US/" I get a browser with a normally functioning button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758761/+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 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Ed's solution also worked for me: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/comments/14. A very simple solution, just copy and paste a single command -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master 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: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+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 1617204] Re: NM does not offer VPN options
Solved. Turns out Lubuntu also needs network-manager-pptp-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617204 Title: NM does not offer VPN options Status in network-manager package in Ubuntu: New Bug description: network-manager-pptp is installed, but when I select "Configure VPN" NM offers only Hardware and Virtual options, no VPN options., Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything works as expected on Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Aug 26 09:05:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-08 (17 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IpRoute: default via 172.16.0.27 dev wlp2s0 proto static metric 600 172.16.0.0/16 dev wlp2s0 proto kernel scope link src 172.16.0.182 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617204/+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 1617204] [NEW] NM does not offer VPN options
Public bug reported: network-manager-pptp is installed, but when I select "Configure VPN" NM offers only Hardware and Virtual options, no VPN options., Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything works as expected on Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Aug 26 09:05:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-08 (17 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IpRoute: default via 172.16.0.27 dev wlp2s0 proto static metric 600 172.16.0.0/16 dev wlp2s0 proto kernel scope link src 172.16.0.182 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1617204 Title: NM does not offer VPN options Status in network-manager package in Ubuntu: New Bug description: network-manager-pptp is installed, but when I select "Configure VPN" NM offers only Hardware and Virtual options, no VPN options., Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything works as expected on Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Aug 26 09:05:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-08 (17 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IpRoute: default via 172.16.0.27 dev wlp2s0 proto static metric 600 172.16.0.0/16 dev wlp2s0 proto kernel scope link src 172.16.0.182 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617204/+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 1536409] Re: gimp move by holding space bar does not terminate
Same version, same problem, not running fullscreen mode. Cannot escape hangup because the mouse and graphics tablet inputs continue to be captured (I assume). When I signed on from another computer via ssh and killed the Gimp process, everything else appeared to resume running normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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 1585923] [NEW] cupsd leaves sockets in CLOSE_WAIT if client uses kerberos authentication
Public bug reported: In Ubuntu 16.04 using cups version 2.1.3-4 the cups daemon leaves tcp sockets in CLOSE_WAIT state if a client uses kerberos authentication with encryption (the default for authenticated connections). cupds will then also consume 100% of a CPU. The impact of this bug is that after a few hours cupsd stops accepting new connections as it runs out of sockets. (This can be slowed down by increasing the open files limit and setting MaxClients to a much higher number) This bug does not exist in cups 1.5.3-0ubuntu8.7 on Ubuntu 12.04. To replicate: Cups server requires kerberos authentication. Cups client runs 'lpstat -h cupserver.domain -v' after obtaining valid kerberos credentials. The cups daemon will then have a connection in CLOSE_WAIT state (according to netstat). In cupsd debug mode the client rapidly logs thousands of: D [24/May/2016:11:49:17 +0100] [Client 29] Read: status=100 The debug error_log for a connection is: D [24/May/2016:11:49:17 +0100] cupsdSetBusyState: newbusy="Not busy", busy="Not busy" D [24/May/2016:11:49:17 +0100] [Client 29] Accepted from AAA.BBB.CCC.DDD:40678 (IPv4) D [24/May/2016:11:49:17 +0100] [Client 29] Waiting for request. D [24/May/2016:11:49:17 +0100] [Client 29] OPTIONS * HTTP/1.1 D [24/May/2016:11:49:17 +0100] cupsdSetBusyState: newbusy="Active clients", busy="Not busy" D [24/May/2016:11:49:17 +0100] [Client 29] Read: status=200 D [24/May/2016:11:49:17 +0100] [Client 29] No authentication data provided. D [24/May/2016:11:49:17 +0100] [Client 29] cupsdSendHeader: code=101, type="(null)", auth_type=0 D [24/May/2016:11:49:17 +0100] [Client 29] Connection now encrypted. D [24/May/2016:11:49:17 +0100] [Client 29] cupsdSendHeader: code=200, type="(null)", auth_type=0 D [24/May/2016:11:49:17 +0100] cupsdSetBusyState: newbusy="Not busy", busy="Active clients" D [24/May/2016:11:49:17 +0100] [Client 29] POST / HTTP/1.1 D [24/May/2016:11:49:17 +0100] cupsdSetBusyState: newbusy="Active clients", busy="Not busy" D [24/May/2016:11:49:17 +0100] [Client 29] Read: status=200 D [24/May/2016:11:49:17 +0100] [Client 29] No authentication data provided. D [24/May/2016:11:49:17 +0100] cupsdIsAuthorized: username="" D [24/May/2016:11:49:17 +0100] [Client 29] cupsdSendHeader: code=401, type="text/html", auth_type=0 D [24/May/2016:11:49:17 +0100] [Client 29] WWW-Authenticate: Negotiate D [24/May/2016:11:49:17 +0100] [Client 29] Closing connection. D [24/May/2016:11:49:17 +0100] cupsdSetBusyState: newbusy="Not busy", busy="Active clients" D [24/May/2016:11:49:17 +0100] [Client 29] Waiting for socket close. D [24/May/2016:11:49:17 +0100] [Client 29] Read: status=100 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CupsErrorLog: Date: Thu May 26 08:20:33 2016 InstallationDate: Installed on 2016-04-25 (30 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) KernLog: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/cups2016--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-trusty dmi.sys.vendor: QEMU ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1585923 Title: cupsd leaves sockets in CLOSE_WAIT if client uses kerberos authentication Status in cups package in Ubuntu: New Bug description: In Ubuntu 16.04 using cups version 2.1.3-4 the cups daemon leaves tcp sockets in CLOSE_WAIT state if a client uses kerberos authentication with encryption (the default for authenticated connections). cupds will then also consume 100% of a CPU. The impact of this bug is that after a few hours cupsd stops accepting new connections as it runs out of sockets. (This can be slowed down by increasing the open files limit and setting MaxClients to a much higher number) This bug does not exist in cups 1.5.3-0ubuntu8.7 on Ubuntu 12.04. To replicate: Cups server requires kerberos authentication. Cups client runs 'lpstat -h cupserver.domain -v' after obtaining valid kerberos credentials. The cups daemon will then have a connection in CLOSE_WAIT state (according to netstat). In cupsd debug mode the client
[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash
i've had the same issue with most every app that I've tried to install. I find that installing instead via Synaptic does seem to be a reliable workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in Unity: Incomplete Status in gnome-menus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1536409] Re: gimp move by holding space bar does not terminate
I should add that the problem is intermittent -- not seen often. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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 1536409] [NEW] gimp move by holding space bar does not terminate
Public bug reported: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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
