[Desktop-packages] [Bug 1836691] Re: Update to 1.49
** Branch linked: lp:~ubuntu-desktop/snapd-glib/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1836691 Title: Update to 1.49 Status in snapd-glib package in Ubuntu: Triaged Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Disco: Triaged Status in snapd-glib source package in Eoan: Triaged Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1836691/+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 1836691] Re: Update to 1.49
** Changed in: snapd-glib (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: snapd-glib (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: snapd-glib (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: snapd-glib (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: snapd-glib (Ubuntu Eoan) Status: New => Triaged ** Changed in: snapd-glib (Ubuntu Disco) Status: New => Triaged ** Changed in: snapd-glib (Ubuntu Bionic) Status: New => Triaged ** Changed in: snapd-glib (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1836691 Title: Update to 1.49 Status in snapd-glib package in Ubuntu: Triaged Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Disco: Triaged Status in snapd-glib source package in Eoan: Triaged Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1836691/+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 1836691] Re: Update to 1.49
** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1836691 Title: Update to 1.49 Status in snapd-glib package in Ubuntu: Triaged Status in snapd-glib source package in Xenial: Triaged Status in snapd-glib source package in Bionic: Triaged Status in snapd-glib source package in Disco: Triaged Status in snapd-glib source package in Eoan: Triaged Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1836691/+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 1836691] [NEW] Update to 1.49
Public bug reported: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1836691 Title: Update to 1.49 Status in snapd-glib package in Ubuntu: New Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1836691/+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 1829160] Re: Xorg and wayland crash
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1829160 Title: Xorg and wayland crash Status in xorg-server package in Ubuntu: Expired Bug description: On Ubuntu 19.10, on either Gnome or Ubuntu desktops whether you use wayland or xorg upon hitting the super key or by pointing the mouse on the upper left corner xorg / wayland crashes or gets stuck. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.1.2-050102-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 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: KDE Date: Wed May 15 10:29:59 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.6, 5.0.0-14-generic, x86_64: installed virtualbox, 6.0.6, 5.1.1-050101-generic, x86_64: installed virtualbox, 6.0.6, 5.1.2-050102-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1134] InstallationDate: Installed on 2019-05-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190508) Lsusb: Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer TravelMate P259-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.1.2-050102-generic root=UUID=c0ff169b-318d-4b2c-8938-1e09f710166e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Lyra_SK dmi.board.vendor: Acer dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd06/27/2017:svnAcer:pnTravelMateP259-M:pvrV1.28:rvnAcer:rnLyra_SK:rvrV1.28:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: TravelMate P259-M dmi.product.sku: TravelMate P259-M_1134_1.28 dmi.product.version: V1.28 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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-server/+bug/1829160/+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 1822360] Re: Scan does not work with Lexmark OfficeEdge Pro 5500
*** This bug is a duplicate of bug 1728012 *** https://bugs.launchpad.net/bugs/1728012 @Phil: It's still in bionic-proposed, but will be moved to bionic- updates any day now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1822360 Title: Scan does not work with Lexmark OfficeEdge Pro 5500 Status in sane-backends package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1822360/+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 1822360] Re: Scan does not work with Lexmark OfficeEdge Pro 5500
*** This bug is a duplicate of bug 1728012 *** https://bugs.launchpad.net/bugs/1728012 Updated software - scanner still does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1822360 Title: Scan does not work with Lexmark OfficeEdge Pro 5500 Status in sane-backends package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1822360/+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 1836661] [NEW] /usr/lib/policykit-1/polkitd:11:polkit_backend_config_source_ensure:polkit_backend_config_source_get_string_list:polkit_backend_local_authority_get_admin_auth_id
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding policykit-1. This problem was most recently seen with package version 0.105-25, the problem page at https://errors.ubuntu.com/problem/d338a615dec289620a3349c6e2f857ee18580d68 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco precise trusty utopic xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1836661 Title: /usr/lib/policykit-1/polkitd:11:polkit_backend_config_source_ensure:polkit_backend_config_source_get_string_list:polkit_backend_local_authority_get_admin_auth_identities:authentication_agent_initiate_challenge:polkit_backend_interactive_authority_check_authorization Status in policykit-1 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding policykit-1. This problem was most recently seen with package version 0.105-25, the problem page at https://errors.ubuntu.com/problem/d338a615dec289620a3349c6e2f857ee18580d68 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1836661/+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 1836659] [NEW] Ubuntu 18.04's ibus package breaks password fields in Firefox again
Public bug reported: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 ** 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/1836659 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox again Status in firefox package in Ubuntu: New Bug description: On an uptodate Ubuntu 18.04.2 LTS system I am observing the same symptoms as in bug https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 When I focus a password field in Firefox, it starts focusing and unfocusing rapidly, making it difficult to type passwords. Also, CPU usage goes up with the 4 processes eating most: %Cpu(s): 25,3 us, 11,0 sy, 0,0 ni, 63,5 id Xorg 60% gnome-flashback 21% firefox 20% ibus-daemon 4% Launching Firefox with GTK_IM_MODULE=xim firefox makes it go away. This started several (~7) days ago. $ apt list gnome-shell ibus firefox Listing... Done firefox/bionic-updates,bionic-security,now 68.0+build3-0ubuntu0.18.04.1 amd64 [installed] gnome-shell/bionic-updates,now 3.28.4-0ubuntu18.04.1 amd64 [installed] ibus/bionic,now 1.5.17-3ubuntu4 amd64 [installed] $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836659/+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 1836651] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1836651 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: error during update ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 15 14:25:23 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-12-26 (201 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1836651/+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 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
Seems to possibly be something going slightly slower with this kernel. With 5.2 a fw IPv6 address assignment tests (DHCP and RA) fail sometimes and pass other times, and usually at least one of them fails. The same failures would happen in the past, but less frequency. I suspect that something is taking slightly longer with 5.2 such that the tests frequently time out before the interface becomes activated. Since the tests do pass I'm setting this to low and not blocking kernel promotion on it. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+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 1836651] [NEW] package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: error during update ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 15 14:25:23 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-12-26 (201 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1836651 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: error during update ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 15 14:25:23 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-12-26 (201 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1836651/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
I suppose many Linux users probably use Firefox as a browser. And I can use the newest version of Firefox to play videos without any trouble. But with chrome and chromium 75: Even after deleting all files and programs related to these browsers and starting totally fresh, video will not play and freeze the browsers. Could it be my nvidia drivers? But even audio play freezes. So it appears that all active media is affected on versions 75 and up, including beta and unstable versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: New Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: DistroRelease: Ubuntu 18.04 Env: 'None' 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 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.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
What changed about video and audio playback on version 75 of chrome and chromium? As I said before any earlier version worked just fine. In chrome or chromium 75 when I click on any video to play, the moving circle appears and then freezes instantly, as if it is stopped on purpose. It may have to do with the process that stops videos from automatically starting until one clicks on the play arrow. Except in this case clicking on a video is treated as if it were a automatic video start? I still cannot believe that no one else has reported this issue. my askubuntu question: https://askubuntu.com/questions/1152145/how-to-repair-chrome-75-video-playback-with-freezes-and-crashes has had 103 views, which leads me to believe that at least over 100 users are affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: New Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: DistroRelease: Ubuntu 18.04 Env: 'None' 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 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.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
chrome://media-internals/
Recent Player
none
Audio
{
"AudioServiceAudioStreams": "Disabled",
"AudioServiceLaunchOnStartup": "Disabled",
"AudioServiceOutOfProcess": "Disabled",
"AudioServiceOutOfProcessKillAtHang": "Disabled",
"AudioServiceSandbox": "Disabled",
"WebRtcApmInAudioService": "Disabled"
}
[]
Input Controller
none
Output Controllers
none
Output Streams
none
Video Capture Device Capabilities
none
Audio Focus
Active Sessions
none
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1835623
Title:
Google Chrome Linux version 75 freezes and then crashes when trying to
play any video
Status in chromium-browser package in Ubuntu:
New
Bug description:
(upstream bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=983203)
Ubuntu 18.04
I expect Chrome to play videos.
When I try to play any video on Google Chrome for Linux, any version of 75 or
higher, Google Chrome freezes.
Chrome 75 will allow sound but no video.
All mouse clicks become unresponsive.
Attempting to close Chrome after many mouse clicks causes Chrome to crash.
Even worse it often also crashes Ubuntu 18.04.
Google Chrome 74 or lower work without any problems playing videos.
It is a Google Chrome Linux version 75 or higher problem.
I cannot believe that neither Google or Ubuntu or any other Linux OS seem to
completely ignore this extremely serious problem.
I am forced to install Google Chrome 71 to fix video playback problem.
I posted on Ubuntu ask, and show over 90 views but no comments.
One answer confirms that he has the exact same problem.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Desktop-Session:
'ubuntu'
'/etc/xdg/xdg-ubuntu:/etc/xdg'
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:
DistroRelease: Ubuntu 18.04
Env:
'None'
'None'
InstallationDate: Installed on 2019-05-02 (66 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20181019)
Load-Avg-1min: 1.47
Load-Processes-Running-Percent: 0.1%
MachineType: MSI MS-7641
NonfreeKernelModules: nvidia_modeset nvidia
Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1
PackageArchitecture: amd64
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.15.0-55-generic
root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Tags: bionic
Uname: Linux 4.15.0-55-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev
sambashare sambashare sudo sudo
_MarkForUpload: True
dmi.bios.date: 04/20/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.1
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 760GMA-P34(FX) (MS-7641)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: MS-7641
dmi.product.version: 5.0
dmi.sys.vendor: MSI
etcconfigcpepperflashpluginnonfree:
flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 |
sed -e "s/,/./g"`
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso
--ppapi-flash-version=$flashversion"
modified.conffile..etc.default.chromium-browser: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
chrome://media-internals/
Recent Player
none
Audio
{
"AudioServiceAudioStreams": "Disabled",
"AudioServiceLaunchOnStartup": "Disabled",
"AudioServiceOutOfProcess": "Disabled",
"AudioServiceOutOfProcessKillAtHang": "Disabled",
"AudioServiceSandbox": "Disabled",
"WebRtcApmInAudioService": "Disabled"
}
[]
Input Controller
none
Output Controllers
none
Output Streams
none
Video Capture Device Capabilities
none
Audio Focus
Active Sessionsnone
On Mon, Jul 15, 2019 at 4:50 AM Olivier Tilloy
wrote:
> Thank you for filing an upstream bug.
>
> Your issue is being treated as seriously as other incoming bugs. The
> problem right now is that triagers haven't observed or managed to
> reproduce the problem, which makes it difficult to know where to start.
> No one else has reported similar issues on Launchpad either, so the bug
> you're experiencing doesn't seem to be affecting many people
> (fortunately).
>
> Can you browse to chrome://media-internals/, click the button to save
> the logs, and attach the log file here? Thanks!
>
> ** Changed in: chromium-browser (Ubuntu)
>Status: Incomplete => New
>
> ** Description changed:
>
> + (upstream bug report:
> + https://bugs.chromium.org/p/chromium/issues/detail?id=983203)
> +
> Ubuntu 18.04
> I expect Chrome to play videos.
> When I try to play any video on Google Chrome for Linux, any version of
> 75 or higher, Google Chrome freezes.
> Chrome 75 will allow sound but no video.
> All mouse clicks become unresponsive.
> Attempting to close Chrome after many mouse clicks causes Chrome to
> crash.
> Even worse it often also crashes Ubuntu 18.04.
> Google Chrome 74 or lower work without any problems playing videos.
> It is a Google Chrome Linux version 75 or higher problem.
> I cannot believe that neither Google or Ubuntu or any other Linux OS
> seem to completely ignore this extremely serious problem.
> I am forced to install Google Chrome 71 to fix video playback problem.
> I posted on Ubuntu ask, and show over 90 views but no comments.
> One answer confirms that he has the exact same problem.
> - ---
> + ---
> ProblemType: Bug
> ApportVersion: 2.20.9-0ubuntu7.6
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Desktop-Session:
> - 'ubuntu'
> - '/etc/xdg/xdg-ubuntu:/etc/xdg'
> - '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
> + 'ubuntu'
> + '/etc/xdg/xdg-ubuntu:/etc/xdg'
> + '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
> DetectedPlugins:
> -
> +
> DistroRelease: Ubuntu 18.04
> Env:
> - 'None'
> - 'None'
> + 'None'
> + 'None'
> InstallationDate: Installed on 2019-05-02 (66 days ago)
> InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20181019)
> Load-Avg-1min: 1.47
> Load-Processes-Running-Percent: 0.1%
> MachineType: MSI MS-7641
> NonfreeKernelModules: nvidia_modeset nvidia
> Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1
> PackageArchitecture: amd64
> ProcEnviron:
> - TERM=xterm-256color
> - PATH=(custom, no user)
> - XDG_RUNTIME_DIR=
> - LANG=en_US.UTF-8
> - SHELL=/bin/bash
> + TERM=xterm-256color
> + PATH=(custom, no user)
> + XDG_RUNTIME_DIR=
> + LANG=en_US.UTF-8
> + SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1
> ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
> Tags: bionic
> Uname: Linux 4.15.0-55-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev
> sambashare sambashare sudo sudo
> _MarkForUpload: True
> dmi.bios.date: 04/20/2015
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: V25.1
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: 760GMA-P34(FX) (MS-7641)
> dmi.board.vendor: MSI
> dmi.board.version: 5.0
> dmi.chassis.asset.tag: To Be Filled By O.E.M.
> dmi.chassis.type: 3
> dmi.chassis.vendor: MSI
> dmi.chassis.version: 5.0
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0:
> dmi.product.family: To Be Filled By O.E.M.
> dmi.product.name: MS-7641
> dmi.product.version: 5.0
> dmi.sys.vendor: MSI
> etcconfigcpepperflashpluginnonfree:
> - flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
> - flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f
> 2 | sed -e "s/,/./g"`
> - CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso
> --ppapi-flash-version=$flashversion"
> + flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
> + flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f
> 2 | sed -e "s/,/./g"`
> + CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso
> --ppapi-flash-version=$flashversion"
>
[Desktop-packages] [Bug 1801427] Re: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README'
a dpkg --force-overwrite -i /var/cache/apt/archives/texlive-latex-recommended-doc_2017.20180305-1_all.deb got me a little further. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1801427 Title: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive- doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 Status in texlive-base package in Ubuntu: Confirmed Bug description: updates or upgrades crash due to tex-live base ubuntu 16.04 I hope this is enough information ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-latex-recommended-doc 2017.20180305-1 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Nov 2 23:57:48 2018 DuplicateSignature: package:texlive-latex-recommended-doc:2015.20160320-1ubuntu0.1 Replacing files in old package texlive-latex-extra-doc (2015.20160320-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-latex-recommended-doc_2017.20180305-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 InstallationDate: Installed on 2017-01-05 (666 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: texlive-base Title: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 UpgradeStatus: Upgraded to xenial on 2018-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1801427/+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 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). - This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6, and TTY7 gives the X session. + This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker 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 nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+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 1817537] Re: libsoup should support ntlmv2
The changes fix some cases but seems like some servers require an extra change https://gitlab.gnome.org/GNOME/libsoup/commit/c51f9f63 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1811402] Re: Can not switch to virtual console (TTY)
** Description changed: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). - This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. + This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker 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 nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. With nouveau driver I can switch to TTY2, TTY3 and TTY6 for text console, and TTY7 gives the X session. This bug also breaks light-locker, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1811402/+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 1836641] [NEW] 18.04 firefox - broken for xml display
Public bug reported: I have some files on my system that I browse with firefox. file:///some/folder/data.xml And data.xml is formatted using an xsl stylesheet. This worked fine until this weekend. Now, I just see a big blob of unformatted text when I visit data.xml. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 68.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BuildID: 20190706110151 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Jul 15 15:44:31 2019 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.50.1 dev eth2 proto dhcp metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.50.0/24 dev eth2 proto kernel scope link src 192.168.50.100 metric 100 Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=68.0/20190706110151 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190709.1-0ubuntu0.18.04.1 RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-hook-error 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/1836641 Title: 18.04 firefox - broken for xml display Status in firefox package in Ubuntu: New Bug description: I have some files on my system that I browse with firefox. file:///some/folder/data.xml And data.xml is formatted using an xsl stylesheet. This worked fine until this weekend. Now, I just see a big blob of unformatted text when I visit data.xml. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 68.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BuildID: 20190706110151 Channel: Unavailable CurrentDesktop: GNOME Date: Mon Jul 15 15:44:31 2019 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.50.1 dev eth2 proto dhcp metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.50.0/24 dev eth2 proto kernel scope link src 192.168.50.100 metric 100 Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=68.0/20190706110151 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190709.1-0ubuntu0.18.04.1 RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1836641/+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 1801427] Re: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texlive-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1801427 Title: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive- doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 Status in texlive-base package in Ubuntu: Confirmed Bug description: updates or upgrades crash due to tex-live base ubuntu 16.04 I hope this is enough information ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-latex-recommended-doc 2017.20180305-1 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Nov 2 23:57:48 2018 DuplicateSignature: package:texlive-latex-recommended-doc:2015.20160320-1ubuntu0.1 Replacing files in old package texlive-latex-extra-doc (2015.20160320-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-latex-recommended-doc_2017.20180305-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 InstallationDate: Installed on 2017-01-05 (666 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: texlive-base Title: package texlive-latex-recommended-doc 2015.20160320-1ubuntu0.1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/polyglossia/README', which is also in package texlive-xetex 2015.20160320-1ubuntu0.1 UpgradeStatus: Upgraded to xenial on 2018-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1801427/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
fonts-noto-cjk fixed in disco and bionic via bug #1834406. ** Changed in: fonts-noto-cjk (Ubuntu Bionic) Status: New => Fix Released ** Changed in: fonts-noto-cjk (Ubuntu Disco) Status: New => Fix Released ** No longer affects: fonts-noto-cjk (Ubuntu Cosmic) ** No longer affects: gnome-characters (Ubuntu Cosmic) ** No longer affects: gucharmap (Ubuntu Cosmic) ** No longer affects: icu (Ubuntu Cosmic) ** No longer affects: openjdk-8 (Ubuntu Cosmic) ** No longer affects: poppler-data (Ubuntu Cosmic) ** No longer affects: unicode-data (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: Fix Released Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: Fix Released Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in fonts-noto-cjk source package in Disco: Fix Released Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but
[Desktop-packages] [Bug 1836616] [NEW] [snap] Upgrade from deb to snap forgets saved passwords
Public bug reported: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin/chromium- browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 ** Affects: chromium-browser (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Triaged ** Tags: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Triaged Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+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 1835794] Re: Bookmarks unusable because clicks drag them
** Changed in: nautilus (Ubuntu) Status: Triaged => Invalid -- 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/1835794 Title: Bookmarks unusable because clicks drag them Status in Nautilus: New Status in nautilus package in Ubuntu: Invalid Bug description: Clicking on a bookmark starts a drag operation that you have to cancel pressing Escape. This happens both in nautilus and in the standard file dialog. It happens also when using the touchpad. Since bookmarks are an important and standard feature, having them crippled to the point of barely usable seems to me like a not-so-minor issue. Upstream report: https://gitlab.gnome.org/GNOME/nautilus/issues/963 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1835794/+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 1835794] Re: Bookmarks unusable because clicks drag them
As I commented upstream (https://gitlab.gnome.org/GNOME/nautilus/issues/963#note_555977) this is probably a bug in general touchpad support because is affecting other apps and components in similar ways. I would close this or move it to some other project (maybe libinput?). -- 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/1835794 Title: Bookmarks unusable because clicks drag them Status in Nautilus: New Status in nautilus package in Ubuntu: Invalid Bug description: Clicking on a bookmark starts a drag operation that you have to cancel pressing Escape. This happens both in nautilus and in the standard file dialog. It happens also when using the touchpad. Since bookmarks are an important and standard feature, having them crippled to the point of barely usable seems to me like a not-so-minor issue. Upstream report: https://gitlab.gnome.org/GNOME/nautilus/issues/963 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1835794/+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 1836576] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()
*** This bug is a duplicate of bug 1697234 *** https://bugs.launchpad.net/bugs/1697234 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1697234, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1836576/+attachment/5277136/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277138/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277144/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277145/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277146/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277147/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1836576/+attachment/5277148/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1697234 totem-video-thumbnailer crashed with SIGTRAP in g_malloc() from g_slice_alloc() from _sysmem_new_block() from gst_buffer_new_allocate() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1836576 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() Status in totem package in Ubuntu: New Bug description: No idea. I didn't even call it myself. ``` $ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 $ apt-cache policy totem totem: Installed: 3.18.1-1ubuntu4 Candidate: 3.18.1-1ubuntu4 Version table: *** 3.18.1-1ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ``` ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: totem 3.18.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 15 15:39:11 2019 EcryptfsInUse: Yes ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2017-09-19 (664 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: /usr/bin/totem-video-thumbnailer /home/username/Documents/Forcepoint/Archives/no-backup-area/New\ Product\ 6.4/UX\ and\ Branding\ -\ Policy\ uploads\ in\ a\ single\ tab.mp4 /home/username/.cache/unity-lens-video/_home_sntentos_Documents_Forcepoint_Archives_no-backup-area_New\ Product\ 6.4_UX\ and\ Branding\ -\ Policy\ uploads\ in\ a\ single\ tab.mp4 Signal: 5 SourcePackage: totem StacktraceTop: g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo wireshark xpra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1836576/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released -- 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/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in
[Desktop-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
For me, after suspend/resume the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. None of the workarounds work here. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu -- 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/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1832786] Re: [snap] chromium-browser ignores system password store
So the interface is connected indeed. What makes you say that the new snap release passes the --password- store=basic command line argument? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1832786 Title: [snap] chromium-browser ignores system password store Status in chromium-browser package in Ubuntu: Incomplete Bug description: The new chromium 75 snap package intentionally ignores the system password store: https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux_password_storage.md Normally, chromium auto-detects what type of password store to use, previously this has resulted in chromium connecting to the gnome password store. The new snap release passes the command line argument: '--password-store=basic' Which bypasses the gnome password storage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832786/+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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
Thank you for filing an upstream bug. Your issue is being treated as seriously as other incoming bugs. The problem right now is that triagers haven't observed or managed to reproduce the problem, which makes it difficult to know where to start. No one else has reported similar issues on Launchpad either, so the bug you're experiencing doesn't seem to be affecting many people (fortunately). Can you browse to chrome://media-internals/, click the button to save the logs, and attach the log file here? Thanks! ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Description changed: + (upstream bug report: + https://bugs.chromium.org/p/chromium/issues/detail?id=983203) + Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: - 'ubuntu' - '/etc/xdg/xdg-ubuntu:/etc/xdg' - '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' + 'ubuntu' + '/etc/xdg/xdg-ubuntu:/etc/xdg' + '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: - + DistroRelease: Ubuntu 18.04 Env: - 'None' - 'None' + 'None' + 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: - flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" - flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` - CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" + flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" + flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` + CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: New Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become
[Desktop-packages] [Bug 1835467] Re: Repeatingly looking for the next occurrence of a word search in a webpage misses one occurrence.
This remains very puzzling!
Could you, by any chance, try an upstream build of firefox (download from
https://www.mozilla.org/firefox/download/thanks/, unpack and run), and share
here whether it's also affected? If so, would you mind filing a bug report at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing the
link to it here?
Thanks!
--
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/1835467
Title:
Repeatingly looking for the next occurrence of a word search in a
webpage misses one occurrence.
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Hi,
This is probably the most unexpected bug that I have ever seen. Fortunately,
it is benign.
How to reproduce:
- Go to the webpage https://www.w3schools.com/howto/howto_js_autocomplete.asp
- Type Ctrl+f to look for a word through the webpage.
- Search for addEventListener. Firefox successfully found 4 occurrences on
the webpage.
- Using the arrows next to the search box, loop through all occurrences.
Firefox then jumps to the following occurrences, in order:
1. inp.addEventListener("input", function(e) {
2. b.addEventListener("click", function(e) {
3. inp.addEventListener("keydown", function(e) { (In my screen is, it was
hidden by the message about cookies: scrolling down by 1cm makes it appear.)
4. document.addEventListener("click", function (e) {
5. First occurrence again: inp.addEventListener("input", function(e) {
6. Second occurrence again: b.addEventListener("click", function(e) {
7. Firefox then directly jumps to the fourth occurrence, missing the third
one: document.addEventListener("click", function (e) {
8. (goes back to 5).
In other words, although the first cycle through all occurrences was
correct, the following cycles completely miss the third occurrence! I
have restarted Firefox and still get this behaviour.
If instead of clicking on the “down” arrow to look for the second
occurrence one looks backwards with the “up” arrow, then it is
“b.addEventListener("click", function(e) {” instead of
“inp.addEventListener("keydown", function(e) {” which is missing from
the loop: it seems that whenever cycling through all occurrences of a
search in a webpage, if there are only four occurrences, then the
third one is never reached except in the first cycle.
I am sending a screenshot of the situation.
This is a very unexpected behaviour, but of very minor consequence:
there is no need to place a high level of importance for this bug, I
guess.
Regards,
Martin.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0.4+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-54-generic.
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin 1585 F pulseaudio
BuildID: 20190620092152
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9091 irq 95'
Mixer name : 'Realtek ALC233'
Components : 'HDA:10ec0235,17aa3825,0012
HDA:80862882,80860101,0010'
Controls : 33
Simple ctrls : 14
Channel: Unavailable
CurrentDesktop: LXDE
Date: Thu Jul 4 23:24:35 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2016-12-05 (941 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IpRoute:
default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600
192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.3 metric 600
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-7e1f310f-034d-4a7b-b742-54df41180319
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0.4/20190620092152 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
bp-7e1f310f-034d-4a7b-b742-54df41180319
bp-daebd85b-34c2-4ab9-88ea-1fc091180208
bp-dd2282e2-f0cb-47f7-a13a-a16c20180102
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to bionic on 2018-08-29 (309 days ago)
[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
I added a systemd unit to stop autofs before going into suspend and start autofs again after resume. I haven't had any freezes with gdm3 anymore. But there is still a difference between Ethernet and Wifi. When connected to Wifi, it takes some seconds longer to unlock the user session. It seems gdm3 is waiting for an active network sonnection. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** No longer affects: virtualbox (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java source package
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** No longer affects: virtualbox-hwe (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java source
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: virtualbox (Ubuntu) Status: New => Fix Released -- 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/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java
[Desktop-packages] [Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) -- 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-desktop-icons package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New 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-desktop-icons/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
This bug was fixed in the package fonts-noto-cjk -
1:20190409+repack1-0ubuntu0.18.04
---
fonts-noto-cjk (1:20190409+repack1-0ubuntu0.18.04) bionic; urgency=medium
* New upstream release.
- This upgrades the Noto Sans CJK fonts to version 2.001, which
includes glyphs for Japan's new era Reiwa (LP: #1834406).
-- Gunnar Hjalmarsson Thu, 27 Jun 2019 07:01:00
+0200
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Released
Status in language-selector source package in Bionic:
Fix Released
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
This bug was fixed in the package language-selector - 0.188.3
---
language-selector (0.188.3) bionic; urgency=medium
* fontconfig/69-language-selector-zh-hk.conf:
* fontconfig/64-language-selector-prefer.conf:
Changes because version 2.001 of the Noto Sans CJK fonts includes
Noto Sans CJK HK and Noto Sans Mono CJK HK (LP: #1834406).
-- Gunnar Hjalmarsson Fri, 28 Jun 2019 19:12:00
+0200
** Changed in: language-selector (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: fonts-noto-cjk (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Released
Status in language-selector source package in Bionic:
Fix Released
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
When can we expect this fix to be back-ported to 18.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Bug description: *Impact This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). Test Case 1) Go to unity-control-center 2) Click sharing (Remote desktop) * Regression potential None The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+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 421537] Re: need a way to rotate video playback
I use Avdshare Video Converter to rotate videos. It has both Mac and Windows version. Step 1: Add video to Avdshare Video Converter Step 2: "Effect" button to open the 'Video Effect' window; Then click '90 Clockwise button' to rotate video file 90 degrees, 180 degrees, 270 degrees; or click 'Flip Horizontal' button Step 3: Click Convert button to finish rotating videos. Here is the step by step guide: https://www.avdshare.com/rotate-mov- file-90-degrees-180-degrees-or-270-degrees -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/421537 Title: need a way to rotate video playback Status in Totem: Fix Released Status in totem package in Ubuntu: Fix Released Bug description: Binary package hint: totem have problems when viewing mov files from cell phone. the viedo is turned 90 degrees to the left. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux 2.6.28-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/421537/+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 1834406] Update Released
The verification of the Stable Release Update for language-selector has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Committed
Status in language-selector source package in Bionic:
Fix Committed
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
This bug was fixed in the package language-selector - 0.194.1
---
language-selector (0.194.1) disco; urgency=medium
* fontconfig/69-language-selector-zh-hk.conf:
* fontconfig/64-language-selector-prefer.conf:
Changes because version 2.001 of the Noto Sans CJK fonts includes
Noto Sans CJK HK and Noto Sans Mono CJK HK (LP: #1834406).
-- Gunnar Hjalmarsson Fri, 28 Jun 2019 19:08:00
+0200
** Changed in: language-selector (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Committed
Status in language-selector source package in Bionic:
Fix Committed
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
I feel like this update has been in -proposed long enough now. Also, the
fix has been verified and package used by 3 people at least (as seen in
comments #14, #15 and #16), so that's already quite good. If no issues
have been noticed so far, not sure if waiting any longer makes any
sense.
Let me release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Committed
Status in language-selector source package in Bionic:
Fix Committed
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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 1834406] Re: Upgrade Noto Sans CJK fonts to version 2.001
This bug was fixed in the package fonts-noto-cjk -
1:20190409+repack1-0ubuntu0.19.04
---
fonts-noto-cjk (1:20190409+repack1-0ubuntu0.19.04) disco; urgency=medium
* New upstream release.
- This upgrades the Noto Sans CJK fonts to version 2.001, which
includes glyphs for Japan's new era Reiwa (LP: #1834406).
-- Gunnar Hjalmarsson Thu, 27 Jun 2019 07:01:00
+0200
** Changed in: fonts-noto-cjk (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1834406
Title:
Upgrade Noto Sans CJK fonts to version 2.001
Status in fonts-noto-cjk package in Ubuntu:
Fix Released
Status in language-selector package in Ubuntu:
Fix Released
Status in fonts-noto-cjk source package in Bionic:
Fix Committed
Status in language-selector source package in Bionic:
Fix Committed
Status in fonts-noto-cjk source package in Disco:
Fix Released
Status in language-selector source package in Disco:
Fix Released
Status in fonts-noto-cjk package in Debian:
New
Bug description:
[Impact]
Due to Japan's new era, a Unicode character has been introduced which
represents the era name (Reiwa) as one single character. The version
of fonts-noto-cjk in the stable releases does not support the new
character, which is what motivates a backport of the eoan fonts-noto-
cjk version. The proposed SRU is in line with the meta bug #1828884.
This means an upgrade of Noto Sans CJK from version 1.004 to 2.001,
and it will bring a few other changes in the bargain. Most notably a
new set of Hong Kong fonts has been added to the previous ones
(simplified and traditional Chinese, Japanese, and Korean). Attached
to this bug report please see the file noto-sans-cjk-news.txt with
upstream's detailing of the changes.
[Test Case]
Install from {bionic,disco}-proposed:
- fonts-noto-cjk
- fonts-noto-cjk-extra
- language-selector-common
- language-selector-gnome
1. The Reiwa glyph
--
Visit http://people.ubuntu.com/~gunnarhj/square-era-name-reiwa.html
and find that a proper Japanese character, and not a tofu, is shown.
2. Presence and configuration of HK fonts
-
(This also bears on the language-selector changes.)
* Install the Hong Kong locale:
sudo locale-gen zh_HK.UTF-8
* Run this command:
LC_CTYPE=zh_HK.UTF-8 fc-match
and find that it returns:
NotoSansCJK-Regular.ttc: "Noto Sans CJK HK" "Regular"
3. General use
--
Browse some web sites with Chinese, Japanese or Korean contents and
confirm that the upgrade does not cause any font rendering issues.
[Regression Potential]
This somewhat aggressive SRU proposal is based on trust in Google and
Adobe as solid upstream providers of these fonts. Version 2.000 (which
includes most of the changes) was released in November 2018, while
version 2.001 (with the Reiwa glyph) was released in April 2019.
Serious problems should have been known by now. The upstream bug
tracker gives no cause for concern:
https://github.com/googlefonts/noto-cjk/issues
It may be worth mentioning that the fonts are provided as OTC files,
and we don't compile those files ourselves. Hence just patching the
new glyph would not be a practicable option.
It would be easy to reverse this upgrade, if regressions would be
reported. Basically we are talking about 7 files on the file system.
[Other Info re. eoan]
Since Debian hasn't packaged this yet, we have created a modified
.orig.tar.xz file where 7 .ttc files (plus NEWS and HISTORY) differ
from version 1:20181130+repack1-1~exp1, i.e. the latest Debian upload.
There is no other Ubuntu/Debian delta, so as soon as Debian has
catched up, it will be fine to start syncing again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1834406/+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
