[Desktop-packages] [Bug 1913570] [NEW] Firefox not opening file chooser dialog for importing certificates
Public bug reported: When installed as a snap, firefox won't open the file chooser dialog for importing a certificate authority. However, it is working when installed using apt. How to reproduce: 1. Install firefox as snap 2. Navigate to Preferences | Privacy & Security | Certificates | View Certificates 3. Select Authorities 4. Click Import ... -> A file selector dialog should open to import a certificate, but nothing happens. Environment: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jan 28 11:43:55 2021 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-15 (12 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) ProcCpuinfoMinimal: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz stepping : 7 microcode : 0x2f cpu MHz: 3701.000 cache size : 8192 KB physical id: 6 siblings : 1 core id: 0 cpu cores : 1 apicid : 6 initial apicid : 6 fpu: yes fpu_exception : yes cpuid level: 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 7402.00 clflush size : 64 cache_alignment: 64 address sizes : 43 bits physical, 48 bits virtual power management: ProcEnviron: SHELL=/bin/bash LANGUAGE=en_US LC_ADDRESS=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LANG=en_US.UTF-8 TERM=xterm-256color LC_IDENTIFICATION=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 XDG_RUNTIME_DIR= LC_TIME=de_DE.UTF-8 PATH=(custom, no user) LC_NUMERIC=de_DE.UTF-8 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Snap: firefox 84.0.2-1 (stable) Tags: hirsute Uname: Linux 5.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Tags added: snap -- 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/1913570 Title: Firefox not opening file chooser dialog for importing certificates Status in firefox package in Ubuntu: New Bug description: When installed as a snap, firefox won't open the file chooser dialog for importing a certificate authority. However, it is working when installed using apt. How to reproduce: 1. Install firefox as snap 2. Navigate to Preferences | Privacy & Security | Certificates | View Certificates 3. Select Authorities 4. Click Import ... -> A file selector dialog should open to import a certificate, but nothing happens. Environment: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jan 28 11:43:55 2021 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-15 (12 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) ProcCpuinfoMinimal: processor: 3 vendor_id: GenuineIntel cpu family : 6 model: 42 model name : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz stepping : 7 microcode: 0x2f cpu MHz : 3701.000 cache size : 8192 KB physical id : 6 siblings : 1 core id : 0 cpu cores: 1 apicid : 6 initial apicid : 6 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology tsc_reliable nonstop_tsc cpuid pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm pti ssbd ibrs ibpb stibp tsc_adjust arat md_clear flush_l1d arch_capabilities bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 7402.00 clflush size : 64 cache_alignment : 64 address sizes: 43 bits physical, 48 bits virtual power management: ProcEnviron: SHELL=/bin/bash LANGUAGE=en_US LC_ADDRESS=de_DE.UTF-8
[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_
Thanks! I appreciate this quick turnaround time :) -- 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/1911921 Title: 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_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+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 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
I'm running latest HWE kernel on 20.04 (5.4.0-65). If I connect a microphone via USB or the headphone socket then it works (in chromium too). But if I disconnect the microphone then Gnome doesn't detect any built- in microphone. As I've made some changes to my modules settings, I think I'll wipe the system and try it with a fresh install. -- 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/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+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 1913480] Re: Sound>Output>Configuration always resets
The settings panel is only a configuration interface, it has no backend or service always active and isn't the one applying the configuration when the devices are connected, the issue is probably rather on the sound service pulseaudio ** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1913480 Title: Sound>Output>Configuration always resets Status in pulseaudio package in Ubuntu: New Bug description: In "Settings>Sound>Output" If set my "Output Device" to "HDMI / DisplayPort 5" and set "Configuration" to "Digital Surround 5.1" If I close the receiver and open it again... The configuration will reset to "Digital stereo" The expected behavior would be to keep the "Digital Surround 5.1"; not resetting it every time. Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1913480/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell EliteBook - Headset: Oppo Enco Quiet -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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_
Upstream has said they will fix gnome-shell itself to warn instead of crash. -- 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/1911921 Title: 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_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+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_
First fix proposed: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/157 -- 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/1911921 Title: 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_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+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 1729433]
I think this bug describes the behaviour on https://askubuntu.com/questions/1274365/windows-of-an-application-have- minimum-size-and-i-cant-find-the-window-anymore We have noticed that with several of our students on Ubuntu 20.04 with LO 7.0.4.2 -- 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/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
As lame as such comments may appear: The level of suffering on my side is large enough to add that I too am really irritated by this “feature”. It is a significant obstacle in my daily workflow, and any workaround must not be necessary in the first place. We’ve been living with browsers with (user!) access to the whole filesystem for decades without worrying. Besides, the software still comes from a trusted source. -- 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/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+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_
** Changed in: gnome-shell-extensions (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extensions (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell-extensions (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium -- 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/1911921 Title: 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_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+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: When using auto-move-windows extension, gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (wor
** Also affects: gnome-shell-extensions Importance: Undecided Status: New ** No longer affects: gnome-shell-extensions ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 + https://gitlab.gnome.org/GNOME/mutter/-/issues/992 + + --- + 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 + () 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: ** Summary changed: - When using auto-move-windows extension, gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) + 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_list, window) == NULL) -- 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/1911921 Title: 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_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+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
