[Desktop-packages] [Bug 1036831] Re: SIGFPE crash with crafted PAF file
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1036831 Title: SIGFPE crash with crafted PAF file Status in libsndfile package in Ubuntu: Fix Released Bug description: When opening a crafted PAF file with channels=0 in the header, I receive a floating point exception error from libsndfile. I have verified this is different than any of the reported SIGFPEs in CVE-2009-4835, as they don't work on v21 or v25. This has been tested on two systems with four versions of libsndfile: Ubuntu 10.04.4: *libsndfile-1.0.20 from CVE-2009-4835 reports *libsndfile-1.0.21-2 from /usr/lib via the 10.04 repository *libsndfile-1.0.25 compiled on the machine from the author's source page Ubuntu 12.04 *libsndfile-1.0.25-4 from /usr/lib/x86_64-linux-gnu via the 12.04 repository *libsndfile-1.0.25 compiled on the machine from the author's source page On 10.04.4 I used the test programs "lt-sndfile-info", "lt-sndfile-to- text", and "Audacity 1.3.12-beta". On 12.04 I just used "lt-sndfile- to-text". An example: $ ./lt-sndfile-info a.paf Version : libsndfile-1.0.25 Floating point exception I have attached a tar file with the crafted audio file, a.paf. It also includes another, b.paf, where the only change is channels=1 to demonstrate different behavior. Though this isn't a serious problem (libsndfile isn't a service), I've tagged it as a security vulnerability since I presume it's going to be a CWE_369 (I haven't looked at the source myself). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1036831/+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 900332] Re: libsndfile1 unable to encode .wav files
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/900332 Title: libsndfile1 unable to encode .wav files Status in libsndfile package in Ubuntu: Fix Released Bug description: I've attempted to use several different packages to encode .wav files (2 standards, GSM 6.10 or 16 bit PCM) - each package returns the most garbled error message which I've ever seen in my life. They suggest the disk is full (which it isn't, I have 129.6GB left on here) and then present the following (note, this contains unicode symbols, you may not see it as I do:) Error while writing WAV (Microsoft) file (disk full?). Libsndfile says "æ OãÐøÇE " Now your guess is as good as mine, and I'm no cryptographer, but that message from Libsndfile says "I'm borked, please fix me!" Seriously, this error is affecting use of programs like Audacity, kdenlive, VLC and others which use the .wav format for encoding media. Any help to figure out what on earth is going on would be welcomed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-14-generic 3.0.0-14.23 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thor 1605 F pulseaudio thor 4280 F audacity CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd7dfc000 irq 43' Mixer name : 'Realtek ALC880' Components : 'HDA:10ec0880,0880,00090500' Controls : 38 Simple ctrls : 22 Date: Mon Dec 5 15:30:53 2011 HibernationDevice: RESUME=UUID=850f320f-babd-41bc-b99a-961612f5d565 HotplugNewDevices: HotplugNewMounts: InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) MachineType: HP Pavilion 061 PW571AA-ABU t830.uk ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=ea8e7999-d27b-451e-b237-ddf269fcd803 ro noplymouth --verbose RelatedPackageVersions: linux-restricted-modules-3.0.0-14-generic N/A linux-backports-modules-3.0.0-14-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: lirc_sir Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel. UpgradeStatus: Upgraded to oneiric on 2011-10-15 (50 days ago) dmi.bios.date: 01/23/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.28 dmi.board.name: Grouper dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 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.:bvr3.28:bd01/23/2006:svnHPPavilion061:pnPW571AA-ABUt830.uk:pvr03p0211RE101GROUP00:rvnASUSTeKComputerINC.:rnGrouper:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: PW571AA-ABU t830.uk dmi.product.version: 03p0211RE101GROUP00 dmi.sys.vendor: HP Pavilion 061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/900332/+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 999994] Re: /usr/lib/x86_64-linux-gnu/libsndfile.so.1: undefined symbol: vorbis_version_string
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1
---
libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium
* debian/rules: forcefully enable tests (they are disabled by default on
riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries
(LP: #1917650)
-- Olivier Tilloy Wed, 03 Mar 2021
17:53:18 +0100
** Changed in: libsndfile (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsndfile in Ubuntu.
https://bugs.launchpad.net/bugs/94
Title:
/usr/lib/x86_64-linux-gnu/libsndfile.so.1: undefined symbol:
vorbis_version_string
Status in libsndfile package in Ubuntu:
Fix Released
Bug description:
When I try to run virtualbox, I get the message:
VirtualBox: supR3HardenedMainGetTrustedMain:
dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed:
/usr/lib/x86_64-linux-gnu/libsndfile.so.1: undefined symbol:
vorbis_version_string
I have tried installing and re-installing libsndfile1 and anything
"vorbis" that seems like it might have a positive influence on this
file.
I initially thought the problem was with virtualbox, but after filing
a bug with virtualbox (https://www.virtualbox.org/ticket/10567), they
claim it's not with virtualbox. I have tried both the ubuntu version
of virtualbox and the one from the virtualbox.org site that's built
for ubuntu 12.04. Both fail with the same error message.
Help!!!
(The annoying thing is that I don't use the sound in virtualbox, but I'm
being prevented from working because of this bug/dependency with libsndfile!)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libsndfile1 1.0.25-4
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 15 16:49:15 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/tcsh
SourcePackage: libsndfile
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/94/+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 1546685] Re: package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1546685 Title: package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libsndfile package in Ubuntu: Fix Released Bug description: when i try install gparted the process stop and appear the error message ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Wed Feb 17 16:22:55 2016 DuplicateSignature: package:libsndfile1:amd64:1.0.25-9.1ubuntu0.15.10.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-02-17 (0 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: libsndfile Title: package libsndfile1:amd64 1.0.25-9.1ubuntu0.15.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1546685/+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 1807826] Re: libsndfile crashed with SIGSEGV in __memset_avx2()
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1807826 Title: libsndfile crashed with SIGSEGV in __memset_avx2() Status in libsndfile package in Ubuntu: Fix Released Bug description: - When running 'sndfile-info' program from 'sndfile-programs' package, the program crashed while trying to write on invalid memory address. The crash point is within libsndfile.so library, so the bug seems to be in 'libsndfile' package. - 'sndfile-play' program from 'sndfile-programs' package also crashes with the same input. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sndfile-programs 1.0.25-10ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 10 23:25:24 2018 ExecutablePath: /usr/bin/sndfile-info InstallationDate: Installed on 2018-12-06 (5 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcCmdline: sndfile-info crash-1_00063474 Signal: 11 SourcePackage: libsndfile StacktraceTop: __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161 memset (__len=, __ch=0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:90 paf24_read_block (psf=, ppaf24=0x7f5f72d0c010) at paf.c:496 paf24_init (psf=0x840420) at paf.c:375 paf_open (psf=psf@entry=0x840420) at paf.c:149 Title: sndfile-info crashed with SIGSEGV in __memset_avx2() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1807826/+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 1807823] Re: libsndfile crashed with SIGSEGV in wav_w64_read_fmt_chunk()
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1807823 Title: libsndfile crashed with SIGSEGV in wav_w64_read_fmt_chunk() Status in libsndfile package in Ubuntu: Fix Released Bug description: - When running 'sndfile-info' program from 'sndfile-programs' package, the program crashed while trying to write on invalid memory address. The crash point is wav_w64_read_fmt_chunk() function of libsndfile.so, so the bug seems to reside in 'libsndfile' package. - 'sndfile-play' program from 'sndfile-programs' package also crashes with the same input. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sndfile-programs 1.0.25-10ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 10 22:51:36 2018 ExecutablePath: /usr/bin/sndfile-info InstallationDate: Installed on 2018-12-06 (5 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcCmdline: sndfile-info crash-0_00018173 SegvAnalysis: Segfault happened at: 0x7ff526d6a3d1 : movb $0x0,0x10(%rbx,%rcx,1) PC (0x7ff526d6a3d1) ok source "$0x0" ok destination "0x10(%rbx,%rcx,1)" (0x100d4b42f) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: libsndfile StacktraceTop: wav_w64_read_fmt_chunk (psf=psf@entry=0xd4b420, fmtsize=875972178) at wav_w64.c:333 rf64_read_header (framesperblock=, blockalign=, psf=0xd4b420) at rf64.c:224 rf64_open (psf=psf@entry=0xd4b420) at rf64.c:88 psf_open_file (psf=0xd4b420, sfinfo=sfinfo@entry=0x7ffd71fd0930) at sndfile.c:2746 sf_open (path=path@entry=0x7ffd71fd2301 "crash-0_00018173", mode=mode@entry=16, sfinfo=sfinfo@entry=0x7ffd71fd0930) at sndfile.c:333 Title: sndfile-info crashed with SIGSEGV in wav_w64_read_fmt_chunk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1807823/+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 1807825] Re: libsndfile crashed with stack overflow in psf_binheader_readf()
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1807825 Title: libsndfile crashed with stack overflow in psf_binheader_readf() Status in libsndfile package in Ubuntu: Fix Released Bug description: - When running 'sndfile-info' program from 'sndfile-programs' package, the program crashed with stack overflow (possibly by unbounded recursion of guess_file_type() function). The crash point is within libsndfile.so library, so the bug seems to be in 'libsndfile' package. - 'sndfile-play' program from 'sndfile-programs' package also crashes with the same input. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sndfile-programs 1.0.25-10ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 10 23:16:55 2018 ExecutablePath: /usr/bin/sndfile-info InstallationDate: Installed on 2018-12-06 (5 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcCmdline: sndfile-info crash-0_00010633 Signal: 11 SourcePackage: libsndfile StacktraceTop: psf_binheader_readf (psf=psf@entry=0x95e420, format=0x7f36299f6651 "", format@entry=0x7f36299f664f "pb") at common.c:1040 id3_skip (psf=psf@entry=0x95e420) at id3.c:35 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2423 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2424 guess_file_type (psf=psf@entry=0x95e420) at sndfile.c:2424 Title: sndfile-info crashed with SIGSEGV in psf_binheader_readf() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1807825/+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 1917650] Re: FTBFS on riscv64 because tests are disabled by default
This bug was fixed in the package libsndfile - 1.0.31-1ubuntu1 --- libsndfile (1.0.31-1ubuntu1) hirsute; urgency=medium * debian/rules: forcefully enable tests (they are disabled by default on riscv64 in Ubuntu) because libsndfile1-dev wants to install test binaries (LP: #1917650) -- Olivier Tilloy Wed, 03 Mar 2021 17:53:18 +0100 ** Changed in: libsndfile (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1917650 Title: FTBFS on riscv64 because tests are disabled by default Status in libsndfile package in Ubuntu: Fix Released Bug description: dpkg defaults to nocheck on riscv64 (see bug #1891686), and as a consequence libsndfile fails to build from source, because libsndfile1-dev wants to install test binaries that weren't built: dh: command-omitted: The call to "dh_auto_test -a" was omitted due to "DEB_BUILD_OPTIONS=nocheck" dh_install: warning: Cannot find (any matches for) "tests/.libs/*" (tried in ., debian/tmp) dh_install: error: missing files, aborting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1917650/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
Hint from another user: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868#note_1050922 @ogra -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+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 1917848] [NEW] thunderbird unwarrantly pastes context info
Public bug reported: When copying some text into a thunderbird email, context information is added as well (see attached). will delete the text proper, but not the context information. -- Version:1.0 StartHTML:000277 EndHTML:024342 StartFragment:022201 EndFragment:024302 SourceURL:file:///Y:\us\Humphrey\Articles\Constructing%20Aristotle's%20categories\How%20to%20derive%20Aristotle’s%20categories%20from%20First%20Principles%20-16.02.docx -- In order to only paste the text proper, one needs to "paste without formatting". This is not intuitive. Please fix. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: humphrey 287754 F pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Mar 5 17:55:20 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/thunderbird/thunderbird ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2021-01-14 (50 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev eno1 proto dhcp metric 100 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 metric 600 MostRecentCrashID: bp-d8ee9043-ef35-483e-8c89-c1b0d0181224 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.10.0/20200629235513 (Out of date) Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-03-05 17-54-51.png" https://bugs.launchpad.net/bugs/1917848/+attachment/5473283/+files/Screenshot%20from%202021-03-05%2017-54-51.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1917848 Title: thunderbird unwarrantly pastes context info Status in thunderbird package in Ubuntu: New Bug description: When copying some text into a thunderbird email, context information is added as well (see attached). will delete the text proper, but not the context information. -- Version:1.0 StartHTML:000277 EndHTML:024342 StartFragment:022201 EndFragment:024302 SourceURL:file:///Y:\us\Humphrey\Articles\Constructing%20Aristotle's%20categories\How%20to%20derive%20Aristotle’s%20categories%20from%20First%20Principles%20-16.02.docx -- In order to only paste the text proper, one needs to "paste without formatting". This is not intuitive. Please fix. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False
[Desktop-packages] [Bug 1707023] Re: mobile network connection cannot be added
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1707023 Title: mobile network connection cannot be added Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 amd64 daily, encrypted home, German language I tried adding a mobile connection (LTE), clicked trough the dialog but the connection will not show up in the list to select from. lsusb: Bus 002 Device 002: ID 12d1:15bb Huawei Technologies Co., Ltd. syslog: gnome-control-c[2348]: value "((NMSettingSerialParity) 110)" of type 'NMSettingSerialParity' is invalid or out of range for property 'parity' of type 'NMSettingSerialParity' NetworkManager[955]: [1502546435.3033] audit: op="connection- add-activate" pid=2348 uid=1000 result="fail" reason="gsm.username: property is empty" gnome-control-c[2348]: Failed to add new connection: (7) gsm.username: property is empty To reproduce: go to "Settings" - "Network" - "Mobile Broadband", click on "Add new connection" in the "Network" field, click next to the Country list select "Austria", click next select "HoT" click next and again next then click Apply. In the "Network" field no connection is added, clicking "Add new connection does not work until until i leave and reenter the "Network" section of "Settings". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1707023/+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 1917844] Re: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
** Tags added: focal groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917844 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917844/+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 1917845] Re: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
*** This bug is a duplicate of bug 1917844 *** https://bugs.launchpad.net/bugs/1917844 ** This bug has been marked a duplicate of bug 1917844 When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917845 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917845/+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 1917846] Re: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
*** This bug is a duplicate of bug 1917844 *** https://bugs.launchpad.net/bugs/1917844 ** This bug has been marked a duplicate of bug 1917844 When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917846 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917846/+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 1917844] [NEW] When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
Public bug reported: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Picture of no mobile broadband details" https://bugs.launchpad.net/bugs/1917844/+attachment/5473275/+files/NoMobileBroadbandDetails.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917844 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917844/+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 1917845] [NEW] When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
Public bug reported: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Picture of no mobile broadband details" https://bugs.launchpad.net/bugs/1917845/+attachment/5473276/+files/NoMobileBroadbandDetails.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917845 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917845/+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 1917846] [NEW] When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting.
Public bug reported: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Picture of no mobile broadband details" https://bugs.launchpad.net/bugs/1917846/+attachment/5473277/+files/NoMobileBroadbandDetails.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1917846 Title: When I plug in a modem, I can only see the mobile broadband details after reopening Network Setting. Status in gnome-control-center package in Ubuntu: New Bug description: When I am in the UI of Network Setting, if I insert a modem, mobile broadband has successfully connected at this time, but it is not refreshed in Network Setting, and mobile broadband does not appear in it. I can only see the mobile broadband details when I reopen Network Setting. it can reproduce in: OS：Ubuntu20.10 gnome-control-center：3.38.3-0ubuntu1 OS:Ubuntu20.04 gnome-control-center：3.36.5-0ubuntu1 Expectation：When I plug in a modem, the Network Setting will refresh automatically and the mobile broadband details will appear in it. Other information：When I unplug the modem, the Network Setting will refresh, and we can see that mobile broadband disappears in it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1917846/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
For personal accounts nothing is lost from what I can see so far, all data is transferred to a blank profile. My god, though, this could surely have been handled better. Not even a banner inside chromium to let us know like what I think happened with Windows Xp. -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917840] [NEW] Please sync pipewire 0.3.22-2 from Debian
Public bug reported: Please sync pipewire 0.3.22-2 from Debian to hirsute. It's a bugfix-only release required to fix bug 1916716: pipewire (0.3.22-2) experimental; urgency=medium [ Daniel van Vugt ] * Fix "the metadata crash" (LP: #1916716). Using upstream commit 3673265ae20d7b59e89cad6c5238c232796731b2 which is scheduled for inclusion in release 0.3.23. -- Iain Lane Thu, 04 Mar 2021 11:09:52 + https://salsa.debian.org/utopia-team/pipewire/-/tags/debian%2F0.3.22-2 https://salsa.debian.org/utopia-team/pipewire/-/commits/debian/experimental ** Affects: pipewire (Ubuntu) Importance: High Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1917840 Title: Please sync pipewire 0.3.22-2 from Debian Status in pipewire package in Ubuntu: New Bug description: Please sync pipewire 0.3.22-2 from Debian to hirsute. It's a bugfix- only release required to fix bug 1916716: pipewire (0.3.22-2) experimental; urgency=medium [ Daniel van Vugt ] * Fix "the metadata crash" (LP: #1916716). Using upstream commit 3673265ae20d7b59e89cad6c5238c232796731b2 which is scheduled for inclusion in release 0.3.23. -- Iain Lane Thu, 04 Mar 2021 11:09:52 + https://salsa.debian.org/utopia-team/pipewire/-/tags/debian%2F0.3.22-2 https://salsa.debian.org/utopia-team/pipewire/-/commits/debian/experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1917840/+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 1909028] Re: Lines coming up on screen
[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/1909028 Title: Lines coming up on screen Status in xorg-server package in Ubuntu: Expired Bug description: Multiple times I see that the scrolling/ video playing is not smooth and things come up in layers. This issue is especially visible while scrolling in vertical (tablet) orientation and watching videos with a lot of motion. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 22:43:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80d0] Subsystem: Hewlett-Packard Company GM108M [GeForce 930M] [103c:80d0] InstallationDate: Installed on 2020-12-15 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:57c4 Realtek Semiconductor Corp. HP Truevision HD Bus 001 Device 007: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=2518abd7-c310-4c54-84cb-86e6f8d53f4a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.19 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80D0 dmi.board.vendor: HP dmi.board.version: 84.29 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP ENVY x360 Convertible dmi.product.sku: T5Q56PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909028/+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 1864178] Re: Rhythmbox crashes when trying to connect to iPhone
Same problem in 20.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1864178 Title: Rhythmbox crashes when trying to connect to iPhone Status in Rhythmbox: New Status in rhythmbox package in Ubuntu: Triaged Bug description: I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. I opened Rhythmbox from the terminal to see the error and I got this ``` (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type NULL, target type b) ** Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) [1]15045 abort (core dumped) rhythmbox ``` Details of the current system: ``` lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ``` ``` apt-cache policy rhythmbox rhythmbox: Installed: 3.4.3-2ubuntu1 Candidate: 3.4.3-2ubuntu1 Version table: *** 3.4.3-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ``` What I expected to happen: I was expected Rhythmbox to show my iPhone under "devices" What actually happned: Rhythmbox just crashed To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1864178/+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 1917806] Re: Xorg freeze
Thanks for the bug report. 1. Next time the freeze happens and then doesn't (failed login, reboot, successful login), please run this command: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 2. Please check for any crash reports using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 3. Try logging into 'Ubuntu on Wayland' by clicking the button in the bottom right corner of the screen before you enter your password. Does that avoid the problem? ** Tags added: amdgpu ** Summary changed: - Xorg freeze + [amdgpu] Freezes after submitting the login password ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917806 Title: [amdgpu] Freezes after submitting the login password Status in gnome-shell package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Freezes after submitting the login password. If I shutdown the system it usually works afterwards on the first boot, but not subsequent reboots. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency 5.4.86 Uname: Linux 5.4.0-66-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 06:39:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-12-07 (87 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-lowlatency root=UUID=d8850dd9-0462-4a0b-a22c-24c0df1551a7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/01/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3405:bd02/01/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917806/+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 1917801] Re: Multi monitor bug opening windows
Thanks for the bug report. We really should report this to the Mutter developers, but to be sure that wouldn't be a waste of their time, please first ensure you're not using any extensions (in the 'Extensions' app) that might be causing this. Then report it at: https://gitlab.gnome.org/GNOME/mutter/issues ** Tags added: multimonitor ** Summary changed: - Multi monitor bug opening windows + Multi monitor bug opening windows (not responsive to input in the location it is drawn) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1917801 Title: Multi monitor bug opening windows (not responsive to input in the location it is drawn) Status in mutter package in Ubuntu: New Bug description: When i open a window like Spotify or GitKracken, that should open in my second monitor (because i always use them there), Ubuntu draws it in my main monitor, but, if i try to move it, resize or press an area of the window, it selects the window that is under it (like if the windows does not logically exist there). If i click on the window title bar, it sometimes appears on the second monitor and is resized (also if i press the minimize button or others). Sometimes the window is not responding until i do not minimize it from the dock and re- maximize it. Once it does that everything works well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 20:18:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (46 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1917801] Re: Multi monitor bug opening windows
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1917801 Title: Multi monitor bug opening windows Status in mutter package in Ubuntu: New Bug description: When i open a window like Spotify or GitKracken, that should open in my second monitor (because i always use them there), Ubuntu draws it in my main monitor, but, if i try to move it, resize or press an area of the window, it selects the window that is under it (like if the windows does not logically exist there). If i click on the window title bar, it sometimes appears on the second monitor and is resized (also if i press the minimize button or others). Sometimes the window is not responding until i do not minimize it from the dock and re- maximize it. Once it does that everything works well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 20:18:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (46 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917801/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
The fix isn't in the 21.0 branch yet. Only on master (22). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1917816] [NEW] Firefox not loading gifv, gifs
Public bug reported: Firefox 86.0-3, fresh installation of Ubuntu 20.04 with no additional repositories added other than for Google Chrome, no third-party drivers, etc. Full dist-upgrade run, rebooted and otherwise working fine. A version of firefox was pulled down using 'snap install firefox' and it did not have the same issues. Some gifs work, but no gifv so far. Not sure of the pattern. Example gifv from imgur.com: https://i.imgur.com/xFVwISe.gifv I've disabled all restrictions in the privacy and security settings. I've also started in safe-mode so no extensions. No reports of this issue on other operating systems or on https://bugzilla.mozilla.org No huge impact to me personally, but maybe something to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 86.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:40:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-03-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=86.0/20210222142601 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502LW.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502LW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502LW.309:bd09/01/2020:br5.17:efr3.8:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM15GU502LW_GU502LW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502LW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus M15 dmi.product.name: ROG Zephyrus M15 GU502LW_GU502LW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1917816 Title: Firefox not loading gifv, gifs Status in firefox package in Ubuntu: New Bug description: Firefox 86.0-3, fresh installation of Ubuntu 20.04 with no additional repositories added other than for Google Chrome, no third-party drivers, etc. Full dist-upgrade run, rebooted and otherwise working fine. A version of firefox was pulled down using 'snap install firefox' and it did not have the same issues. Some gifs work, but no gifv so far. Not sure of the pattern. Example gifv from imgur.com: https://i.imgur.com/xFVwISe.gifv I've disabled all restrictions in the privacy and security settings. I've also started in safe-mode so no extensions. No reports of this issue on other operating systems or on https://bugzilla.mozilla.org No huge impact to me personally, but maybe something to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 86.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210222142601 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:40:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
[Desktop-packages] [Bug 1917812] Re: extracting archives from within nautilus omits subfolders
I am experiencing this issue on two laptops with 20.04.2. But I just verified that it indeed works as expected with a Live ISO inside a VM. Is there a way to debug this? -- 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/1917812 Title: extracting archives from within nautilus omits subfolders Status in nautilus package in Ubuntu: New Bug description: When extracting ZIP archives from within nautilus (e.g. right-click -> "Extract Here") the extracted file structure is missing subfolders. Reproduce: 1. download a ZIP archive that includes files and folders in the root (e.g. https://github.com/electron/electron/releases/download/v12.0.0/electron-v12.0.0-linux-x64.zip) 2. within nautilus right-click on the archive and select "Extract Here" 3. check the extracted folder, you will see that only the files have been extracted, the folders are missing This is an issue that was recently introduced, as this used to work a while ago on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 22:09:52 2021 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917812/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
I agree the statement is a bit ambiguous, but I *think* it's meant as "data that is stored locally only (and not synced) will continue to be available locally". I.e. if it wasn't synced, it won't be 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917812] Re: extracting archives from within nautilus omits subfolders
Thank you for your bug report, it works correctly on the current Ubuntu serie. nautilus uses libarchive but that package didn't change in focal, unsure why it was working and isn't anymore for you... ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1917812 Title: extracting archives from within nautilus omits subfolders Status in nautilus package in Ubuntu: New Bug description: When extracting ZIP archives from within nautilus (e.g. right-click -> "Extract Here") the extracted file structure is missing subfolders. Reproduce: 1. download a ZIP archive that includes files and folders in the root (e.g. https://github.com/electron/electron/releases/download/v12.0.0/electron-v12.0.0-linux-x64.zip) 2. within nautilus right-click on the archive and select "Extract Here" 3. check the extracted folder, you will see that only the files have been extracted, the folders are missing This is an issue that was recently introduced, as this used to work a while ago on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 22:09:52 2021 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917812/+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 1898389] Re: browser frequently crashing with trap int3
I've switched to firefox, that solved the problem! -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Expired Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages *** 85.0.4183.83-0ubuntu0.16.04.2 100 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages dmesg: [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 sp:7ffdfc31ca70 error:0 [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 sp:7ffd8fc04770 error:0 [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 sp:7ffdfc31b2c0 error:0 [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be sp:7ffdfc31bd40 error:0 [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 sp:7ffdfc31cab0 error:0 [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 sp:7ffdfc31b300 error:0 [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 sp:7ffdfc31c640 error:0 [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be sp:7ffdfc31a6a0 error:0 [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 sp:7fe1dcaf95e0 error:0 [519367.329864] traps: chromium-browse[24588] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.357674] traps: chromium-browse[24558] trap invalid opcode ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 sp:7ffdfc316260 error:0 [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 sp:7ffdfc31abd0 error:0 [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be sp:7ffdfc31bbb0 error:0 [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 sp:7ffdfc31d020 error:0 [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 sp:7ffdfc3165c0 error:0 [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 sp:7ffdfc3164c0 error:0 [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 sp:7ffdfc31c5b0 error:0 [519429.841404] traps: chromium-browse[24906] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
> data that they have stored locally will continue to be available locally. Doesn't forcing deletion of the profile violate this claim? -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917812] [NEW] extracting archives from within nautilus omits subfolders
Public bug reported: When extracting ZIP archives from within nautilus (e.g. right-click -> "Extract Here") the extracted file structure is missing subfolders. Reproduce: 1. download a ZIP archive that includes files and folders in the root (e.g. https://github.com/electron/electron/releases/download/v12.0.0/electron-v12.0.0-linux-x64.zip) 2. within nautilus right-click on the archive and select "Extract Here" 3. check the extracted folder, you will see that only the files have been extracted, the folders are missing This is an issue that was recently introduced, as this used to work a while ago on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 22:09:52 2021 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1917812 Title: extracting archives from within nautilus omits subfolders Status in nautilus package in Ubuntu: New Bug description: When extracting ZIP archives from within nautilus (e.g. right-click -> "Extract Here") the extracted file structure is missing subfolders. Reproduce: 1. download a ZIP archive that includes files and folders in the root (e.g. https://github.com/electron/electron/releases/download/v12.0.0/electron-v12.0.0-linux-x64.zip) 2. within nautilus right-click on the archive and select "Extract Here" 3. check the extracted folder, you will see that only the files have been extracted, the folders are missing This is an issue that was recently introduced, as this used to work a while ago on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 22:09:52 2021 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917812/+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 823155]
Still repro. Arch Linux 64-bit Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 94283af977246c70dbed4452d197b003d8bb14b9 CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 2 March 2021 -- 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/823155 Title: [Upstream] Impress Custom Animation Sound Effect not audible in Slide Show Status in LibreOffice: Confirmed Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a new Impress document via the Terminal: loimpress --nologo New Impress file -> click the rectangle containing "Click to add text" -> Under Tasks Custom Animation -> button Add... -> Entrance tab highlight Random Effects -> OK button -> right of Property ... button -> Effect tab -> change Sound dropdown apert -> OK button -> Slide Show and it plays the apert sound. 4) What happens instead is no sound is played during the slide show. Original Reporter Comments: I am using Ubuntu 11.04 Natty. I have tested this in Ubuntu 10.10 with OpenOffice.org presentation (Impress), same problem too. All in all I have tried this on 3 different computers. 2 on 11.04 and 1 on 10.10 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Tue Aug 9 16:59:45 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/823155/+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 823155]
Dear Buovjaga, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/823155 Title: [Upstream] Impress Custom Animation Sound Effect not audible in Slide Show Status in LibreOffice: Confirmed Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a new Impress document via the Terminal: loimpress --nologo New Impress file -> click the rectangle containing "Click to add text" -> Under Tasks Custom Animation -> button Add... -> Entrance tab highlight Random Effects -> OK button -> right of Property ... button -> Effect tab -> change Sound dropdown apert -> OK button -> Slide Show and it plays the apert sound. 4) What happens instead is no sound is played during the slide show. Original Reporter Comments: I am using Ubuntu 11.04 Natty. I have tested this in Ubuntu 10.10 with OpenOffice.org presentation (Impress), same problem too. All in all I have tried this on 3 different computers. 2 on 11.04 and 1 on 10.10 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Tue Aug 9 16:59:45 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/823155/+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 1898389] Re: browser frequently crashing with trap int3
Getting those traps as well, don't know if it is because of the snap usage or chromium: [941728.747452] traps: chrome[1912045] trap int3 ip:559081754d9e sp:7ffe0c20d510 error:0 in chrome[55907cad+780d000] [941731.964290] traps: chrome[1912059] trap int3 ip:559081754d9e sp:7ffe0c213e40 error:0 in chrome[55907cad+780d000] -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Expired Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages *** 85.0.4183.83-0ubuntu0.16.04.2 100 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages dmesg: [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 sp:7ffdfc31ca70 error:0 [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 sp:7ffd8fc04770 error:0 [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 sp:7ffdfc31b2c0 error:0 [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be sp:7ffdfc31bd40 error:0 [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 sp:7ffdfc31cab0 error:0 [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 sp:7ffdfc31b300 error:0 [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 sp:7ffdfc31c640 error:0 [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be sp:7ffdfc31a6a0 error:0 [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be sp:7ffdfc31ca40 error:0 [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 sp:7fe1dcaf95e0 error:0 [519367.329864] traps: chromium-browse[24588] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.357674] traps: chromium-browse[24558] trap invalid opcode ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in chromium-browser[558471f1c000+a1c4000] [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 sp:7ffdfc316260 error:0 [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 sp:7ffdfc31abd0 error:0 [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be sp:7ffdfc31bbb0 error:0 [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 sp:7ffdfc31d020 error:0 [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 sp:7ffdfc3165c0 error:0 [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 sp:7ffdfc3164c0 error:0 [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 sp:7ffdfc31c5b0 error:0 [519429.841404] traps: chromium-browse[24906] trap invalid opcode ip:558478cb1962 sp:7ffdfc31cb68 error:0 in chromium-browser[558471f1c000+a1c4000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+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 1917806] [NEW] Xorg freeze
Public bug reported: Freezes after submitting the login password. If I shutdown the system it usually works afterwards on the first boot, but not subsequent reboots. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency 5.4.86 Uname: Linux 5.4.0-66-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 06:39:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-12-07 (87 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-lowlatency root=UUID=d8850dd9-0462-4a0b-a22c-24c0df1551a7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/01/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3405:bd02/01/2021:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917806 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Freezes after submitting the login password. If I shutdown the system it usually works afterwards on the first boot, but not subsequent reboots. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-lowlatency 5.4.86 Uname: Linux 5.4.0-66-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 06:39:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314] InstallationDate: Installed on 2020-12-07 (87 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-lowlatency root=UUID=d8850dd9-0462-4a0b-a22c-24c0df1551a7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/01/2021 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string
[Desktop-packages] [Bug 1917801] [NEW] Multi monitor bug opening windows
*** This bug is a security vulnerability *** Public security bug reported: When i open a window like Spotify or GitKracken, that should open in my second monitor (because i always use them there), Ubuntu draws it in my main monitor, but, if i try to move it, resize or press an area of the window, it selects the window that is under it (like if the windows does not logically exist there). If i click on the window title bar, it sometimes appears on the second monitor and is resized (also if i press the minimize button or others). Sometimes the window is not responding until i do not minimize it from the dock and re-maximize it. Once it does that everything works well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] È una directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 20:18:29 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-43-generic, x86_64: installed nvidia, 460.39, 5.8.0-44-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1080] [1462:3362] InstallationDate: Installed on 2021-01-17 (46 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=34f5f1d0-f244-447f-8b6b-1ec5c14fe8f6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.B0 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.B0:bd06/05/2020:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "A video of the bug with GitKracken" https://bugs.launchpad.net/bugs/1917801/+attachment/5473097/+files/2021-03-04_21-05-35.mov ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917801 Title: Multi monitor bug opening windows Status in xorg package in Ubuntu: New Bug description: When i open a window like Spotify or GitKracken, that should open in my second monitor (because i always use them there), Ubuntu draws it in my main monitor, but, if i try to move it, resize or
[Desktop-packages] [Bug 1917800] [NEW] "Protocol not available" with bluetooth when pulseaudio-module-bluetooth is installed
Public bug reported: I know this is not the default configuration yet, but when using pipewire as a pulse replacement everything worked fine for me except bluetooth. When the connection failed it showed "Protocol not available" in bluetoothd's log. I noticed that once I removed pulseaudio-module-bluetooth bluez connected to pipewire fine. Seems like this might be a packaging problem that should be kept an eye on. ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1917800 Title: "Protocol not available" with bluetooth when pulseaudio-module- bluetooth is installed Status in pipewire package in Ubuntu: New Bug description: I know this is not the default configuration yet, but when using pipewire as a pulse replacement everything worked fine for me except bluetooth. When the connection failed it showed "Protocol not available" in bluetoothd's log. I noticed that once I removed pulseaudio-module-bluetooth bluez connected to pipewire fine. Seems like this might be a packaging problem that should be kept an eye on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1917800/+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 1917791] Re: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all
ubuntu-bug clearly identified the speaker was muted to 0%. The speaker should be the main audio source or the system should atleast save the changes to the audio setting and should not reset itself on every startup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1917791 Title: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: The system wont show internal laptop speaker in system settings. And keeps on defaulting/using headphone as main audio source. On every restart I have to use either alsamixer from terminal or pulseaudio software to select the speaker as main audio device, unmute it and increase the volume. Nothing is connected to the headphone jack. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:55:53 2021 InstallationDate: Installed on 2021-02-22 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio /dev/snd/pcmC0D0p: anique 1840 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2016 dmi.bios.release: 15.30 dmi.bios.vendor: Insyde dmi.bios.version: F.1E dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 817D dmi.board.vendor: HP dmi.board.version: 39.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 39.19 dmi.modalias: dmi:bvnInsyde:bvrF.1E:bd07/26/2016:br15.30:efr39.19:svnHP:pnHPStreamNotebookPC13:pvrType1ProductConfigId:rvnHP:rn817D:rvr39.13:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Notebook PC 13 dmi.product.sku: L2T26EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1917791/+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 1917791] [NEW] [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all
Public bug reported: The system wont show internal laptop speaker in system settings. And keeps on defaulting/using headphone as main audio source. On every restart I have to use either alsamixer from terminal or pulseaudio software to select the speaker as main audio device, unmute it and increase the volume. Nothing is connected to the headphone jack. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:55:53 2021 InstallationDate: Installed on 2021-02-22 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio /dev/snd/pcmC0D0p: anique 1840 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2016 dmi.bios.release: 15.30 dmi.bios.vendor: Insyde dmi.bios.version: F.1E dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 817D dmi.board.vendor: HP dmi.board.version: 39.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 39.19 dmi.modalias: dmi:bvnInsyde:bvrF.1E:bd07/26/2016:br15.30:efr39.19:svnHP:pnHPStreamNotebookPC13:pvrType1ProductConfigId:rvnHP:rn817D:rvr39.13:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Notebook PC 13 dmi.product.sku: L2T26EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1917791 Title: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: The system wont show internal laptop speaker in system settings. And keeps on defaulting/using headphone as main audio source. On every restart I have to use either alsamixer from terminal or pulseaudio software to select the speaker as main audio device, unmute it and increase the volume. Nothing is connected to the headphone jack. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 16:55:53 2021 InstallationDate: Installed on 2021-02-22 (10 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anique 1840 F pulseaudio /dev/snd/pcmC0D0p: anique 1840 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Stream Notebook PC 13, Realtek ALC3227, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2016 dmi.bios.release: 15.30 dmi.bios.vendor: Insyde dmi.bios.version: F.1E dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 817D dmi.board.vendor: HP dmi.board.version: 39.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 39.19 dmi.modalias: dmi:bvnInsyde:bvrF.1E:bd07/26/2016:br15.30:efr39.19:svnHP:pnHPStreamNotebookPC13:pvrType1ProductConfigId:rvnHP:rn817D:rvr39.13:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=STR X=Null dmi.product.name: HP Stream Notebook PC 13 dmi.product.sku: L2T26EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage
[Desktop-packages] [Bug 1917035] Re: [snap] packaging license missing
Perfect! Thank you Olivier. -- 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/1917035 Title: [snap] packaging license missing Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Hey there! I'm searching for the license under which the contents of the snap- from-source repository [1] are published. This repository is used by Canonical to build the chromium snap. The repository does not contain any LICENSE file, and the information does not appear to be given anywhere else either. As I'm not familiar with Launchpad, I already opened a question [2]. However, the given answers do not satisfy me. I hope a Canonical employee can shed some light on this. Some background: I'm maintaining a snap that is running on multiple Ubuntu Core devices. This snap uses puppeteer and therefore requires packaging a chromium instance. However, since headless chromium (snap) currently crashes on startup, which looks like a result of the changes made when switching to the gnome-extension [3], I can not build any new version, including security updates, of my snap until the headless issue is resolved. Therefore, I'm looking into the possibility of building the chromium snap myself with the changes to use the gnome-extension reverted, at least until the issue with Canonical's snap is fixed. [1] https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source [2] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/695729 [3] https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917035/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
Sorry I wasn't very clear, but it was only 2 commands, and your output is as expected. So you can safely delete ~/.local/share/applications/chromium_chromium.desktop, the icon should remain in your dock. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Invalid -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Invalid Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
Did I miss something? It looks like you may have referenced 3 commands but I only see 2. -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
echo $XDG_DATA_DIRS: /usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
gsettings get org.gnome.shell favorite-apps: ['chromium_chromium.desktop', 'nemo.desktop', 'org.gnome.gedit.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'shotwell.desktop', 'slack_slack.desktop', 'simple-scan.desktop', 'Zoom.desktop', 'gnome-system-monitor.desktop', 'flameshot.desktop', 'brackets_brackets.desktop', 'org.gnome.Calculator.desktop'] -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1916881] Re: Thunderbird unable to access external pgp keys
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916881 Title: Thunderbird unable to access external pgp keys Status in thunderbird package in Ubuntu: Confirmed Bug description: Since upgrading thunderbird to the latest ubuntu package 1:78.7.1+build1-0ubuntu0.20.04.1 (and thus throwing out enigmail) I cannot use encryption anymore. The 78 version of thunderbird has replaced enigmail with its own implementation of PGP encryption, and it is still able to decrypt messages accessing the pgp agent. But the access to gnupg seems to be completely broken. The keyring is completely empty, it does not now any public key and needs to learn from scratch. Even then, I cannot reply to an encrypted mail with an encrypted (unsigned!) answer, since thunderbird cannot find my key. To enable PGP functions at all, thunderbird requires to enter the settings and configure which pgp key belongs to the mailbox account, and offers to * create a new key * import from a file * use an external gnupg key (e.g. on smartcard) Since I'm using a smartcard key, I've chosen the third option and entered the key id, which is accepted, but not listed in the key manager. Even if my own key is technically not required to send an encrypted list (except for making the Sent folder readable for myself), I can't send the message. Thunderbird raises an error message because the configured key cannot be found on the keyring. Which is technically correct, since the import from gnupg didn't work, both with the smartcard and a regular soft key. Obviously, thunderbird has some problem accessing the gnupg keys. My first guess was that apparmor causes problems, but that's not the case. I've used strace to verify that thunderbird has access to ~/.gnupg , and indeed it can and does read the files, therefore I'm not sure, why it actually doesn't work. Nevertheless, it doesn't work and I currently can't send encrypted messages. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1759 F pulseaudio /dev/snd/pcmC0D0p: hadmut 1759 F...m pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt Date: Thu Feb 25 12:22:09 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-06-12 (257 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 bp-cd2c713c-37b0-4b60-9b06-b94130210125 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+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 1917035] Re: snap-from-source repo license missing
You are right Lorenz, [2] doesn't really answer your question. I have now added a LICENSE file to the packaging: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=551373c73af1d3e30f5f0536370359d6fd4f857f. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Committed ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Summary changed: - snap-from-source repo license missing + [snap] packaging license missing ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- 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/1917035 Title: [snap] packaging license missing Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Hey there! I'm searching for the license under which the contents of the snap- from-source repository [1] are published. This repository is used by Canonical to build the chromium snap. The repository does not contain any LICENSE file, and the information does not appear to be given anywhere else either. As I'm not familiar with Launchpad, I already opened a question [2]. However, the given answers do not satisfy me. I hope a Canonical employee can shed some light on this. Some background: I'm maintaining a snap that is running on multiple Ubuntu Core devices. This snap uses puppeteer and therefore requires packaging a chromium instance. However, since headless chromium (snap) currently crashes on startup, which looks like a result of the changes made when switching to the gnome-extension [3], I can not build any new version, including security updates, of my snap until the headless issue is resolved. Therefore, I'm looking into the possibility of building the chromium snap myself with the changes to use the gnome-extension reverted, at least until the issue with Canonical's snap is fixed. [1] https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source [2] https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/695729 [3] https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917035/+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 1916255] Re: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on
I should clarify that this bug occurs only when the xwayland session is used, in the x11 (xorg) session the caps lock works correctly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916255 Title: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on Status in gnome-shell package in Ubuntu: Triaged Bug description: Caps lock is not properly detected, for example if you log in with a password that is in upper case, when entering the desktop without deactivating caps lock, when trying to open an encrypted drive whose password is in upper case even though the indicator shows that Caps lock is active and detects it as if it were not. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 19 09:03:42 2021 DistUpgraded: 2020-10-24 20:57:52,724 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ae2] InstallationDate: Installed on 2020-04-09 (316 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Hewlett-Packard CQ2951LA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f43448ef-2a06-45ab-8bac-fe9e8907ff57 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to groovy on 2020-10-25 (117 days ago) dmi.bios.date: 08/31/2012 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.asset.tag: 3CR2390SBN dmi.board.name: 2AE2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: 3CR2390SBN dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: CQ2951LA dmi.product.sku: H3X53AA#ABM dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916255/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
Yes, I'm saying that you shouldn't need to have a copy of the desktop file unders ~/.local/share for GNOME shell to display it in your favourites bar. What is the output of the following commands for you? gsettings get org.gnome.shell favorite-apps echo $XDG_DATA_DIRS For me the first one outputs a list containing 'chromium_chromium.desktop', and the second one has a colon-separated list of paths, the last one being "/var/lib/snapd/desktop", which means that XDG-compliant desktop implementations (including GNOME Shell) know to look for desktop files there. -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1916881] Re: Thunderbird unable to access external pgp keys
** Tags added: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916881 Title: Thunderbird unable to access external pgp keys Status in thunderbird package in Ubuntu: Confirmed Bug description: Since upgrading thunderbird to the latest ubuntu package 1:78.7.1+build1-0ubuntu0.20.04.1 (and thus throwing out enigmail) I cannot use encryption anymore. The 78 version of thunderbird has replaced enigmail with its own implementation of PGP encryption, and it is still able to decrypt messages accessing the pgp agent. But the access to gnupg seems to be completely broken. The keyring is completely empty, it does not now any public key and needs to learn from scratch. Even then, I cannot reply to an encrypted mail with an encrypted (unsigned!) answer, since thunderbird cannot find my key. To enable PGP functions at all, thunderbird requires to enter the settings and configure which pgp key belongs to the mailbox account, and offers to * create a new key * import from a file * use an external gnupg key (e.g. on smartcard) Since I'm using a smartcard key, I've chosen the third option and entered the key id, which is accepted, but not listed in the key manager. Even if my own key is technically not required to send an encrypted list (except for making the Sent folder readable for myself), I can't send the message. Thunderbird raises an error message because the configured key cannot be found on the keyring. Which is technically correct, since the import from gnupg didn't work, both with the smartcard and a regular soft key. Obviously, thunderbird has some problem accessing the gnupg keys. My first guess was that apparmor causes problems, but that's not the case. I've used strace to verify that thunderbird has access to ~/.gnupg , and indeed it can and does read the files, therefore I'm not sure, why it actually doesn't work. Nevertheless, it doesn't work and I currently can't send encrypted messages. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1759 F pulseaudio /dev/snd/pcmC0D0p: hadmut 1759 F...m pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt Date: Thu Feb 25 12:22:09 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-06-12 (257 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 bp-cd2c713c-37b0-4b60-9b06-b94130210125 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+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 1916881] Re: Thunderbird unable to access external pgp keys
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1916881 Title: Thunderbird unable to access external pgp keys Status in thunderbird package in Ubuntu: Confirmed Bug description: Since upgrading thunderbird to the latest ubuntu package 1:78.7.1+build1-0ubuntu0.20.04.1 (and thus throwing out enigmail) I cannot use encryption anymore. The 78 version of thunderbird has replaced enigmail with its own implementation of PGP encryption, and it is still able to decrypt messages accessing the pgp agent. But the access to gnupg seems to be completely broken. The keyring is completely empty, it does not now any public key and needs to learn from scratch. Even then, I cannot reply to an encrypted mail with an encrypted (unsigned!) answer, since thunderbird cannot find my key. To enable PGP functions at all, thunderbird requires to enter the settings and configure which pgp key belongs to the mailbox account, and offers to * create a new key * import from a file * use an external gnupg key (e.g. on smartcard) Since I'm using a smartcard key, I've chosen the third option and entered the key id, which is accepted, but not listed in the key manager. Even if my own key is technically not required to send an encrypted list (except for making the Sent folder readable for myself), I can't send the message. Thunderbird raises an error message because the configured key cannot be found on the keyring. Which is technically correct, since the import from gnupg didn't work, both with the smartcard and a regular soft key. Obviously, thunderbird has some problem accessing the gnupg keys. My first guess was that apparmor causes problems, but that's not the case. I've used strace to verify that thunderbird has access to ~/.gnupg , and indeed it can and does read the files, therefore I'm not sure, why it actually doesn't work. Nevertheless, it doesn't work and I currently can't send encrypted messages. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1759 F pulseaudio /dev/snd/pcmC0D0p: hadmut 1759 F...m pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: LXQt Date: Thu Feb 25 12:22:09 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-06-12 (257 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-42a938ea-d29a-4ad6-95cd-df43e0210213 bp-cd2c713c-37b0-4b60-9b06-b94130210125 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Same problem: MPOW Bluetooth 5 dongle (Model: BH456A) $ uname -a Linux dg-dl 5.8.0-44-generic #50~20.04.1-Ubuntu SMP Wed Feb 10 21:07:30 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ rfkill ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 6 bluetooth hci0 unblocked unblocked $ lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation C226 Series Chipset Family Server Advanced SKU LPC Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K1200] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] (rev a1) 03:00.0 PCI bridge: ASMedia Technology Inc. Device 1182 04:03.0 PCI bridge: ASMedia Technology Inc. Device 1182 04:07.0 PCI bridge: ASMedia Technology Inc. Device 1182 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) $ dmesg | grep -i blue [2.641328] usb 3-7: Product: Bluetooth Radio [6.626592] Bluetooth: Core ver 2.22 [6.626603] Bluetooth: HCI device and connection manager initialized [6.626606] Bluetooth: HCI socket layer initialized [6.626607] Bluetooth: L2CAP socket layer initialized [6.626608] Bluetooth: SCO socket layer initialized [6.860576] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [6.861534] Bluetooth: hci0: RTL: rom_version status=0 version=1 [6.861534] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin [6.903755] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2 [6.903759] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found [ 97.431707] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 97.431708] Bluetooth: BNEP filters: protocol multicast [ 97.431711] Bluetooth: BNEP socket layer initialized [ 246.400802] usb 3-8: Product: Bluetooth Radio [ 246.406937] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 246.407880] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 246.407884] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin [ 246.407925] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2 [ 246.407929] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found [ 268.373795] usb 3-6: Product: Bluetooth Radio [ 268.377141] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 268.377947] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 268.377952] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin [ 268.378019] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2 [ 268.378025] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found [ 330.775006] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 330.776000] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 330.776003] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin [ 330.776037] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2 [ 330.776040] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found [ 418.646117] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 418.647121] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 418.647125] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761b_fw.bin [ 418.647168] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761b_fw.bin failed with error -2 [ 418.647172] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761b_fw.bin not found [ 435.976571] usb 3-7: Product: Bluetooth Radio [ 435.980209] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b
[Desktop-packages] [Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
This has been going on for a while. I found an article that suggested a solution for the disappearing icon be to add the .desktop file. I would certainly be interested in a better solution. Changing to "current" seems to have worked but I sense you hinting there is a larger problem in having to accomplish this in this manner. -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
You could try making it: Icon=/snap/chromium/current/chromium.png I'm curious as to why you need a copy of chromium_chromium.desktop in ~/.local/share for it to appear in your favourites bar. Isn't the one installed by the snap (in /var/lib/snapd/desktop/applications/chromium_chromium.desktop) good enough for this? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] [NEW] Icon location not updating in chromium_chromium.desktop
Public bug reported: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: New Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917771] Re: Icon location not updating in chromium_chromium.desktop
I should have mentioned - I can go in and update chromium_chromium.desktop with the new location, the icon appears and everything works fine. -- 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/1917771 Title: Icon location not updating in chromium_chromium.desktop Status in chromium-browser package in Ubuntu: New Bug description: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+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 1917764] Re: profile gets deleted on startup due to account "no longer allowed as the primary account"
*** This bug is a duplicate of bug 1917705 *** https://bugs.launchpad.net/bugs/1917705 ** This bug has been marked a duplicate of bug 1917705 "profile will be deleted" at startup after chromium 89 update -- 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/1917764 Title: profile gets deleted on startup due to account "no longer allowed as the primary account" Status in chromium-browser package in Ubuntu: New Bug description: I had chromium installed via snap : installed: 89.0.4389.72(1506) 145MB - This morning I ran chromium and got the following message Your account (...) is no longer allowed as the primary account. Because this account is managed by (...), your bookmarks, history, passwords and other settings will be cleared from this device. and, indeed, it was all gone. Impossible to synchronize to the account. I tried clearing ~/snap/chromium and ~/.config/chromium, but still could not restart synchronization. Then I tried reverting : $ snap revert chromium chromium revenu à 88.0.4324.182 and things went working again : I can login to the account and the bookmarks/history/etc. are synced again. I'm running Ubuntu 20.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917764/+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 1917764] Re: profile gets deleted on startup due to account "no longer allowed as the primary account"
I tried updating to latest/edge channel
$ sudo snap refresh chromium --channel=latest/edge
chromium (edge) 90.0.4421.5 par Canonical✓ mis à jour
Problem persists : I can't activate synchronization.
When I click on the "user" button (top right of the window, next to the
vertical-dots menu) I see:
- a button to activate synchronization, when I'm on version 88.0.4324.182
- no such button on version 89 (stable) et 90 (edge)
about://sync-internals shows "Disable Reasons" is "Not signed in".
Here's the full report :
Thu Mar 04 2021 14:30:21 GMT+0100 (heure normale d’Europe centrale)
==
Status
==
{
"actionable_error": [
{
"stat_name": "Error Type",
"stat_status": "uninitialized",
"stat_value": "Uninitialized"
},
{
"stat_name": "Action",
"stat_status": "uninitialized",
"stat_value": "Uninitialized"
},
{
"stat_name": "Error Description",
"stat_status": "uninitialized",
"stat_value": "Uninitialized"
}
],
"actionable_error_detected": false,
"details": [
{
"data": [
{
"stat_name": "Transport State",
"stat_status": "",
"stat_value": "Disabled"
},
{
"stat_name": "Disable Reasons",
"stat_status": "",
"stat_value": "Not signed in"
},
{
"stat_name": "Sync Feature Enabled",
"stat_status": "",
"stat_value": false
},
{
"stat_name": "Setup In Progress",
"stat_status": "",
"stat_value": false
},
{
"stat_name": "Auth Error",
"stat_status": "",
"stat_value": "OK since browser startup"
}
],
"is_sensitive": false,
"title": "Summary"
},
{
"data": [
{
"stat_name": "Client Version",
"stat_status": "",
"stat_value": "Chromium Linux 90.0.4421.5
(6bb0ebcc9bbf6a347e4ed8f3dbc1811ba39efbb2-refs/branch-heads/4421@{#11}) unknown"
},
{
"stat_name": "Server URL",
"stat_status": "",
"stat_value": "https://clients4.google.com/chrome-sync/dev;
}
],
"is_sensitive": false,
"title": "Version Info"
},
{
"data": [
{
"stat_name": "Requested Token",
"stat_status": "",
"stat_value": "n/a"
},
{
"stat_name": "Received Token Response",
"stat_status": "",
"stat_value": "n/a"
},
{
"stat_name": "Last Token Request Result",
"stat_status": "",
"stat_value": "OK"
},
{
"stat_name": "Has Token",
"stat_status": "",
"stat_value": false
},
{
"stat_name": "Next Token Request",
"stat_status": "",
"stat_value": "not scheduled"
}
],
"is_sensitive": false,
"title": "Credentials"
},
{
"data": [
{
"stat_name": "Server Connection",
"stat_status": "",
"stat_value": "not attempted"
},
{
"stat_name": "Last Synced",
"stat_status": "",
"stat_value": "Never"
},
{
"stat_name": "Sync First-Time Setup Complete",
"stat_status": "",
"stat_value": true
},
{
"stat_name": "Sync Cycle Ongoing",
"stat_status": "uninitialized",
"stat_value": false
},
{
"stat_name": "Local Sync Backend Enabled",
"stat_status": "",
"stat_value": false
},
{
"stat_name": "Local Backend Path",
"stat_status": "uninitialized",
"stat_value": "Uninitialized"
}
],
"is_sensitive": false,
"title": "Local State"
},
{
"data": [
{
"stat_name": "Throttled or Backoff",
"stat_status": "uninitialized",
"stat_value": false
},
{
"stat_name": "Retry Time",
"stat_status": "uninitialized",
"stat_value": "Uninitialized"
},
{
"stat_name": "Notifications Enabled",
"stat_status": "uninitialized",
"stat_value": false
}
],
"is_sensitive": false,
"title": "Network"
},
{
"data": [
{
"stat_name": "Explicit Passphrase",
"stat_status": "uninitialized",
"stat_value": false
},
{
"stat_name": "Passphrase Required",
"stat_status": "uninitialized",
"stat_value": false
},
{
"stat_name": "Cryptographer Ready To Encrypt",
"stat_status": "uninitialized",
"stat_value": false
},
{
"stat_name": "Cryptographer Has Pending Keys",
"stat_status": "uninitialized",
[Desktop-packages] [Bug 1917763] Re: FFE: new upstream release 21.0 and migrate to llvm 12
** Changed in: mesa (Ubuntu) Status: New => In Progress ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1917763 Title: FFE: new upstream release 21.0 and migrate to llvm 12 Status in mesa package in Ubuntu: In Progress Bug description: Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's been in Debian experimental since rc1. The packaging also migrates it to use llvm 12. The risks involve graphical issues or even crashes when running more intense OpenGL/Vulkan apps like games. Running a desktop is a simple use-case and should work fine across the board. Upstream gitlab has a fairly extensive CI for various drivers, while Intel tests on their own CI. This means that any showstoppers should be shaken out already. We will be able to pull maybe two point-releases before hirsute is frozen, and then push more as an SRU. I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too with some games, all good. packages for hirsute are available on ppa:canonical-x/x-staging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1917763/+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 1917763] [NEW] FFE: new upstream release 21.0 and migrate to llvm 12
Public bug reported: Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's been in Debian experimental since rc1. The packaging also migrates it to use llvm 12. The risks involve graphical issues or even crashes when running more intense OpenGL/Vulkan apps like games. Running a desktop is a simple use-case and should work fine across the board. Upstream gitlab has a fairly extensive CI for various drivers, while Intel tests on their own CI. This means that any showstoppers should be shaken out already. We will be able to pull maybe two point-releases before hirsute is frozen, and then push more as an SRU. I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too with some games, all good. packages for hirsute are available on ppa:canonical-x/x-staging ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1917763 Title: FFE: new upstream release 21.0 and migrate to llvm 12 Status in mesa package in Ubuntu: New Bug description: Mesa 21.0.0 will be released soon, and we still want it in 21.04. It's been in Debian experimental since rc1. The packaging also migrates it to use llvm 12. The risks involve graphical issues or even crashes when running more intense OpenGL/Vulkan apps like games. Running a desktop is a simple use-case and should work fine across the board. Upstream gitlab has a fairly extensive CI for various drivers, while Intel tests on their own CI. This means that any showstoppers should be shaken out already. We will be able to pull maybe two point-releases before hirsute is frozen, and then push more as an SRU. I've tested 21.0.0-rc's on Intel and AMD (RX 5700) and the latter too with some games, all good. packages for hirsute are available on ppa:canonical-x/x-staging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1917763/+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 1917764] [NEW] profile gets deleted on startup due to account "no longer allowed as the primary account"
Public bug reported: I had chromium installed via snap : installed: 89.0.4389.72(1506) 145MB - This morning I ran chromium and got the following message Your account (...) is no longer allowed as the primary account. Because this account is managed by (...), your bookmarks, history, passwords and other settings will be cleared from this device. and, indeed, it was all gone. Impossible to synchronize to the account. I tried clearing ~/snap/chromium and ~/.config/chromium, but still could not restart synchronization. Then I tried reverting : $ snap revert chromium chromium revenu à 88.0.4324.182 and things went working again : I can login to the account and the bookmarks/history/etc. are synced again. I'm running Ubuntu 20.04.2 LTS ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1917764 Title: profile gets deleted on startup due to account "no longer allowed as the primary account" Status in chromium-browser package in Ubuntu: New Bug description: I had chromium installed via snap : installed: 89.0.4389.72(1506) 145MB - This morning I ran chromium and got the following message Your account (...) is no longer allowed as the primary account. Because this account is managed by (...), your bookmarks, history, passwords and other settings will be cleared from this device. and, indeed, it was all gone. Impossible to synchronize to the account. I tried clearing ~/snap/chromium and ~/.config/chromium, but still could not restart synchronization. Then I tried reverting : $ snap revert chromium chromium revenu à 88.0.4324.182 and things went working again : I can login to the account and the bookmarks/history/etc. are synced again. I'm running Ubuntu 20.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917764/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
I have fixed the bionic build in 460.39-0ubuntu0.18.04.2. I had accidentally dropped a change that is only required for bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
For bionic, it seems that the new nvidia-settings FTBFS on amd64. Can someone take a look at that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1917756] Re: FTBFS on ppc64el
And I uploaded https://launchpad.net/ubuntu/+source/libraw/0.20.2-1ubuntu1 to hirsute with the fix I submitted to salsa. ** Changed in: libraw (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libraw in Ubuntu. https://bugs.launchpad.net/bugs/1917756 Title: FTBFS on ppc64el Status in libraw package in Ubuntu: Fix Committed Bug description: This is caused by missing symbols, due to the default optimization level on ppc64el (-O3): dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libraw20/DEBIAN/symbols doesn't match completely debian/libraw20.symbols --- debian/libraw20.symbols (libraw20_0.20.2-1_ppc64el) +++ dpkg-gensymbolsOw1CUA 2021-02-22 09:43:14.637485948 + @@ -577,7 +577,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 @@ -1175,7 +1175,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 dh_makeshlibs: error: failing due to earlier errors I submitted https://salsa.debian.org/debian-phototools- team/libraw/-/merge_requests/5 to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libraw/+bug/1917756/+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 1917756] [NEW] FTBFS on ppc64el
Public bug reported: This is caused by missing symbols, due to the default optimization level on ppc64el (-O3): dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libraw20/DEBIAN/symbols doesn't match completely debian/libraw20.symbols --- debian/libraw20.symbols (libraw20_0.20.2-1_ppc64el) +++ dpkg-gensymbolsOw1CUA 2021-02-22 09:43:14.637485948 + @@ -577,7 +577,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 @@ -1175,7 +1175,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 dh_makeshlibs: error: failing due to earlier errors I submitted https://salsa.debian.org/debian-phototools- team/libraw/-/merge_requests/5 to fix this. ** Affects: libraw (Ubuntu) Importance: Undecided Assignee: Olivier Tilloy (osomon) Status: Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libraw in Ubuntu. https://bugs.launchpad.net/bugs/1917756 Title: FTBFS on ppc64el Status in libraw package in Ubuntu: Fix Committed Bug description: This is caused by missing symbols, due to the default optimization level on ppc64el (-O3): dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libraw20/DEBIAN/symbols doesn't match completely debian/libraw20.symbols --- debian/libraw20.symbols (libraw20_0.20.2-1_ppc64el) +++ dpkg-gensymbolsOw1CUA 2021-02-22 09:43:14.637485948 + @@ -577,7 +577,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 @@ -1175,7 +1175,7 @@ libraw_version@Base 0.16.0 libraw_versionNumber@Base 0.16.0 (c++)"pana_cs6_page_decoder::read_page()@Base" 0.20.0 - (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 +#MISSING: 0.20.2-1# (c++|arch-bits=64)"std::_Vector_base >::~_Vector_base()@Base" 0.20.0 (c++)"std::ctype::do_widen(char) const@Base" 0.16.0 (c++)"typeinfo for LibRaw@Base" 0.16.0 (c++)"typeinfo for LibRaw_abstract_datastream@Base" 0.16.0 dh_makeshlibs: error: failing due to earlier errors I submitted https://salsa.debian.org/debian-phototools- team/libraw/-/merge_requests/5 to fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libraw/+bug/1917756/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
This bug was fixed in the package nvidia-settings - 460.39-0ubuntu0.20.04.1 --- nvidia-settings (460.39-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release. * debian/patches/link-order.diff, debian/patches/12_nostrip.patch, debian/patches/05_add_polkit_support.patch, debian/patches/06_remove_local_prefix.patch, debian/patches/07_remove_features_for_legacy.patch debian/patches/08_add_prime_support.patch debian/patches/10_legacy_vdpau.patch debian/patches/11_link_as-needed.patch debian/patches/13_libxnvctrl_so_0.patch debian/patches/15_clean.patch: - Refresh patches. * debian/patches/series: - Drop 16_gzip-n.patch. * debian/patches/08_add_prime_support.patch: - Refresh and add support for a progress dialog (LP: #1915003). -- Alberto Milone Wed, 03 Feb 2021 22:11:10 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
This bug was fixed in the package nvidia-prime - 0.8.16~0.20.04.1 --- nvidia-prime (0.8.16~0.20.04.1) focal; urgency=medium * prime-select: - Make sure to update the initramfs, so that the driver options can be applied correctly. This time around we can also provide visual feedback (in the form of a progress spinner) while update-initramfs is running (LP: #1915003). -- Alberto Milone Wed, 10 Feb 2021 12:38:51 +0100 ** Changed in: nvidia-prime (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: nvidia-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
20.2.x is dead, next upstream version is 21.0.0 which we'll get in hirsute once released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
This bug was fixed in the package nvidia-prime - 0.8.16~0.20.10.1 --- nvidia-prime (0.8.16~0.20.10.1) groovy; urgency=medium * prime-select: - Make sure to update the initramfs, so that the driver options can be applied correctly. This time around we can also provide visual feedback (in the form of a progress spinner) while update-initramfs is running (LP: #1915003). -- Alberto Milone Wed, 10 Feb 2021 12:36:51 +0100 ** Changed in: nvidia-prime (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915003] Update Released
The verification of the Stable Release Update for nvidia-settings has completed successfully and the package is now being 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 nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915003] Re: SRU: Always update the initramfs when changing power profile
This bug was fixed in the package nvidia-settings - 460.39-0ubuntu0.20.10.1 --- nvidia-settings (460.39-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release. * debian/patches/link-order.diff, debian/patches/12_nostrip.patch, debian/patches/05_add_polkit_support.patch, debian/patches/06_remove_local_prefix.patch, debian/patches/07_remove_features_for_legacy.patch debian/patches/08_add_prime_support.patch debian/patches/10_legacy_vdpau.patch debian/patches/11_link_as-needed.patch debian/patches/13_libxnvctrl_so_0.patch debian/patches/15_clean.patch: - Refresh patches. * debian/patches/series: - Drop 16_gzip-n.patch. * debian/patches/08_add_prime_support.patch: - Refresh and add support for a progress dialog (LP: #1915003). -- Alberto Milone Wed, 03 Feb 2021 18:09:00 +0100 ** Changed in: nvidia-settings (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-prime source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_
** Description changed: + [Impact] + + gnome-shell crashes when auto-move-windows extension is enabled. + https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 - --- + [Test Plan] + + 1. Install gnome-shell-extensions + + 2. Open the 'Extensions' app and enable auto-move-windows. + + 3. Configure auto-move-windows with a rule for Chrome/Chromium. + + 4. Open Chrome/Chromium and point it at a simple video like from + https://download.blender.org/peach/bigbuckbunny_movies/ or + https://download.blender.org/demo/movies/BBB/ + + 5. Set the Chrome tab playing the video to PiP mode. + + Expect: No crashes and the video moves to an external window. + + [Where problems could occur] + + Changing mutter's window management code always brings risk of + regression to the GNOME desktop. + + [Other Info] As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: ** Description changed: [Impact] - gnome-shell crashes when auto-move-windows extension is enabled. + gnome-shell crashes when auto-move-windows extension is used. https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 [Test Plan] 1. Install gnome-shell-extensions 2. Open the 'Extensions' app and enable auto-move-windows. 3. Configure auto-move-windows with a rule for Chrome/Chromium. 4. Open Chrome/Chromium and point it at a simple video like from https://download.blender.org/peach/bigbuckbunny_movies/ or https://download.blender.org/demo/movies/BBB/ 5. Set the Chrome tab playing the video to PiP mode. Expect: No crashes and the video moves to an external window. [Where problems could occur] Changing mutter's window management code always brings risk of regression to the GNOME desktop. [Other Info] As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: ** Description changed: [Impact] - gnome-shell crashes when auto-move-windows extension is used. + gnome-shell crashes when auto-move-windows extension is used with + windows that want to be on all workspaces (like Chrome PiP). https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 [Test Plan] 1. Install gnome-shell-extensions 2. Open the
[Desktop-packages] [Bug 1917705] Re: "profile will be deleted" at startup after chromium 89 update
This is an unfortunate consequence of a decision by Google to restrict access to the sync API to Chrome only (which explains why in comment #3 you're seeing that chrome 89 on linux works fine). There's a lengthy discussion with details here: https://groups.google.com/a/chromium.org/g/chromium- packagers/c/SG6jnsP4pWM/m/Y73W4CecCQAJ. I am quoting the part that's relevant for end users: « What does this mean for my users? Users of products that are incorrectly using these APIs will notice that they won't be able to log into their Google Accounts in those products anymore. For users who accessed Google features (like Chrome Sync) through a 3rd- party Chromium-based browser, their data will continue to be available in their Google Account, and data that they have stored locally will continue to be available locally. As always, users can view and manage their data through Google Chrome, Chrome OS, and/or on the My Google Activity page, and they can also download their data from the Google Takeout page, and/or delete it from this page. » I'm afraid (and sorry) there's nothing that can be done from a packaging perspective to mitigate this regression. Reverting the snap in the stable channel wouldn't help, because it's not a version problem. The official announcement states that starting March 15 attempts to log in will fail anyway. I suppose that users that can't do without the profile sync feature will need to move on to using the official chrome package distributed by Google, instead of chromium (which is probably what Google wants, really). ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Won't Fix -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
** Summary changed: - profile will be deleted + "profile will be deleted" at startup after chromium 89 update -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Confirmed Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
*** This bug is a duplicate of bug 1917705 *** https://bugs.launchpad.net/bugs/1917705 ** This bug has been marked a duplicate of bug 1917705 profile will be 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: Confirmed Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
*** This bug is a duplicate of bug 1917705 *** https://bugs.launchpad.net/bugs/1917705 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: Confirmed Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917739] Re: rcv
Please attach a video or photo of the problem. Also: 1. Reboot and reproduce the problem again. 2. Reboot again into recovery mode this time, and then run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917739 Title: rcv Status in Ubuntu: Incomplete Bug description: ubuntu boot only in recovery mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 12:51:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2021-02-25 (6 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ad32rb@/vmlinuz-5.8.0-44-generic root=ZFS=rpool/ROOT/ubuntu_ad32rb ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1917739/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
I'm guessing this is bug 1897965. Please try the workaround from that. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic
[Desktop-packages] [Bug 1917739] [NEW] rcv
Public bug reported: ubuntu boot only in recovery mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 12:51:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2021-02-25 (6 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ad32rb@/vmlinuz-5.8.0-44-generic root=ZFS=rpool/ROOT/ubuntu_ad32rb ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1917739 Title: rcv Status in xorg package in Ubuntu: New Bug description: ubuntu boot only in recovery mode ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 12:51:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2021-02-25 (6 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ad32rb@/vmlinuz-5.8.0-44-generic root=ZFS=rpool/ROOT/ubuntu_ad32rb ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2017 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name:
[Desktop-packages] [Bug 1917713] Re: [snap] Logged out of Chromium after latest update to 89
I think I am also hitting this same bug. I'm running Chromium 1506 from Snap on Ubuntu 20.04. I have two Chromium profiles. One of them is managed by my employer. When I try to start that one, I get the error message: "Your account is no longer allowed as the primary account. Because this account is managed by , your bookmarks, history, passwords and other settings will be cleared from this device." This profile seems to now be unusable - when I ack the error message, Chromium immediately quits. The other is my personal account. I can use this account, but although I am logged in to my Google account, Chromium itself is no longer logged in - I have a blank icon in the top right where my user avatar should be. When I open the dropdown, it says "Not logged in". -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions:
[Desktop-packages] [Bug 1917705] Re: profile will be deleted
May I suggest dropping 89 on the stable channel for snappy? -- 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/1917705 Title: profile will be deleted Status in chromium-browser package in Ubuntu: Confirmed Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap ** Description changed: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. + + The current profile is named "Person 1". + + Ubuntu 20.04.2 LTS, fully updated + Chromium 89.0.4389.72 2021-03-03 (1506) 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
Sorry, reversing my last incomplete (the package would not have been installed if you use `snap install`). Please provide OS & release details manually via comment, or edit. -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917705] Re: profile will be deleted
Possibly related : https://bugs.launchpad.net/bugs/1917713 -- 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/1917705 Title: profile will be deleted Status in chromium-browser package in Ubuntu: Confirmed Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
Currently we have no release details, no package details; detail that is provided by apport-collect. Your last comment (thank you) implies the program isn't even installed on your system so something is up, or this bug is misfiled. -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
I run the command and it said: "Package chromium-browser not installed and no hook available, ignoring" I reviewed the linked bug and, though it is similar, the difference is that I still seem to have everything, whereas in the bug it is suggested data is lost. So could it be the same bug but with different symptoms? -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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
