[Desktop-packages] [Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
** Description changed: This is a freeze which is obviously caused by a bug in the xserver-xorg- video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: - sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eon" or "disco" to "bionic" (for this line only) + sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eoan" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) Status in Linux: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: This is a freeze which is obviously caused by a bug in the xserver- xorg-video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eoan" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- Mailing list: https://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 1835703] Re: package gnome-shell 3.28.4-0ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1835703 Title: package gnome-shell 3.28.4-0ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-shell package in Ubuntu: Expired Bug description: I have no idea but i got some error while upgrading by: sudo apt upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.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 AptOrdering: systemd:amd64: Install libsystemd0:amd64: Install libsystemd0:amd64: Configure gdm3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 8 22:25:10 2019 DisplayManager: gdm3 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GsettingsChanges: InstallationDate: Installed on 2019-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: gnome-shell Title: package gnome-shell 3.28.4-0ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1835703/+subscriptions -- Mailing list: https://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 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
For anyone who is still having this problem, hopefully this will help you get your webcam working. I was able to get my webcam working and I am using a Dell Precision 7510 Laptop running Ubuntu 18.04.3. 1.) I issued "$dmesg | grep -i camera" in a terminal window and received "uvcvideo 1-11:1.0: Entity type for entity Camera 1 was not initialized!" which landed me here at this website (FYI I am still receiving that message and my camera works... as laurent.pinchart +bugzilla-kernel pointed out already it is a harmless warning). 2) I did a search for "ubuntu uvcvideo" in google and landed on "https://help.ubuntu.com/community/UVC; which then pointed me to "https://www.berlios.de/software/linux-uvc/#download; which then pointed me to "http://www.ideasonboard.org/uvc/;. 3) From "http://www.ideasonboard.org/uvc/;, if you scroll down to the bottom of it you will see a Downlaod section. Navigate to the "https://www.linuxtv.org/wiki/index.php/How_to_Obtain; webpage and follow the "Basic" User's Approach instructions. 4) You may be asked to install pre-requisites during the build process. I had to issue the following command "$sudo apt install libproc- processtable-perl". 5) Once build is complete, run "$sudo make install". 6) I installed uvcdynctrl as floe suggested. I don't know if this helped or not sorry... 7) I then found and example file to test if the camera was working from "https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/v4l2grab.c.html;. I saved this file and tried to compile it "$gcc -o v4l2grab v4l2grab.c" and received an error that it couldn't find the libv4l2.h header file. So i searched for it using $sudo find / -name "libv4l2.h" and didn't find it. This led me to believe that I didn't have the v4l2 development library installed so I installed it $sudo apt install libv4l-dev. 8) I searched again and found it! I then set C include environment path variable to point to the directory containing the header file $export C_INCLUDE_PATH=/usr/include/ and changed #include "../libv4l/include/libv4l2.h" to just #include "libv4l2.h" 9) Tried to recompile and got a linking error, so I issued $gcc -o v4l2grab v4l2grab.c -lv4l1 -lv4l2 and waula, it compiled. Changed its permssions to be executable $chmod +755 v4l2grab (using octal format where 7 in binary is 111 corresponding to rwx for owner and 5 or 110 rw- for group and other) and ran it ./v4l2grab where then I saw the .ppm files in the directory where the executable was ran from, but this was not good enough I want live feed. 10) I then installed v4l-utils and ran $v4l2-ctl -d /dev/video0 --list- formats-ext. This gave me the parameters that are compatible with my webcam for video capture (width=1280, height=720, format=MJPG, and device index=0). 11) As a final death blow I ran the following v4l2-ctl -V --set-fmt-video=width=1280,height=720,pixelformat=MJPG --stream-mmap --stream-count=-1 --stream-to=test.jpg -d /dev/video0 but only got a single image. I think you need to incude OpenCV. Anyways, I hope this helps you atleast get images off of the webcam. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Desktop-packages] [Bug 1801540]
(In reply to Takashi Iwai from comment #273) > Hmm, would it be only about playback? That is, restricting the workaround > only to capture stream works better? > > --- a/sound/pci/hda/hda_controller.c > +++ b/sound/pci/hda/hda_controller.c > @@ -617,7 +617,8 @@ static int azx_pcm_open(struct snd_pcm_substream > *substream) > * tsched=1 when a capture stream triggers. Until we figure out the > * real cause, disable tsched mode by telling the PCM info flag. > */ > - if (chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) > + if ((chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) && > + substream->stream == SNDRV_PCM_STREAM_CAPTURE) > runtime->hw.info |= SNDRV_PCM_INFO_BATCH; > > if (chip->align_buffer_size) > > > In anyway, we need to know this change makes sense at all. IOW, people need > to check whether this causes yet another regression on the devices that have > worked with BATCH workaround. With the standard flags, Discord is perfect, Steam has stutters for the first minute and a bit of delay (500 ms). With the batch flag only on the capture stream, Steam is perfect, Discord has delayed audio. With the batch flag only on the playback stream, same thing with both of them (first case). -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://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 1801540]
Following my previous post, disabling the batch flag on both streams (patch 3 from comment 269), Steam is perfect, Discord is lagged again while acquiring. With the second patch from the comment 269, same identical problem without the patch (Discord perfect, Steam crackling for the first minute + audio slightly delayed). However when changing volume there was a little bit of distortion on the output audio (extremely small, but still audible, especially on high volumes), but it seems that using the workaround only on acquisition seems to have removed that small issue. If someone here had the same problem when changing volume, please try patch n.2 and report back. It seems that we can't have both working together simultaneously on my end. The default workaround is still the best option on my system, for now. -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://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 1840597] Re: Web Extension API, `browser.search.get` throws error `An unexpected error occurred`
Thanks osomon! This is so much better. Fixed in 69.0+build2-0ubuntu0.18.04.1. -- 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/1840597 Title: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Web Extension API, `browser.search.get` throws error `An unexpected error occurred` on ubuntu's version of firefox 68 Steps to reproduce 1. Extract attached ff-extensions.zip 2. In the extracted folder, run `web-ext run` 3. In address bar type about:debugging. Temporary extensions 'Test Extension' will be loaded. 4. Click 'Debug' It gives an error in console tab, Error: "An unexpected error occurred" This issue is reproducible only with the Firefox installations from 'Ubuntu Software', not with the Firefox downloads from Mozilla's page. This is the possible root cause for "Tridactyl is broken on ubuntu's version of firefox 68", see https://github.com/tridactyl/tridactyl/issues/1670 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 68.0.1+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anoop 2183 F pulseaudio BuildID: 20190718135155 Channel: Unavailable CurrentDesktop: Unity Date: Mon Aug 19 01:09:47 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-08 (587 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.100 metric 600 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=69.0/20190807220259 (Out of date) Profile0 (Default) - LastVersion=68.0.1/20190718135155 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to xenial on 2018-09-10 (342 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0G0G6Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd08/07/2017:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0G0G6Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1840597/+subscriptions -- Mailing list: https://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 1842954]
Hi, Have you tried reverting the xorg amdgpu package to an older version? Of course that is just a workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) Status in Linux: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: This is a freeze which is obviously caused by a bug in the xserver- xorg-video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eon" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- Mailing list: https://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 1792085] Re: MTP not working/very slow on Bionic
How is this not fixed a year later? Whatever people are working on for the next release that they feel is sexy I hate it. Instead please fix bugs which make the existing system unusable. Then you will be my hero. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.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 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://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 1843107] [NEW] Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
Public bug reported: After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to 3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome- tweaks are no longer applied to X11 applications when running in a Wayland session (I tried Firefox and Emacs). This seems to be because gsd-xsettings is not running. Known workarounds: • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or • use Xorg instead of Wayland; or • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.33.92-1ubuntu1 Uname: Linux 5.2.11-050211-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 6 17:24:02 2019 InstallationDate: Installed on 2016-02-19 (1295 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) Status in gnome-settings-daemon package in Ubuntu: New Bug description: After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to 3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome- tweaks are no longer applied to X11 applications when running in a Wayland session (I tried Firefox and Emacs). This seems to be because gsd-xsettings is not running. Known workarounds: • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or • use Xorg instead of Wayland; or • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.33.92-1ubuntu1 Uname: Linux 5.2.11-050211-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 6 17:24:02 2019 InstallationDate: Installed on 2016-02-19 (1295 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions -- Mailing list: https://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 1714504] Re: App indicator is not always displayed
Please nominate to Bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714504 Title: App indicator is not always displayed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Bug description: I've 2 apps that should be displayed in the indicator: - hp systray (from the package hplip-gui) - synology cloud client (download from synology) Sometimes the indicators are displayed and sometimes not. The extension is loaded and show no error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 14:57:16 2017 Dependencies: InstallationDate: Installed on 2013-09-03 (1458 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1714504/+subscriptions -- Mailing list: https://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 1757873] Re: Please port your package away from Qt 4
** Changed in: sni-qt (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sni-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757873 Title: Please port your package away from Qt 4 Status in sni-qt package in Ubuntu: New Status in sni-qt package in Debian: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1757873/+subscriptions -- Mailing list: https://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 1188569] Re: [SRU]Some keyboard shortcuts randomly stop working
well that's funny... I did 2x 1's... well that shows how tired I am! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: [SRU]Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: *Impact Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. *Test Case A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you * Regression potential None ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- Mailing list: https://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 1188569] Re: [SRU]Some keyboard shortcuts randomly stop working
I found a solution that works on Ubuntu 19.04... - Note: This is only for media keys (the keybindings that stop working for me) - Note: If you know a better way to set the keybindings to disabled then do that! ;) Steps: 1) Open Terminal and enter: "sudo apt install playerctl" then to be sure run "restart" 1) Go to settings 2) Find keyboard shortcuts (devices > keyboard) 3) Find play-pause under media and set it to: Ctrl+Shift+E or something you don't use (this is what I used) Explanation: you need to disable these shortcuts to actually use them (with playerctl) (Do this for each predefined media key keybinding, when you do it'll disable the last one done and they'll all be set to disabled except for one which is set to Ctrl+shift+E or whatever you chose) 4) Scroll to the bottom 6) Create a new custom keyboard shortcut 7) Set the name according to which action you desire, set the command to something similar to: "playerctl pause-play --player=spotify" more documentation can be found here: https://github.com/altdesktop/playerctl 8) Repeat steps 5-7 for each media key & modify the command accordingly (see Github link) 9) Create a new keyboard shortcut called deleteMe 1.0 10) Bind this to whatever you chose earlier (Ctrl+shift+E is what I used) 11) Now delete it! Ha, bet you didn't see that one coming! Anyways now all the media keys above should be set to disabled, now use your newly invigorated keybindings with ease! ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: [SRU]Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: *Impact Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. *Test Case A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you * Regression potential None ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- Mailing list: https://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 1767749] Re: wrote report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak-ng.110.crash
** Also affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1767749 Title: wrote report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak- ng.110.crash Status in Ubuntu MATE: Invalid Status in speech-dispatcher package in Ubuntu: New Bug description: Ubuntu MATE 18.04 LTS (Japanese environment) Turn on the power and display the login screen. Click the doll icon (Accessibility) on the upper right of the screen with the left mouse button. Turn on "Screen reader" and "On-screen keyboard". I intentionally made a wrong input with the keyboard on the screen. Turn off "on-screen keyboard". I intentionally made a wrong input with the keyboard. I repeat this several times. I turned off "screen reader" and "on-screen keyboard". I logged in. When Ubuntu MATE Welcome is displayed, an internal error (crash) has been reported. Trying the same thing, there are times when it does not occur, but sometimes it happens. --- /var/log/apport.log： ERROR: apport (pid 1244) Sun Apr 29 10:51:44 2018: called for pid 1211, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 1244) Sun Apr 29 10:51:44 2018: executable: /usr/lib/speech-dispatcher-modules/sd_espeak-ng (command line "/usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf") ERROR: apport (pid 1244) Sun Apr 29 10:51:44 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 1244) Sun Apr 29 10:51:44 2018: debug: session gdbus call: ERROR: apport (pid 1244) Sun Apr 29 10:51:49 2018: wrote report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak-ng.110.crash ERROR: apport (pid 1282) Sun Apr 29 10:52:03 2018: called for pid 1261, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 1282) Sun Apr 29 10:52:03 2018: executable: /usr/lib/speech-dispatcher-modules/sd_espeak-ng (command line "/usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf") ERROR: apport (pid 1282) Sun Apr 29 10:52:03 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 1282) Sun Apr 29 10:52:03 2018: debug: session gdbus call: ERROR: apport (pid 1282) Sun Apr 29 10:52:03 2018: apport: report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak-ng.110.crash already exists and unseen, doing nothing to avoid disk usage DoS ERROR: apport (pid 1352) Sun Apr 29 10:53:33 2018: called for pid 1329, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 1352) Sun Apr 29 10:53:33 2018: executable: /usr/lib/speech-dispatcher-modules/sd_espeak-ng (command line "/usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf") ERROR: apport (pid 1352) Sun Apr 29 10:53:33 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 1352) Sun Apr 29 10:53:33 2018: debug: session gdbus call: ERROR: apport (pid 1352) Sun Apr 29 10:53:33 2018: apport: report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak-ng.110.crash already exists and unseen, doing nothing to avoid disk usage DoS --- ERROR: apport (pid 5595) Sun Apr 29 12:04:33 2018: called for pid 5567, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 5595) Sun Apr 29 12:04:33 2018: executable: /usr/lib/speech-dispatcher-modules/sd_espeak-ng (command line "/usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf") ERROR: apport (pid 5595) Sun Apr 29 12:04:33 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 5595) Sun Apr 29 12:04:33 2018: debug: session gdbus call: ERROR: apport (pid 5595) Sun Apr 29 12:04:34 2018: wrote report /var/crash/_usr_lib_speech-dispatcher-modules_sd_espeak-ng.110.crash ERROR: apport (pid 5635) Sun Apr 29 12:05:07 2018: called for pid 5614, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 5635) Sun Apr 29 12:05:07 2018: executable: /usr/lib/speech-dispatcher-modules/sd_espeak-ng (command line "/usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf") ERROR: apport (pid 5635) Sun Apr 29 12:05:07 2018: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
[Desktop-packages] [Bug 1768920] Re: 2 WiFi Icons in the Panel after installation of 18.04
This should be fixed in ubuntu-mate-settings (19.10.2) which is part of Ubuntu MATE 19.10. ** Also affects: ubuntu-mate-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: Confirmed => Invalid ** Changed in: ubuntu-mate-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1768920 Title: 2 WiFi Icons in the Panel after installation of 18.04 Status in Ubuntu MATE: Invalid Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Fix Released Bug description: After installing Ubuntu Mate 18.04, on the First login it shows 2 WiFi icons in the top panel. It goes away after the reboot though. My Laptop: Dell XPS 13 9370 Developer Edition, 16 GB RAM and 1 TB SSD Regards, Saurabh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1768920/+subscriptions -- Mailing list: https://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 1141034]
In Writer we use Left/Top, Right/Bottom for paragraph style > alignment depending on horizontal/vertical direction. The dynamic label might be not so easy to implement. How about "Shift forward" and backward for left/right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1141034 Title: RTL Spreadsheet Insert Cells Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: When using a right-to-left spreadsheet, right clicking and selected "insert cells" shows the normal LTR option to shift cells right, although when used it actually shifts cells left. I believe that shifting cells left is the correct behaviour in this case, but the text of the option should be changed to read "shift cells left". This was first noticed when using the Hebrew language user interface, but the problem is present when using English UI too. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd Date: Sun Mar 3 00:47:21 2013 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1141034/+subscriptions -- Mailing list: https://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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
With GNOME Shell 3.33.91: gpaste 3.30.2-1ubuntu3 (universe) gnome-shell-extension-suspend-button 0~git20180827-2 (universe) Both marked as "Error loading extension" in Tweaks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- Mailing list: https://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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-dashtodock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- Mailing list: https://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 1843083] Re: tracker-store crashed with SIGSEGV
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1843083 Title: tracker-store crashed with SIGSEGV Status in tracker package in Ubuntu: New Bug description: I din't know about ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: tracker 2.2.99.0-1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 6 20:15:58 2019 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2016-02-29 (1284 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcCmdline: /usr/lib/tracker/tracker-store ProcEnviron: LANG=ca_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=ca SegvAnalysis: Segfault happened at: 0x55affda50c33:cmpq $0x0,0x8(%rdi) PC (0x55affda50c33) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: () () tracker_data_commit_transaction () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () Title: tracker-store crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-07-30 (37 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1843083/+subscriptions -- Mailing list: https://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 1843044] Re: firefox crashes on a FIPS enabled machine
debdiff.xenial ** Attachment added: "debdiff.xenial" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+attachment/5287138/+files/debdiff.xenial -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundles nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- Mailing list: https://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 1843044] Re: firefox crashes on a FIPS enabled machine
debdiff.bionic ** Attachment added: "debdiff.bionic" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+attachment/5287139/+files/debdiff.bionic -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundles nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- Mailing list: https://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 1843044] Re: firefox crashes on a FIPS enabled machine
debdiff.eoan ** Attachment added: "debdiff.eoan" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+attachment/5287141/+files/debdiff.eoan ** Description changed: [IMPACT] - firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. + firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundles nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] - This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox nss is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. + This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundles nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine
[Desktop-packages] [Bug 1843044] Re: firefox crashes on a FIPS enabled machine
debdiff.disco ** Attachment added: "debdiff.disco" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+attachment/5287140/+files/debdiff.disco -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundles nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- Mailing list: https://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 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
I'm on Fedora 30 and also experiencing this. Dual monitors (one rotated, portrait right) on Wayland, but not using any scaling. Happens every time when waking up from sleep. AMD Vega 56 graphics card. Bug report (not by me) on Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1745055 ** Bug watch added: Red Hat Bugzilla #1745055 https://bugzilla.redhat.com/show_bug.cgi?id=1745055 -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock Status in mutter package in Ubuntu: New Bug description: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description: Ubuntu 19.04 Release: 19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-08 (178 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Tags: wayland-session disco Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-04-21 (134 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- Mailing list: https://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 130997] Re: Non-Linux hidden files like Thumbs.db should be treated the same as .filename
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nemo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/130997 Title: Non-Linux hidden files like Thumbs.db should be treated the same as .filename Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Status in nemo package in Ubuntu: Confirmed Status in Baltix: Invalid Bug description: Binary package hint: nautilus When a file is named .something in Linux, it's considered a hidden file, and Nautilus can be toggled to display these or not. I guess OS X uses the same convention, so .DS_Store and the like will not be shown? But other OSes don't, so we have things like Thumbs.db, desktop.ini, and so on. These should be treated exactly the same way by Nautilus; hidden from view until you toggle the "Show hidden files" option. Either by setting a blacklist of common filenames or by actually reading the hidden file attribute from NTFS/FAT/whatever. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/130997/+subscriptions -- Mailing list: https://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 1721704] Re: Printer settings stuck on loading drivers database
Still happening on 18.04 - slight difference - I can't get past the "Select Printer Driver" screen while "Loading drivers database..." and the swirling busy icon are up, so I don't have the printer at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1721704 Title: Printer settings stuck on loading drivers database Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1721704/+subscriptions -- Mailing list: https://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 1440372] Re: please port duplicity to Python3
the package still depends on python-lockfile. ** Changed in: duplicity (Ubuntu Eoan) Status: Fix Committed => New ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1440372 Title: please port duplicity to Python3 Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Status in duplicity source package in Eoan: New Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. deja-dup should be ported to Python3. There seems to be some progress upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1440372/+subscriptions -- Mailing list: https://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 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
** Attachment added: "output of ipptool -tv ipp://SAMSUNGC410W.local:631/ipp/printer get-printer-attributes.testoutput of" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+attachment/5287106/+files/ipp-attrs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" Status in system-config-printer package in Ubuntu: Expired Bug description: Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'". The error message is unhelpful and can't be copied. The output of the console is > system-config-printer (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_insert_after: assertion 'G_NODE (sibling->user_data)->parent == G_NODE (parent->user_data)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/newprinter.py", line 4196, in getNPPPD ppd = cups.PPD(f) RuntimeError: ppdOpenFile failed Continuing anyway.. which looks like the error message could be improved dramatically. The same issue happens for Driverless IPP. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: system-config-printer 1.5.7+20160812-0ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 28 14:40:51 2017 InstallationDate: Installed on 2015-12-12 (594 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: Gerät für HP_Color_LaserJet_MFP_M476dn: hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5 Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525 MachineType: LENOVO 20221 PackageArchitecture: all Papersize: a4 PpdFiles: QL-570: Brother QL-570 CUPS v1.1 HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: system-config-printer UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- Mailing list: https://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 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
I am affected by the same issue on Ubuntu 18.04.3 $ driverless ipp://SAMSUNGC410W.local:631/ipp/printer Logs are attachd. How can I futher investigate? ** Attachment added: "debug output of system-config-printer" https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+attachment/5287105/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" Status in system-config-printer package in Ubuntu: Expired Bug description: Adding a Hewlett-Packard HP Color LaserJet MFP M476dn as IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'". The error message is unhelpful and can't be copied. The output of the console is > system-config-printer (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_insert_after: assertion 'G_NODE (sibling->user_data)->parent == G_NODE (parent->user_data)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-CRITICAL **: gtk_tree_store_set_value: assertion 'VALID_ITER (iter, tree_store)' failed (system-config-printer.py:21002): Gtk-WARNING **: Failed to fetch network locations: Timeout was reached Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/newprinter.py", line 4196, in getNPPPD ppd = cups.PPD(f) RuntimeError: ppdOpenFile failed Continuing anyway.. which looks like the error message could be improved dramatically. The same issue happens for Driverless IPP. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: system-config-printer 1.5.7+20160812-0ubuntu9 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 28 14:40:51 2017 InstallationDate: Installed on 2015-12-12 (594 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: Gerät für HP_Color_LaserJet_MFP_M476dn: hp:/usb/HP_Color_LaserJet_MFP_M476dn?serial=CNB8H415Z5 Gerät für QL-570: usb://Brother/QL-570?serial=F4Z735525 MachineType: LENOVO 20221 PackageArchitecture: all Papersize: a4 PpdFiles: QL-570: Brother QL-570 CUPS v1.1 HP_Color_LaserJet_MFP_M476dn: HP Color LaserJet Pro MFP M476 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root SourcePackage: system-config-printer UpgradeStatus: Upgraded to zesty on 2017-05-01 (88 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- Mailing list: https://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 1843055] [NEW] Wine, Samba4 users, cups-pdf don't print 18.04
Public bug reported: Hi, In my company we have Ubuntu computer who user are login by Active Directory (with samba4) We use sssd to make the connection. My sssd configuration file: [sssd] services = nss, pam, autofs config_file_version = 2 domains = DOMAINE [domain/DOMAINE] id_provider = ad access_provider = ad override_homedir = /home/%u default_shell = /bin/bash cache_credentials = True krb5_store_password_if_offline = True ad_gpo_access_control = permissive krb5_ccname_template=FILE:%d/krb5cc_%U ldap_id_mapping = True use_fully_qualified_names = False fallback_homedir = /home/%u simple_allow_users = $ Everything was working fine until a minor upgrade (2.2.7-1ubuntu2.7 it was working well on 2.2.7-1ubuntu2.3). We use wine to run a windows software, but you can use the notepad as well. When a Active Directory is login, and try to print a PDF, is hown PDF file is not created, and no PDF inside. But if we try with a other software without wine, everything works well. Here the debug information: https://pastebin.com/VjMHBYBh Has you can see we have a line with: "unknown user: unknown" the problem look here. It's look cups don't receive the correct user. As I say before, no problem with local user wher we don't have this line but the good one with the correct username. So why Wine better than other package, because other don't have update until we pass from 2.2.7-1ubuntu2.3 to 2.2.7-1ubuntu2.7. If you have any idea it will be great. Thank's for helping. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: cups cups-pdf samba4 wine ** Tags added: wine ** Tags added: cups cups-pdf samba4 -- 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/1843055 Title: Wine, Samba4 users, cups-pdf don't print 18.04 Status in cups package in Ubuntu: New Bug description: Hi, In my company we have Ubuntu computer who user are login by Active Directory (with samba4) We use sssd to make the connection. My sssd configuration file: [sssd] services = nss, pam, autofs config_file_version = 2 domains = DOMAINE [domain/DOMAINE] id_provider = ad access_provider = ad override_homedir = /home/%u default_shell = /bin/bash cache_credentials = True krb5_store_password_if_offline = True ad_gpo_access_control = permissive krb5_ccname_template=FILE:%d/krb5cc_%U ldap_id_mapping = True use_fully_qualified_names = False fallback_homedir = /home/%u simple_allow_users = $ Everything was working fine until a minor upgrade (2.2.7-1ubuntu2.7 it was working well on 2.2.7-1ubuntu2.3). We use wine to run a windows software, but you can use the notepad as well. When a Active Directory is login, and try to print a PDF, is hown PDF file is not created, and no PDF inside. But if we try with a other software without wine, everything works well. Here the debug information: https://pastebin.com/VjMHBYBh Has you can see we have a line with: "unknown user: unknown" the problem look here. It's look cups don't receive the correct user. As I say before, no problem with local user wher we don't have this line but the good one with the correct username. So why Wine better than other package, because other don't have update until we pass from 2.2.7-1ubuntu2.3 to 2.2.7-1ubuntu2.7. If you have any idea it will be great. Thank's for helping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1843055/+subscriptions -- Mailing list: https://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 1843044] Re: firefox crash on a FIPS enabled machine
The build log and test runs for eoan build is on my test ppa https://launchpad.net/~vineetha/+archive/ubuntu/firefox-test/+build/17525936 The build log and test runs for disco build is on my test ppa https://launchpad.net/~vineetha/+archive/ubuntu/firefox-test/+build/17525851 The build log and test runs for bionic build is on my test ppa https://launchpad.net/~vineetha/+archive/ubuntu/test-ppa/+build/17524983 The build log and test runs for xenial build is on my test ppa https://launchpad.net/~vineetha/+archive/ubuntu/firefox-test/+build/17525924 ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Vineetha Kamath (vineetha) ** Summary changed: - firefox crash on a FIPS enabled machine + firefox crashes on a FIPS enabled machine -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox nss is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843044/+subscriptions -- Mailing list: https://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 1843044] [NEW] firefox crash on a FIPS enabled machine
Public bug reported: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description:Ubuntu Bionic Beaver Release:18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox nss is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1843044 Title: firefox crash on a FIPS enabled machine Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox nss is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no
[Desktop-packages] [Bug 1701243] Re: GDM does not work if gnome-session is not installed
** Changed in: gdm3 (Debian) Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1701243 Title: GDM does not work if gnome-session is not installed Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 package in Debian: New Bug description: Test Case = Install Ubuntu 17.10 from a recent daily image. After install log in. sudo apt install gdm3 Choose gdm3 when prompted. Restart your computer. The bug is that gdm refuses to start Workaround == Install gnome-session More Info = For smoother upgrades and to allow the option of a more vanilla GNOME experience, it was decided to try to continue to use an ubuntu-session package by default containing an "ubuntu" session that identifies as "Ubuntu" and runs GNOME. We don't want or need the GNOME sessions in the default install. This is more fallout from https://git.gnome.org/browse/gdm/commit/?id=f66cdfcb so let's try reverting that change. See also LP: #1686257 and https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=850291 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1701243/+subscriptions -- Mailing list: https://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 1832988] Re: Intel 8260 Bluetooth not working
Hi, sorry for the very late response. This now appears to be working with the stock kernel. I'll post version details later -- 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/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to:
[Desktop-packages] [Bug 1843039] [NEW] [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
Public bug reported: Sound doesn't work intermittently ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sab7713 F pulseaudio /dev/snd/pcmC0D0c: sab7713 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 14:07:06 2019 InstallationDate: Installed on 2019-09-03 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1843039 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Sound doesn't work intermittently ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sab7713 F pulseaudio /dev/snd/pcmC0D0c: sab7713 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 14:07:06 2019 InstallationDate: Installed on 2019-09-03 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1843039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6
On Fri, Sep 06, 2019 at 11:35:47AM -, Łukasz Zemczak wrote: > This looks good in overall. I trust that you are confident that the new > pango1.0 will migrate without any bigger issues, especially seeing how many > reverse-dependencies it has. I also hope there is no ABI break introduced in > the two new versions? The changelogs do not seem to mention anything > explicitly. Wouldn't want us to require additional rebuilds so late in the > cycle. > Have you tested the packages from the PPA? I'm running with them, it seems fine to me. I think I'd want to check with others in the desktop team before going ahead, though. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://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 1842643] Re: [ffe] Update to 1.44.6
This looks good in overall. I trust that you are confident that the new pango1.0 will migrate without any bigger issues, especially seeing how many reverse-dependencies it has. I also hope there is no ABI break introduced in the two new versions? The changelogs do not seem to mention anything explicitly. Wouldn't want us to require additional rebuilds so late in the cycle. Have you tested the packages from the PPA? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://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 1625944] Re: [Dell Precision 5510][Yakkety] built-in HDMI port does not work, no signal output
NVIDIA drier version 430.40 Quadro M1000M (GPU 0) -- 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/1625944 Title: [Dell Precision 5510][Yakkety] built-in HDMI port does not work, no signal output Status in xorg package in Ubuntu: Won't Fix Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) No signal output while plug the cable into built-in hdmi port. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 6.2.0 20160914 (Ubuntu 6.2.0-3ubuntu15) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 21 14:37:35 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e5] Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5] InstallationDate: Installed on 2016-09-19 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=a40a640b-1533-47a4-be70-98a11eb306bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.10:bd06/30/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Sep 21 11:46:07 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625944/+subscriptions -- Mailing list: https://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 1625944] Re: [Dell Precision 5510][Yakkety] built-in HDMI port does not work, no signal output
I just installed Ubuntu 19.04 on Dell PRECISION 5510 and hdmi do not work ➜ ~ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco ➜ ~ uname --all Linux precise 5.2.11-050211-generic #201908290731 SMP Thu Aug 29 07:33:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1625944 Title: [Dell Precision 5510][Yakkety] built-in HDMI port does not work, no signal output Status in xorg package in Ubuntu: Won't Fix Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) No signal output while plug the cable into built-in hdmi port. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 6.2.0 20160914 (Ubuntu 6.2.0-3ubuntu15) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 21 14:37:35 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e5] Subsystem: Dell GM107GLM [Quadro M1000M] [1028:06e5] InstallationDate: Installed on 2016-09-19 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160918) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=a40a640b-1533-47a4-be70-98a11eb306bc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.10:bd06/30/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Sep 21 11:46:07 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625944/+subscriptions -- Mailing list: https://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 1829862] Re: [FFe] re-seeding demoted packages with python3 support
** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Changed in: duplicity (Ubuntu) Status: New => Fix Released ** Changed in: deja-dup (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1829862 Title: [FFe] re-seeding demoted packages with python3 support Status in deja-dup package in Ubuntu: In Progress Status in duplicity package in Ubuntu: Fix Released Status in mailman3 package in Ubuntu: Won't Fix Status in swift package in Ubuntu: Fix Released Bug description: As part of demotion of python2.7 to universe the following packages were demoted as colateral damange: * swift * mailman * duplicity This is an FFe requesting to allow re-seeding these packages back into main and/or onto desktop image, when python3 variants of them become available. Either prior to release, or as an SRU. Note that Openstack should have rc milestone available prior to release, with final just-in-time/shortly-after Eoan GA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1829862/+subscriptions -- Mailing list: https://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 1829862] Re: [FFe] re-seeding demoted packages with python3 support
mailman3 MIR got abandonned. ** Changed in: swift (Ubuntu) Status: New => Fix Released ** Changed in: mailman3 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1829862 Title: [FFe] re-seeding demoted packages with python3 support Status in deja-dup package in Ubuntu: In Progress Status in duplicity package in Ubuntu: Fix Released Status in mailman3 package in Ubuntu: Won't Fix Status in swift package in Ubuntu: Fix Released Bug description: As part of demotion of python2.7 to universe the following packages were demoted as colateral damange: * swift * mailman * duplicity This is an FFe requesting to allow re-seeding these packages back into main and/or onto desktop image, when python3 variants of them become available. Either prior to release, or as an SRU. Note that Openstack should have rc milestone available prior to release, with final just-in-time/shortly-after Eoan GA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1829862/+subscriptions -- Mailing list: https://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 1842890] Re: gnome-shell high cpu usage and unresponsiveness
Thanks, perfect! :) -- 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/1842890 Title: gnome-shell high cpu usage and unresponsiveness Status in gnome-shell package in Ubuntu: Incomplete Bug description: From time to time the shell becomes slow and poorly responsive, checking the CPU usage I discovered that in such moments it had high values, like 25-35%. In only one occasion it went up to 100% CPU and I was forced to reboot. I don't know if it matters, but I'm using an external screen connected to my laptop. Let me know if I can help better to debug the issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 11:35:03 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (213 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-21 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842890/+subscriptions -- Mailing list: https://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 1841382] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu8 --- accountsservice (0.6.55-0ubuntu8) eoan; urgency=medium * debian/rules: - Compile with -Dsystemd=true to fix libaccountsservice not working properly (LP: #1841382) -- Robert Ancell Fri, 06 Sep 2019 15:33:47 +1200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1841382 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() / g_hash_table_lookup() from accountsservice 0.6.55-0ubuntu5/6 Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/0075340d0f484f9b5d37821d3023970cc12d I do not know what triggered the crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 25 20:45:09 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-24 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 ?? () ?? () Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1841382/+subscriptions -- Mailing list: https://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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
** Changed in: mutter (Ubuntu Disco) Status: Confirmed => In Progress -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: In Progress Status in mutter source package in Eoan: Fix Released Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://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 1842662] Re: Gnome Dash (vanilla - no extensions) first icon always missing unless you open the dash soon after login
I ran it again and there are no errors - but nothing is showing up here? -- 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/1842662 Title: Gnome Dash (vanilla - no extensions) first icon always missing unless you open the dash soon after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using Vanilla Gnome session, with extensions turned off, the dash icons on the left of the screen do not display properly. The topmost icon is always missing (with the exception below) and replaced by a small empty square (which can still be clicked to open the application). This is very reproducible; I have the same issue on two separate machines, and the behaviour is identical * Opening the dash shortly after login prevents the problem from happening - all icons display correctly and remain correct for the duration of the session. * Waiting a while (e.g. one minute) after logging in before opening the dash will always result in the topmost icon being missing, and the only way to get it back is to restart the session. * It doesn't matter what application is placed in the topmost position on the dash - its icon will go missing. This doesn't seem to be related to extensions as I have extensions turned off in Tweaks, and both X11 and Wayland sessions have the same behavior. This is the same behavior as shown at this askubuntu link, and has been occurring ever since updating to 19.04: https://askubuntu.com/questions/1142990/first-most-application-icon- on-dash-hidden-until-gnome-shell- restarts?newreg=d0a226571a884b3fb3efed0639123106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842662/+subscriptions -- Mailing list: https://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 1843015] Re: [USB-Audio - Xonar SoundCard, playback] No sound at all
After some googling, this is already known bug in pulseaudio? -- 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/1843015 Title: [USB-Audio - Xonar SoundCard, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After some testing, aplay -D hw:2,2 samplename works but there seems to be no way to set that in gnome or for other applications? cat /proc/asound/devices 1:: sequencer 2: [ 2- 0]: digital audio playback 3: [ 2- 0]: digital audio capture 4: [ 2- 1]: digital audio playback 5: [ 2- 1]: digital audio capture 6: [ 2- 2]: digital audio playback 7: [ 2- 3]: digital audio playback 8: [ 2] : control 9: [ 0- 3]: digital audio playback 10: [ 0- 7]: digital audio playback 11: [ 0- 8]: digital audio playback 12: [ 0- 9]: digital audio playback 13: [ 0-10]: digital audio playback 14: [ 0-11]: digital audio playback 15: [ 0- 0]: hardware dependent 16: [ 0] : control 17: [ 1- 0]: digital audio playback 18: [ 1- 0]: digital audio capture 19: [ 1- 1]: digital audio playback 20: [ 1- 2]: digital audio capture 21: [ 1- 0]: hardware dependent 22: [ 1] : control 33:: timer Further, there is period of no sound at all from optical output when starting to play sample. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.2.11 x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 10:33:58 2019 InstallationDate: Installed on 2019-08-10 (26 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SoundCard failed Symptom_Card: Xonar SoundCard - Xonar SoundCard Symptom_Type: No sound at all Title: [USB-Audio - Xonar SoundCard, playback] No sound at all UpgradeStatus: Upgraded to disco on 2019-08-10 (26 days ago) dmi.bios.date: 07/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1843015/+subscriptions -- Mailing list: https://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 1798091] Re: thumbnailer cannot create tempfiles (with apparmor denials)
not fixed with ubuntu 19.04 pop os evince 3.32.0-1ubuntu0.1 ** Tags removed: cosmic ** Tags added: verification-failed-dingo ** Tags removed: verification-failed-dingo ** Tags added: verification-failed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1798091 Title: thumbnailer cannot create tempfiles (with apparmor denials) Status in evince package in Ubuntu: Fix Released Status in evince source package in Cosmic: Fix Released Status in evince source package in Disco: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Nautilus fails to generate previews for pdf files * Test case Download/copy a pdf, open the directory in nautilus, a preview image should be displayed * Regression potential Check that there are no other apparmor denials and the thumbnailer works - While trying to create thumbnails in a directory from within nautilus, I got: [781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince-thumbnailer" name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:59:00 2018 InstallationDate: Installed on 2014-06-19 (1580 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions -- Mailing list: https://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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-vaapi-driver (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libva (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in Libva: Fix Released Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in intel-vaapi-driver source package in Bionic: Confirmed Status in libva source package in Bionic: Confirmed Status in mesa source package in Bionic: Invalid Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1813131/+subscriptions -- Mailing list: https://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 1843015] Re: [USB-Audio - Xonar SoundCard, playback] No sound at all
So, in short, even though Gnome panel allows setting the device, it does not allow handling correct /output/ when there are multiple choices? E.g. only optical connected to receiver instead of analog. -- 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/1843015 Title: [USB-Audio - Xonar SoundCard, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After some testing, aplay -D hw:2,2 samplename works but there seems to be no way to set that in gnome or for other applications? cat /proc/asound/devices 1:: sequencer 2: [ 2- 0]: digital audio playback 3: [ 2- 0]: digital audio capture 4: [ 2- 1]: digital audio playback 5: [ 2- 1]: digital audio capture 6: [ 2- 2]: digital audio playback 7: [ 2- 3]: digital audio playback 8: [ 2] : control 9: [ 0- 3]: digital audio playback 10: [ 0- 7]: digital audio playback 11: [ 0- 8]: digital audio playback 12: [ 0- 9]: digital audio playback 13: [ 0-10]: digital audio playback 14: [ 0-11]: digital audio playback 15: [ 0- 0]: hardware dependent 16: [ 0] : control 17: [ 1- 0]: digital audio playback 18: [ 1- 0]: digital audio capture 19: [ 1- 1]: digital audio playback 20: [ 1- 2]: digital audio capture 21: [ 1- 0]: hardware dependent 22: [ 1] : control 33:: timer Further, there is period of no sound at all from optical output when starting to play sample. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.2.11 x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 10:33:58 2019 InstallationDate: Installed on 2019-08-10 (26 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SoundCard failed Symptom_Card: Xonar SoundCard - Xonar SoundCard Symptom_Type: No sound at all Title: [USB-Audio - Xonar SoundCard, playback] No sound at all UpgradeStatus: Upgraded to disco on 2019-08-10 (26 days ago) dmi.bios.date: 07/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1843015/+subscriptions -- Mailing list: https://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 1843015] [NEW] [USB-Audio - Xonar SoundCard, playback] No sound at all
Public bug reported: After some testing, aplay -D hw:2,2 samplename works but there seems to be no way to set that in gnome or for other applications? cat /proc/asound/devices 1:: sequencer 2: [ 2- 0]: digital audio playback 3: [ 2- 0]: digital audio capture 4: [ 2- 1]: digital audio playback 5: [ 2- 1]: digital audio capture 6: [ 2- 2]: digital audio playback 7: [ 2- 3]: digital audio playback 8: [ 2] : control 9: [ 0- 3]: digital audio playback 10: [ 0- 7]: digital audio playback 11: [ 0- 8]: digital audio playback 12: [ 0- 9]: digital audio playback 13: [ 0-10]: digital audio playback 14: [ 0-11]: digital audio playback 15: [ 0- 0]: hardware dependent 16: [ 0] : control 17: [ 1- 0]: digital audio playback 18: [ 1- 0]: digital audio capture 19: [ 1- 1]: digital audio playback 20: [ 1- 2]: digital audio capture 21: [ 1- 0]: hardware dependent 22: [ 1] : control 33:: timer Further, there is period of no sound at all from optical output when starting to play sample. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.2.11 x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 10:33:58 2019 InstallationDate: Installed on 2019-08-10 (26 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SoundCard failed Symptom_Card: Xonar SoundCard - Xonar SoundCard Symptom_Type: No sound at all Title: [USB-Audio - Xonar SoundCard, playback] No sound at all UpgradeStatus: Upgraded to disco on 2019-08-10 (26 days ago) dmi.bios.date: 07/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1804:bd07/29/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1843015 Title: [USB-Audio - Xonar SoundCard, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: After some testing, aplay -D hw:2,2 samplename works but there seems to be no way to set that in gnome or for other applications? cat /proc/asound/devices 1:: sequencer 2: [ 2- 0]: digital audio playback 3: [ 2- 0]: digital audio capture 4: [ 2- 1]: digital audio playback 5: [ 2- 1]: digital audio capture 6: [ 2- 2]: digital audio playback 7: [ 2- 3]: digital audio playback 8: [ 2] : control 9: [ 0- 3]: digital audio playback 10: [ 0- 7]: digital audio playback 11: [ 0- 8]: digital audio playback 12: [ 0- 9]: digital audio playback 13: [ 0-10]: digital audio playback 14: [ 0-11]: digital audio playback 15: [ 0- 0]: hardware dependent 16: [ 0] : control 17: [ 1- 0]: digital audio playback 18: [ 1- 0]: digital audio capture 19: [ 1- 1]: digital audio playback 20: [ 1- 2]: digital audio capture 21: [ 1- 0]: hardware dependent 22: [ 1] : control 33:: timer Further, there is period of no sound at all from optical output when starting to play sample. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.2.11 x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 6 10:33:58 2019 InstallationDate: Installed on 2019-08-10 (26 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SoundCard failed Symptom_Card: Xonar SoundCard - Xonar SoundCard Symptom_Type: No sound at all Title: [USB-Audio - Xonar SoundCard, playback] No sound at all UpgradeStatus: Upgraded to disco on 2019-08-10 (26 days ago) dmi.bios.date: 07/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version:
