[Desktop-packages] [Bug 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome
The issue seem to appear when multiple fonts can provide the emojis. What seems to me is that the noto-color-emojis are not necessarily the first in the list. I had for exaple other font-noto packages and they were hiding the color emojis. I removed all the others and now I can see the color ones again. The fact that user fonts have priority over system fonts is the reason for why the previous workaround works. However, in order to fix this bug, we need to think first, what should be fixed? Option 1: the issue is just that the user is unaware -> keep the current behaviour and eventually find a way to inform the user of what font has the highest priority to provide emojis, possibly at install time. (This should be possible, given that Chrome does this) Option 2: the issue is the mechanism -> we could have some configuration for a default emoji-provider, and have it handled with update- alternatives, the same way one can set the vanilla or ubuntu or pop gdm theme. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1859926 Title: fonts-noto-color-emoji not making pretty emojis in google chrome Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Bug description: Google-Chrome and emoji's is being a weird headache. Something's causing it not to find the right font to make emoji's: "[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+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 1872028] [NEW] [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker
Public bug reported: [Reproduce steps] 1. Install 20.04 daily build on 4/9. 2. Do dist-upgrade after installation. 3. Go to System Setting->Sound->Output, press the test button. 4. There is no sound output while press the Front right and Front left button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 04:11:26 2020 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.03.01 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.93.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One dmi.product.sku: 6AE44AV dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1872028 Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker Status in alsa-driver package in Ubuntu: New Bug description: [Reproduce steps] 1. Install 20.04 daily build on 4/9. 2. Do dist-upgrade after installation. 3. Go to System Setting->Sound->Output, press the test button. 4. There is no sound output while press the Front right and Front left button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 04:11:26 2020 InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1358 F pulseaudio /dev/snd/pcmC0D0c: u 1358 F...m pulseaudio /dev/snd/pcmC0D0p: u 1358 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2019 dmi.bios.vendor: HP dmi.bios.version: R12 Ver. 02.03.01 dmi.board.name: 85A2 dmi.board.vendor: HP dmi.board.version: KBC Version 08.93.00 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One dmi.product.sku: 6AE44AV dmi.sys.vendor: HP To manage notifications about this bug go to:
[Desktop-packages] [Bug 1872016] [NEW] package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872016/+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 1872016] Re: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872016 Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in ibus package in Ubuntu: New Bug description: Following an upgrade from 16.4 to 18.4 this error occured I can also not see any desktop ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Apr 10 15:37:48 2020 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-12 (1093 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.6.12 SourcePackage: ibus Title: package gir1.2-ibus-1.0 1.5.17-3ubuntu5.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872016/+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 1872011] Re: Google chrome sometimes stops displaying color emojis
*** This bug is a duplicate of bug 1859926 *** https://bugs.launchpad.net/bugs/1859926 ** Description changed: - I recently noticed that after reboots or possibly after Google Chrome - get updated, I cannot anymore see color emojis (I can only see the old - black and white ones instead). Reinstalling the package seem to solve - the issue temporarily but after the a reboot or Chrome update the issue - arises again. - - A discussion on what appears to be the same issue: - https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- - up-at-all-in-chrome-only-partially-in-firefox + I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. + Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 + Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox + Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** This bug has been marked a duplicate of bug 1859926 fonts-noto-color-emoji not making pretty emojis in google chrome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1872011 Title: Google chrome sometimes stops displaying color emojis Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji
[Desktop-packages] [Bug 1872011] [NEW] Google chrome sometimes stops displaying color emojis
*** This bug is a duplicate of bug 1859926 *** https://bugs.launchpad.net/bugs/1859926 Public bug reported: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. + + A discussion on what appear to be the same issue: + https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- + up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: - + InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. - A discussion on what appear to be the same issue: + A discussion on what appears to be the same issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing- up-at-all-in-chrome-only-partially-in-firefox ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fonts-noto-color-emoji 0~20191119-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 10 09:51:14 2020 Dependencies: InstallationDate: Installed on 2020-04-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1872011 Title: Google chrome sometimes stops displaying color emojis Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: I recently noticed that after reboots or possibly after Google Chrome get updated, I cannot anymore see color emojis (I can only see the old black and white ones instead). Reinstalling the package seem to solve the issue temporarily but after the a reboot or Chrome update the issue arises again. Similar issue on Brave (Chrome-based) browser: https://community.brave.com/t/emoji-are-monochrome-line-art-or-blank-boxes-brave-1-1-23/100111/7 Discussion on AskUbuntu on similar issue: https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox Possibly a duplicate of: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926?comments=all ProblemType: Bug
[Desktop-packages] [Bug 1650683] Re: tracker runs despite search being set to off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- 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/1650683 Title: tracker runs despite search being set to off Status in tracker package in Ubuntu: Confirmed Bug description: The master switch in the Search control panel is set to OFF (see attached screenshot). Yet the tracker daemon runs (poorly, cf. bug #1650681). This could under some circumstances lead to privacy violations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1650683/+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 1872006] Re: evince crashed with SIGABRT in g_assertion_message.cold()
Thank you for your bug report. Were you applying updates at the same time? If so that's a known GTK issue ** Changed in: evince (Ubuntu) Status: New => Incomplete ** Information type changed from Private to Public -- 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/1872006 Title: evince crashed with SIGABRT in g_assertion_message.cold() Status in evince package in Ubuntu: Incomplete Bug description: I tried to open a downloaded pdf file in skype and the application crash report popped up. Opening the file in folder by double clicking on it opens the pdf file in Document Viewer without any errors. I'm using latest beta Ubuntu 20.04 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Apr 10 07:51:17 2020 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2019-07-21 (263 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=17370850-6108-41f9-9fa4-5c6273ce0acb ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: evince crashed with SIGABRT in g_assertion_message_error() UpgradeStatus: Upgraded to focal on 2020-04-03 (6 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1872006/+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 1871997] Re: The primary display will cause black screen when external 4K monitor is configured to flipped
Thank you for your bug report. Could you add your 'journalctl -b 0' log to the bug after getting the issue? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1871997 Title: The primary display will cause black screen when external 4K monitor is configured to flipped Status in xorg package in Ubuntu: Incomplete Bug description: The primary (built-in) display will cause black screen when external 4K monitor is configured to flipped Steps to reproduce: 1. plug 4K monitor via HDMI 2. open gnome-control-center 3. select Displays -> Orientation -> Landscape (flipped) 4. apply 5. black screen on built-in displays The primary display can be recovered if HDMI cable is re-plugged again. Machine: Dell XPS 13 9380 (Intel Coffee Lake) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:24:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-07 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=60712c21-4620-4018-821e-afb9a77f9ec8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.10.2 dmi.board.name: 0SSY11 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.10.2:bd01/15/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+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
