[Desktop-packages] [Bug 1899206] [NEW] Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which
seems to have been introduced within the past couple of weeks. I have a
couple custom keyboard settings configured in Tweaktool "Additional
Layout Options". These settings work great.

I have a USB keyboard plugged into the machine. If I have the keyboard
plugged in when I start my Gnome session, the customized keyboard layout
options are correctly applied to the USB keyboard. If I unplug and
reconnect the keyboard, the keyboard does will _NOT_ have the customized
keyboard settings.

If I restart my Gnome session (using Alt-F2 -> "r"), the customized
settings are applied to the keyboard.

I think this behavior is something new. Before, I was able to
unplug/reconnect my keyboard and it would apply my customized keyboard
settings on reconnect. Is there anything I can do to force the
application of the custom keyboard tweaks on USB keyboard reconnect?

Is anyone else able to reproduce this? I don't have any other machines
with Ubuntu 20.04.1 to test with.

Thanks!

(This is also cross-posted at askubuntu:
https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional-
layout-options-not-working)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard 
unplug/reconnect
https://bugs.launchpad.net/bugs/1899206
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1899275] Re: no icon placement option on desktop

[Daniel van Vugt]

*** This bug is a duplicate of bug 1875695 ***
https://bugs.launchpad.net/bugs/1875695

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1875695, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: gnome-shell (Ubuntu) => gnome-flashback (Ubuntu)

** This bug has been marked a duplicate of bug 1875695
   Unable to place icons on desktop in user-defined order, use vertical column 
instead

-- 
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/1899275

Title:
  no icon placement option on desktop

Status in gnome-flashback package in Ubuntu:
  New

Bug description:
  Im surprised that this has not been reported before:
  Using GNOME-Flashback under Ubuntu 20.04 it seems impossible to place the 
icons on the desktop according to my choice.
  Also I can find no way of replacing an icon image (the "picture") with 
something of my own choosing.
  This was definitely possible in previous versions. The present situation is 
most inconvenient.

  I dont know whether this is a bug or a display of sub-par judgement in
  the part of a maintainer

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sat Oct 10 19:38:49 2020
  DisplayManager: lightdm
  InstallationDate: Installed on 2019-09-11 (395 days ago)
  InstallationMedia: Backup2019 18.04 - Release amd64
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  ShellJournal:
   -- Logs begin at Thu 2020-10-01 17:42:38 IDT, end at Sat 2020-10-10 19:39:01 
IDT. --
   -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-07 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1899275/+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 1899397] Re: [Lenovo IdeaPad 3 14IIL05] No fan detected

[Daniel van Vugt]

Please explain in more detail: No fan detected by what?

What were you expecting and what are you looking at?

** Summary changed:

- Fan not work
+ [Lenovo IdeaPad 3 14IIL05] No fan detected

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Changed in: linux (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/1899397

Title:
  [Lenovo IdeaPad 3 14IIL05] No fan detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No fan detected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 11 23:33:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3fb5]
  InstallationDate: Installed on 2020-09-24 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81WD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=98af080a-ee1a-4302-b335-e6462548d523 ro i842.nopnp=1 pci=nocrs quiet 
splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EMCN13WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05:
  dmi.product.family: IdeaPad 3 14IIL05
  dmi.product.name: 81WD
  dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05
  dmi.product.version: IdeaPad 3 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/linux/+bug/1899397/+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 1899252] Re: quick alt-tab doenst work

[Daniel van Vugt]

I can't seem to reproduce the issue on Ubuntu 20.04. Can you please try
removing this extension:

  Current_screen_only_for_Alternate_Tab

and tell us if that makes a difference?

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1899252

Title:
  quick alt-tab doenst work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm getting the same behavior as the link below, in Ubuntu 18.04 you
  could do a quick alt+tab to change to the first window of an
  application, but now that I updated it to the latest version (20.04) I
  have the all windows of an app are displayed with Alt+tab.

  https://bugzilla.gnome.org/show_bug.cgi?id=697480

  This was supposedly fixed by Didier Roche, check out the following
  link https://bugzilla.gnome.org/show_bug.cgi?id=786009.

  The behavior is best described in the videos made by Didier:

  Gnome-session vanilla

  https://youtu.be/D32VEP0sFk4

  Ubuntu-session

  https://youtu.be/k-IBk-Fibj4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 13:00:04 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-26 (563 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-02 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899252/+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 1899230] Re: gnome-shell crashed with SIGSEGV in _cairo_ft_scaled_glyph_init()

[Daniel van Vugt]

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV in _cairo_ft_scaled_glyph_init()
+ gnome-shell crashed with SIGSEGV in _cairo_ft_scaled_glyph_init() from 
_cairo_scaled_glyph_lookup() from composite_glyphs()

** Tags added: nvidia

-- 
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/1899230

Title:
  gnome-shell crashed with SIGSEGV in _cairo_ft_scaled_glyph_init() from
  _cairo_scaled_glyph_lookup() from composite_glyphs()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Missed how this happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 18:20:22 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
   () at /lib/x86_64-linux-gnu/libcairo.so.2
   () at /lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell crashed with SIGSEGV in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899230/+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 1899235] Re: Touchpad freeze after overnight sleep

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Touchpad freeze after overnight sleep
+ [Dell Inspiron 3180] Touchpad freeze after overnight sleep

-- 
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/1899235

Title:
  [Dell Inspiron 3180] Touchpad freeze after overnight sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The real issue is touchpad freeze after wakeup from overnight sleep.
  Mouse though does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Oct 10 08:14:07 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: I don't know
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2020-09-03 (36 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3180
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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/linux/+bug/1899235/+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 1899184] Re: CPU spikes and system hangs from gnome-shell every 5-10 seconds

[Daniel van Vugt]

We will need more information about the affected machine. When the
problem is happening please run:

  journalctl -b0 > journal.txt
  lspci -kv > lspci.txt
  xrandr --verbose > xrandr.txt

and then attach the resulting text files here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1899184

Title:
  CPU spikes and system hangs from gnome-shell every 5-10 seconds

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On a fresh installation of Ubuntu 20.04 with no configuration files
  changed yet (the "install third-party software" option enabled),
  installed from the official daily ISO, the system freezes for about a
  second every 5-10 seconds and I see a spike to 70% or more CPU usage
  by gnome-shell. I cannot see anything that shows up in `sudo
  journalctl -ef` or `sudo dmesg -w` when the freezes occur. The problem
  reproduces on both X11 and Wayland, although under Wayland it's more
  annoying since a freeze leads to repeated keypresses of whatever key
  was being held down on the keyboard at the time of the freeze.

  This problem seems to have been reported at
  

  but with no plausible resolution or workaround in sight.

  I tried to follow  to figure out what
  was going on with gnome-shell, but I don't think the results seem very
  helpful.

  Result of `sudo perf top`:

  4.39%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  4.26%  libc-2.31.so [.] __vfprintf_internal

  And `sudo perf top --sort comm,dso`:

  45.28%  gnome-shell  libglib-2.0.so.0.6400.3
  17.23%  gnome-shell  libc-2.31.so

  And `sudo perf record -g -p PID` for the `gnome-shell` PID:

  +   39.81% 0.01%  [unknown][.] 

  +   14.26% 2.04%  libc-2.31.so [.] 
__vasprintf_internal
  +8.61% 8.42%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  +8.51% 8.09%  libc-2.31.so [.] 
__vfprintf_internal

  And `strace -c -p PID`:

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   34.410.128602   5 22784 19837 recvmsg
   25.740.096215   7 13716   632 ioctl
   18.040.067420  10  6686   poll
    9.500.035523   7  4858   write
    4.560.017025   7  2322   writev

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 07:54:43 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  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/ubuntu/+source/gnome-shell/+bug/1899184/+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 1899184] Re: CPU spikes and system hangs from gnome-shell every 5-10 seconds

[Daniel van Vugt]

Please also tell us what extensions you have enabled, if any.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1899184

Title:
  CPU spikes and system hangs from gnome-shell every 5-10 seconds

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On a fresh installation of Ubuntu 20.04 with no configuration files
  changed yet (the "install third-party software" option enabled),
  installed from the official daily ISO, the system freezes for about a
  second every 5-10 seconds and I see a spike to 70% or more CPU usage
  by gnome-shell. I cannot see anything that shows up in `sudo
  journalctl -ef` or `sudo dmesg -w` when the freezes occur. The problem
  reproduces on both X11 and Wayland, although under Wayland it's more
  annoying since a freeze leads to repeated keypresses of whatever key
  was being held down on the keyboard at the time of the freeze.

  This problem seems to have been reported at
  

  but with no plausible resolution or workaround in sight.

  I tried to follow  to figure out what
  was going on with gnome-shell, but I don't think the results seem very
  helpful.

  Result of `sudo perf top`:

  4.39%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  4.26%  libc-2.31.so [.] __vfprintf_internal

  And `sudo perf top --sort comm,dso`:

  45.28%  gnome-shell  libglib-2.0.so.0.6400.3
  17.23%  gnome-shell  libc-2.31.so

  And `sudo perf record -g -p PID` for the `gnome-shell` PID:

  +   39.81% 0.01%  [unknown][.] 

  +   14.26% 2.04%  libc-2.31.so [.] 
__vasprintf_internal
  +8.61% 8.42%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  +8.51% 8.09%  libc-2.31.so [.] 
__vfprintf_internal

  And `strace -c -p PID`:

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   34.410.128602   5 22784 19837 recvmsg
   25.740.096215   7 13716   632 ioctl
   18.040.067420  10  6686   poll
    9.500.035523   7  4858   write
    4.560.017025   7  2322   writev

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 07:54:43 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  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/ubuntu/+source/gnome-shell/+bug/1899184/+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 1899184] Re: CPU spikes and system hangs from gnome-shell every 5-10 seconds

[Daniel van Vugt]

It looks like the freezes could be a separate problem to the CPU spikes.
Because these look like input freezes:

[ 6939.689860] shallan gnome-shell[15054]: _clutter_stage_queue_event: 
assertion 'CLUTTER_IS_STAGE (stage)' failed
[ 6939.689984] shallan gnome-shell[15054]: clutter_do_event: Event does not 
have a stage: discarding.
[ 6939.699761] shallan gnome-shell[15054]: _clutter_stage_queue_event: 
assertion 'CLUTTER_IS_STAGE (stage)' failed
[ 6939.699930] shallan gnome-shell[15054]: clutter_do_event: Event does not 
have a stage: discarding.
[ 6939.729329] shallan gnome-shell[15054]: _clutter_stage_queue_event: 
assertion 'CLUTTER_IS_STAGE (stage)' failed
[ 6939.729490] shallan gnome-shell[15054]: clutter_do_event: Event does not 
have a stage: discarding.

but I don't know how that could cause high CPU.

-- 
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/1899184

Title:
  CPU spikes and system hangs from gnome-shell every 5-10 seconds

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On a fresh installation of Ubuntu 20.04 with no configuration files
  changed yet (the "install third-party software" option enabled),
  installed from the official daily ISO, the system freezes for about a
  second every 5-10 seconds and I see a spike to 70% or more CPU usage
  by gnome-shell. I cannot see anything that shows up in `sudo
  journalctl -ef` or `sudo dmesg -w` when the freezes occur. The problem
  reproduces on both X11 and Wayland, although under Wayland it's more
  annoying since a freeze leads to repeated keypresses of whatever key
  was being held down on the keyboard at the time of the freeze.

  This problem seems to have been reported at
  

  but with no plausible resolution or workaround in sight.

  I tried to follow  to figure out what
  was going on with gnome-shell, but I don't think the results seem very
  helpful.

  Result of `sudo perf top`:

  4.39%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  4.26%  libc-2.31.so [.] __vfprintf_internal

  And `sudo perf top --sort comm,dso`:

  45.28%  gnome-shell  libglib-2.0.so.0.6400.3
  17.23%  gnome-shell  libc-2.31.so

  And `sudo perf record -g -p PID` for the `gnome-shell` PID:

  +   39.81% 0.01%  [unknown][.] 

  +   14.26% 2.04%  libc-2.31.so [.] 
__vasprintf_internal
  +8.61% 8.42%  libglib-2.0.so.0.6400.3  [.] 
g_variant_serialised_n_children
  +8.51% 8.09%  libc-2.31.so [.] 
__vfprintf_internal

  And `strace -c -p PID`:

  % time seconds  usecs/call callserrors syscall
  -- --- --- - - 
   34.410.128602   5 22784 19837 recvmsg
   25.740.096215   7 13716   632 ioctl
   18.040.067420  10  6686   poll
    9.500.035523   7  4858   write
    4.560.017025   7  2322   writev

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 07:54:43 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  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/ubuntu/+source/gnome-shell/+bug/1899184/+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 1899152] Re: Resolution not set or inappropriate

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Summary changed:

- Resolution not set or inappropriate
+ [intel G33] Resolution not set or inappropriate

** Summary changed:

- [intel G33] Resolution not set or inappropriate
+ [intel G33] Resolution limited to 1024x768

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1899152

Title:
  [intel G33] Resolution limited to 1024x768

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  Defaultly it is set to 1024x768. But my screen resolution is 1440x400.

  I tried using terminal to add newmode and saved with the desired
  resolution. When I aplied the new one, the system gets hanged
  everytime.

  Previuosly I used 14.04 version. Then there was no issue. I added
  newmode using terminal. And next it was fine.

  But now it is not allowing me to set.

  Please make this issue clear.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 16:03:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:29c2]
  InstallationDate: Installed on 2020-10-02 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: OEM OEM
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=948d3ae0-06d2-4522-8970-f6183d8b94fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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/xserver-xorg-video-intel/+bug/1899152/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Ben O'Steen]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Noticed that I couldn't use my headset mic on any apps in the past month, but 
the above reports are describing the same behavioural issues as I am seeing soI 
think I am hitting the same problem.
 
Using Sennheisser HD 4.40BT headphones on a System76 Gazelle. Connects default 
audio through headphones with the A2DP profile as expected when connecting 
through BT, but the Internal Microphone stays selected for input. Trying to 
select the HD4.4 microphone setting does nothing, and no signal of any kind 
comes through the input.

Switching to the HFP/HSP profile also leads to a break in audio, and
after the A2DP setting is shown as unavailable until I wipe the userland
pulse configs. It cuts off the audio through the headset and ends up in
a bad configuration where I have to turn BT off and on again to
reconnect and when it does, the configuration is stuck on HFP/HSP and in
mono.

No audio through the headset mic can be picked up through any
pulseaudio-enabled monitors, all showing zero input with whatever
configuration or set-up I can muster.

Running Linux pop-os 5.4.0-7642-generic #46~1598628707~20.04~040157c-
Ubuntu SMP Fri Aug 28 18:02:16 UTC  x86_64

-- 
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/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1898943] Re: dock and top bar blinking at fullscreen

[Daniel van Vugt]

Please also try running this again:

  apport-collect 1898943

-- 
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/1898943

Title:
  dock and top bar blinking at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The dock is flashing (opening and closing) when I have smart hide mode
  enabled (Dash to Dock extension). The same phenomenon occurs when I
  use the "Hide Top Bar" extension with hidden mode ...

  The blinks occur with a certain pattern, which I believe is based on
  the values of the extensions (pressure setting etc.) ... Anyway, it is
  a problem that affects two different extensions at the same time.
  Usually the problem starts when I use Firefox's fullscreen. Sometimes
  the dock and the top bar work perfectly, but after a while they start
  to blink. You can click on the icons, but you need to reach the
  correct timing. If it blinks too fast, it becomes very difficult to
  use the dock in full screen.

  The problem happens only in some windows (which were used in
  fullscreen mode) and do not reach other windows. It is resolved with
  the closing and reopening of the program, but soon they reappear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898943/+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 1898943] Re: dock and top bar blinking at fullscreen

[Daniel van Vugt]

For code that wasn't installed from Ubuntu we can't track their bugs
here...

If you can reproduce the blinking with only Ubuntu packages then please
tell us which packages.

If you can't reproduce the blinking with only Ubuntu packages then we
will need to close this bug.

** Package changed: gnome-shell-extension-dashtodock (Ubuntu) => gnome-
shell (Ubuntu)

-- 
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/1898943

Title:
  dock and top bar blinking at fullscreen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The dock is flashing (opening and closing) when I have smart hide mode
  enabled (Dash to Dock extension). The same phenomenon occurs when I
  use the "Hide Top Bar" extension with hidden mode ...

  The blinks occur with a certain pattern, which I believe is based on
  the values of the extensions (pressure setting etc.) ... Anyway, it is
  a problem that affects two different extensions at the same time.
  Usually the problem starts when I use Firefox's fullscreen. Sometimes
  the dock and the top bar work perfectly, but after a while they start
  to blink. You can click on the icons, but you need to reach the
  correct timing. If it blinks too fast, it becomes very difficult to
  use the dock in full screen.

  The problem happens only in some windows (which were used in
  fullscreen mode) and do not reach other windows. It is resolved with
  the closing and reopening of the program, but soon they reappear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898943/+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 1895897] Re: Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: Assertion `pScreen->myNum < xf86NumScreens' failed.

[Daniel van Vugt]

Confirmed by:

https://errors.ubuntu.com/bucket/?id=/usr/lib/xorg/Xorg%3AXorg%3A%20../../../../../../hw/xfree86/common/xf86Helper.c%3A1743%3A%20xf86ScreenToScrn%3A%20Assertion%20%60pScreen-%3EmyNum%20%3C%20xf86NumScreens%27%27%20failed.

but that link is not usable because of bug 1863689.

** Changed in: xorg-server (Ubuntu)
   Status: Invalid => New

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

-- 
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/1895897

Title:
  Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743:
  xf86ScreenToScrn: Assertion `pScreen->myNum < xf86NumScreens' failed.

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I got this crash report but I don't know what exactly triggered it.
  I'm willing to provide more info when needed.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: xserver-xorg-core 2:1.20.8-2ubuntu6
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AssertionMessage: Xorg: 
../../../../../../hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 16 23:19:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2020-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20LTS01800
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty 
-novtswitch -verbose 3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=301ac90f-9a29-425d-9b75-b6b2a43bf00a ro 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
   __assert_fail_base (fmt=0x7fa38d729588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55dc8d338b00 "pScreen->myNum < xf86NumScreens", 
file=0x55dc8d338a90 "../../../../../../hw/xfree86/common/xf86Helper.c", 
line=1743, function=) at assert.c:92
   __GI___assert_fail (assertion=0x55dc8d338b00 "pScreen->myNum < 
xf86NumScreens", file=0x55dc8d338a90 
"../../../../../../hw/xfree86/common/xf86Helper.c", line=1743, 
function=0x55dc8d338d20 "xf86ScreenToScrn") at assert.c:101
   xf86ScreenToScrn ()
  Title: Xorg assert failure: Xorg: 
../../../../../../hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/18/2019
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET60W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS01800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.37
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:br1.37:efr1.37:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS01800
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  separator:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.5-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  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 

[Desktop-packages] [Bug 1898943] [NEW] dock and top bar blinking at fullscreen

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The dock is flashing (opening and closing) when I have smart hide mode
enabled (Dash to Dock extension). The same phenomenon occurs when I use
the "Hide Top Bar" extension with hidden mode ...

The blinks occur with a certain pattern, which I believe is based on the
values of the extensions (pressure setting etc.) ... Anyway, it is a
problem that affects two different extensions at the same time. Usually
the problem starts when I use Firefox's fullscreen. Sometimes the dock
and the top bar work perfectly, but after a while they start to blink.
You can click on the icons, but you need to reach the correct timing. If
it blinks too fast, it becomes very difficult to use the dock in full
screen.

The problem happens only in some windows (which were used in fullscreen
mode) and do not reach other windows. It is resolved with the closing
and reopening of the program, but soon they reappear.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-comment focal
-- 
dock and top bar blinking at fullscreen
https://bugs.launchpad.net/bugs/1898943
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
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 1681290] Re: UI experiences delay when menu / tooltip disappears

[Daniel van Vugt]

*** This bug is a duplicate of bug 1181666 ***
https://bugs.launchpad.net/bugs/1181666

If you have a different issue then please open a new bug of your own by
running:

  ubuntu-bug gnome-shell

-- 
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/1681290

Title:
  UI experiences delay when menu / tooltip disappears

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system will not respond to mouse clicks or keypresses.
  This appears to happen when I hold the mouse over an item and a pop-up
  tooltip appears, or when I click on a menu.  I believe it happens when
  the tooltip/menu is set to disappear.

  Steps to reproduce are:
   1) Select a menu item
   2) Click outside the menu
   3) The click won't register for around 7 or 8 seconds.  No other keypresses 
register immediately but will occur around 7 seconds later. 

  This occurs in GNOME, GNOME applications and also for non-GNOME
  applications such as Firefox and Chrome.

  
  lsb_release -rd:

  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04


  apt-cache policy gnome-session:

  gnome-session:
Installed: 3.24.0-0ubuntu1
Candidate: 3.24.0-0ubuntu1
Version table:
   *** 3.24.0-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.24.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Apr 10 11:39:40 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (332 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1681290/+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 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

[Daniel van Vugt]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=208965
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887968

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

Status in Linux:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address 

[Desktop-packages] [Bug 1893567] Re: Login name ellipsis/dot-dot-dot (scaling too large to fit the text in) on login screen using mutter 3.36.4-0ubuntu0.20.04.2

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Fix Released

-- 
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/1893567

Title:
  Login name ellipsis/dot-dot-dot (scaling too large to fit the text in)
  on login screen using mutter 3.36.4-0ubuntu0.20.04.2

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Recently, my Ubuntu 20.04.1 login screen started showing my username
  as a dot-dot-dot, with a vertical scroll, despite being my user name
  only four letters (i.e.: kopa). It is the only user account in the
  system too.

  I've attached a screenshot of the login screen where the issue can be
  seen.

  GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No
  changes to its configuration were made.

  I can provide whatever extra information that could be useful in
  diagnosing this problem.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1893567/+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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

[Daniel van Vugt]

Also tracking in
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd

** Description changed:

+ https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
+ 
+ ---
+ 
  Launching terminator crashes gnome-shell, happens on two separate
  machines.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
-  LANG=fi_FI.UTF-8
-  PATH=(custom, user)
-  SHELL=/bin/zsh
-  XDG_RUNTIME_DIR=
+  LANG=fi_FI.UTF-8
+  PATH=(custom, user)
+  SHELL=/bin/zsh
+  XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? ()
-  g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? ()
+  g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

-- 
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/1897765

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd

  ---

  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+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 1896440] Re: gnome-shell crashed with SIGABRT in __GI_raise()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1898910 ***
https://bugs.launchpad.net/bugs/1898910

Looks like either bug 1898005 or bug 1898910.

** This bug has been marked a duplicate of bug 1898910
   gnome-shell crashes when you try to change the resolution 
[St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child 
== NULL)] called from DesktopGrid::_backgroundDestroyed()

-- 
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/1896440

Title:
  gnome-shell crashed with SIGABRT in __GI_raise()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  doing nothing, just firefox open.

  corrado@corrado-n7-gg-0918:~$ inxi -Fxx
  System:Host: corrado-n7-gg-0918 Kernel: 5.8.0-18-generic x86_64 bits: 64 
compiler: N/A Desktop: N/A wm: gnome-shell 
 dm: GDM3 Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 
 Chassis: type: 10 
 serial:  
 Mobo: Dell model: 0C1PF2 v: A00 serial:  
UEFI: Dell v: 1.5.0 date: 12/17/2019 
  Battery:   ID-1: BAT0 charge: 22.4 Wh condition: 37.1/42.0 Wh (88%) volts: 
11.6/11.4 model: SWD-ATL3.618 DELL WJPC403 
 serial: 6595 status: Discharging 
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 L2 cache: 6144 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046 
 Speed: 1955 MHz min/max: 400/3600 MHz Core speeds (MHz): 1: 2931 
2: 2788 3: 2444 4: 822 5: 2356 6: 3050 7: 3601 
 8: 564 
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus ID: 00:02.0 chip ID: 8086:8a56 
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus ID: 1-6:3 chip ID: 0bda:5520 
 Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: 
modesetting unloaded: fbdev,vesa 
 resolution: 1920x1080~60Hz s-dpi: 96 
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
20.1.7 direct render: Yes 
  Audio: Device-1: Intel Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:34c8 
 Sound Server: ALSA v: k5.8.0-18-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000 
 bus ID: 01:00.0 chip ID: 10ec:8136 
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci v: kernel 
 port: 3000 bus ID: 02:00.0 chip ID: 168c:0042 
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 
 Device-3: Qualcomm Atheros type: USB driver: btusb bus ID: 1-10:4 
chip ID: 0cf3:e009 
  Drives:Local Storage: total: 476.94 GiB used: 8.05 GiB (1.7%) 
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
 serial: 201PD3JEPTML 
  Partition: ID-1: / size: 31.25 GiB used: 8.00 GiB (25.6%) fs: ext4 dev: 
/dev/nvme0n1p7 
  Swap:  ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
priority: -2 dev: /dev/nvme0n1p2 
  Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A 
 Fan Speeds (RPM): cpu: 0 
  Info:  Processes: 250 Uptime: 1h 57m Memory: 7.55 GiB used: 1.50 GiB 
(19.8%) Init: systemd v: 246 runlevel: 5 Compilers: 
 gcc: N/A Packages: 1827 apt: 1821 snap: 6 Shell: Bash v: 5.0.17 
running in: gnome-terminal inxi: 3.1.06 
  corrado@corrado-n7-gg-0918:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 21 08:40:37 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-09-18 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200918.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about 

[Desktop-packages] [Bug 1899398] Re: /usr/bin/gnome-shell:5:meta_window_actor_thaw:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function:function_call

[Daniel van Vugt]

*** This bug is a duplicate of bug 1897765 ***
https://bugs.launchpad.net/bugs/1897765

** This bug has been marked a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

-- 
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/1899398

Title:
  /usr/bin/gnome-
  
shell:5:meta_window_actor_thaw:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function:function_call

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899398/+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 1899397] [NEW] Fan not work

[Eduardo Donoso Escobar]

Public bug reported:

No fan detected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 23:33:39 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3fb5]
InstallationDate: Installed on 2020-09-24 (18 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81WD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=98af080a-ee1a-4302-b335-e6462548d523 ro i842.nopnp=1 pci=nocrs quiet 
splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: EMCN13WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 3 14IIL05
dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05:
dmi.product.family: IdeaPad 3 14IIL05
dmi.product.name: 81WD
dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05
dmi.product.version: IdeaPad 3 14IIL05
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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/1899397

Title:
  Fan not work

Status in xorg package in Ubuntu:
  New

Bug description:
  No fan detected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 11 23:33:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3fb5]
  InstallationDate: Installed on 2020-09-24 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81WD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=98af080a-ee1a-4302-b335-e6462548d523 ro i842.nopnp=1 pci=nocrs quiet 
splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EMCN13WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05:
  dmi.product.family: IdeaPad 3 14IIL05
  dmi.product.name: 81WD
  dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05
  dmi.product.version: IdeaPad 3 14IIL05
  dmi.sys.vendor: 

[Desktop-packages] [Bug 1899398] [NEW] /usr/bin/gnome-shell:5:meta_window_actor_thaw:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function:function_call

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1897765 ***
https://bugs.launchpad.net/bugs/1897765

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: groovy

-- 
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/1899398

Title:
  /usr/bin/gnome-
  
shell:5:meta_window_actor_thaw:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function:function_call

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.38.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899398/+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 1899395] Re: /usr/bin/gnome-control-center:11:cc_sound_panel_init:g_type_create_instance:g_object_new_internal:g_object_new_valist:g_object_new

[Daniel van Vugt]

*** This bug is a duplicate of bug 1892486 ***
https://bugs.launchpad.net/bugs/1892486

** This bug has been marked a duplicate of bug 1892486
   gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from 
cc_sound_panel_init

-- 
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/1899395

Title:
  /usr/bin/gnome-control-
  
center:11:cc_sound_panel_init:g_type_create_instance:g_object_new_internal:g_object_new_valist:g_object_new

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.37.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899395/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init

[Daniel van Vugt]

** Description changed:

+ https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170
+ 
+ ---
+ 
  Not sure yet. Wait for the retrace.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
-  Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
-  PC (0x7f8657e0f611) ok
-  source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
-  destination "%xmm3" ok
+  Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
+  PC (0x7f8657e0f611) ok
+  source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
+  destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
-  ()
-  g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ()
+  g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

-- 
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/1892486

Title:
  gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu")
  from cc_sound_panel_init

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170

  ---

  Not sure yet. Wait for the retrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
   PC (0x7f8657e0f611) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init

[Daniel van Vugt]

** Summary changed:

- gnome-control-center crashed with SIGSEGV
+ gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from 
cc_sound_panel_init

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => New

** Information type changed from Private to Public

-- 
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/1892486

Title:
  gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu")
  from cc_sound_panel_init

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170

  ---

  Not sure yet. Wait for the retrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
   PC (0x7f8657e0f611) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init

[Apport retracing service]

** Tags removed: need-amd64-retrace

-- 
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/1892486

Title:
  gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu")
  from cc_sound_panel_init

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170

  ---

  Not sure yet. Wait for the retrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
   PC (0x7f8657e0f611) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

-- 
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/1892486

Title:
  gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu")
  from cc_sound_panel_init

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170

  ---

  Not sure yet. Wait for the retrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
   PC (0x7f8657e0f611) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init

[Daniel van Vugt]

It appears the crash originates from 0007-sound-Allow-volume-to-be-set-
above-100.patch

@@ -276,12 +285,23 @@ cc_sound_panel_init (CcSoundPanel *self)
G_CONNECT_SWAPPED);
   allow_amplified_changed_cb (self);

+  if (strstr (g_getenv("XDG_CURRENT_DESKTOP"), "ubuntu") != NULL) {
+gtk_widget_set_visible(self->ubuntu_output_frame, TRUE);
+gtk_widget_set_visible(GTK_WIDGET (self->output_volume_slider), FALSE);
+g_settings_bind (self->sound_settings, "allow-volume-above-100-percent",


** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: focal rls-ff-incoming

-- 
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/1892486

Title:
  gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu")
  from cc_sound_panel_init

Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170

  ---

  Not sure yet. Wait for the retrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Aug 21 18:19:17 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-07-16 (36 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>:   movdqu 
(%rdi),%xmm3
   PC (0x7f8657e0f611) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ()
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1899395] [NEW] /usr/bin/gnome-control-center:11:cc_sound_panel_init:g_type_create_instance:g_object_new_internal:g_object_new_valist:g_object_new

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1892486 ***
https://bugs.launchpad.net/bugs/1892486

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.37.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: eoan 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/1899395

Title:
  /usr/bin/gnome-control-
  
center:11:cc_sound_panel_init:g_type_create_instance:g_object_new_internal:g_object_new_valist:g_object_new

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.37.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1899395/+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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

[Daniel van Vugt]

Ignore the above message.

-- 
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/1897765

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+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 1867763] Re: gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL)

[Daniel van Vugt]

The issue with Ubuntu 20.10 (groovy) is continued in bug 1898910 and bug
1898005. Please use those bugs from now on.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1867763

Title:
  gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy:
  assertion failed: (priv->child == NULL)

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/d24a5ac63e9b00cde36f6c46ecbcc5b20442be90
  https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02
  https://errors.ubuntu.com/problem/08f665df1bdd54b07b538c33a6ab57e9ad9e85d5

  ---

  I do not know what is happened, just a reporter appeared. But 10
  minutes ago when I came to my computer after 5 minutes, it was
  restarted. It should not be restarted, just should be sleep or locked.
  However I do not know even this issue related with this report or not.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 13:32:09 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-13 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867763/+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 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from Des

[Daniel van Vugt]

See also bug 1898005.

** This bug is no longer a duplicate of private bug 1898005

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
https://bugs.launchpad.net/bugs/1898910

Title:
  gnome-shell crashes when you try to change the resolution
  [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed:
  (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed()

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02

  ---

  Ubuntu on Wayland crashes when you try to change the resolution even if your 
display supports the
  Version: 3.38.0-1ubuntu2
  Release: 20.10 Groovy Gorilla (development branch)
  What I expected to happen
  1. Login to Wayland
  2. Change the resolution
  3. Go on with my day

  What actually happened
  1. Login to Wayland
  2. Change the resolution
  3. Wait a minute to get kicked to the gdm login screen
  4. Now I am here.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  7 12:55:35 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-10-07 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-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 /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()

[Daniel van Vugt]

See also bug 1898910.

** Summary changed:

- gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: 
(priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()

** Information type changed from Private to Public

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => High

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: New => Confirmed

-- 
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/1898005

Title:
  gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed:
  (priv->child == NULL) called from
  DesktopManager::_destroyDesktopIcons()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  Sorry, I missed what was happening when this crashed.  I'll try to
  catch it next time.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 30 08:38:45 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-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 /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+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 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow

[Daniel van Vugt]

** This bug is no longer a duplicate of private bug 1898082

-- 
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/1897765

Title:
  gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
  accounting") from meta_window_actor_thaw() from
  WindowManager::_sizeChangedWindow

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+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 1898082] Re: gnome-shell crashed with signal 5 in g_log_structured_array()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1897765 ***
https://bugs.launchpad.net/bugs/1897765

** This bug has been marked a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

** Information type changed from Private to Public

-- 
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/1898082

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  First of X Plane run after uopgarde to 20.10 from  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 18:55:23 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-09-06 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-10-01 (0 days ago)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898082/+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 1898471] Re: gnome-shell crashed with signal 5 in g_log_structured_array()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1897765 ***
https://bugs.launchpad.net/bugs/1897765

** This bug is no longer a duplicate of private bug 1898082
** This bug has been marked a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

-- 
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/1898471

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  affected by lock - unlock screen

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 19:08:34 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-27 (160 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_IL
   LANGUAGE=en_IL:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-10-01 (2 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898471/+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 1899351] Re: gnome-shell crashed with signal 5 in meta_window_actor_thaw()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1897765 ***
https://bugs.launchpad.net/bugs/1897765

** This bug is no longer a duplicate of private bug 1898082
** This bug has been marked a duplicate of bug 1897765
   gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw 
accounting") from meta_window_actor_thaw() from 
WindowManager::_sizeChangedWindow

-- 
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/1899351

Title:
  gnome-shell crashed with signal 5 in meta_window_actor_thaw()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happened while in Steam big picture mode. I don't know if it's
  related.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 11 00:19:54 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-10-17 (360 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_actor_thaw () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libgjs.so.0
   () at /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gnome-shell crashed with signal 5 in meta_window_actor_thaw()
  UpgradeStatus: Upgraded to groovy on 2020-10-02 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899351/+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 865791] Re: Pointer Speed settings have no effect on touchpad

[Daniel van Vugt]

** Changed in: gnome-control-center (Ubuntu)
   Importance: Low => Medium

** Bug watch added: bugzilla.gnome.org/ #699502
   https://bugzilla.gnome.org/show_bug.cgi?id=699502

** Changed in: gnome-control-center
   Importance: Medium => Unknown

** Changed in: gnome-control-center
   Status: Invalid => Unknown

** Changed in: gnome-control-center
 Remote watch: GNOME Bug Tracker #699502 => bugzilla.gnome.org/ #699502

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1016

** Changed in: gnome-control-center
 Remote watch: bugzilla.gnome.org/ #699502 => 
gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016

** Project changed: gnome-control-center => ubuntu

** No longer affects: ubuntu

-- 
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/865791

Title:
  Pointer Speed settings have no effect on touchpad

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  While the speed setting directly under 'Mouse' will works with usb mice, the 
settings under Touchpad have no effect on touchpad  speed & or sensitivity 
  Fairly common touchpad here on dell laptop
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Video Bus   id=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Laptop Integrated Webcamid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=10   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=12   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  Date: Mon Oct  3 19:28:34 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111002)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   deja-dup   20.0-0ubuntu3
   indicator-datetime 0.3.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/865791/+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 1173922] Re: Touchpad speed cannot be adjusted via GUI

[Daniel van Vugt]

*** This bug is a duplicate of bug 865791 ***
https://bugs.launchpad.net/bugs/865791

** Summary changed:

- Mouse/Touchpad speed cannot be adjusted via GUI
+ Touchpad speed cannot be adjusted via GUI

** This bug has been marked a duplicate of bug 865791
   Pointer Speed settings have no effect on touchpad

-- 
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/1173922

Title:
  Touchpad speed cannot be adjusted via GUI

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I wanted to adjust the speed of my touchpad, because it was too fast
  for me. So I adjusted it in the settings, but every time I close the
  mouse/touchpad settings window the value will go back to default.

  I can adjust the speed in the console when I type :
  xinput --set-prop "SynPS/2 Synaptics TouchPad" "Device Accel Velocity 
Scaling" 7.

  Hope this can be fixed soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1173922/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Michael Nazzareno Trimarchi]

** Changed in: wpa (Ubuntu)
 Assignee: (unassigned) => Michael Nazzareno Trimarchi 
(michael-t16qijz8x59bnuup5)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1281588] Re: Disk standby timer is broken

[Mohammad Kazemi]

I'm experiencing this bug on Ubuntu 20.04.1 
It seems something is trying to access my disk, exactly every 10 minutes. I 
reported it as a new bug +bug/1899361

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1281588

Title:
  Disk standby timer is broken

Status in udisks:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Trusty:
  Confirmed

Bug description:
  udisks' / gnome-disk-utility's support for the drive standby timer is
  broken.  If the standby timer is set to at least 10 minutes ( which is
  the minimum on many drives ), every 10 minutes udisks tries to update
  the smart status of the drive, which resets the standby timer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1281588/+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 1899236] Re: gnome-shell crashed with SIGABRT after connecting external monitor

[Aurimas Fišeras]

*** This bug is a duplicate of bug 1898005 ***
https://bugs.launchpad.net/bugs/1898005

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899236/+attachment/5420299/+files/JournalErrors.txt

-- 
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/1899236

Title:
  gnome-shell crashed with SIGABRT after connecting external monitor

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashes while attaching external monitor, but only if some programs
  are running, e. g., Firefox.

  Maybe this time (see #1895373) core dump will not be invalid.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 08:33:27 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-07 (429 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-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 /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899236/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1899310] Re: the bluetooth headphone, although connected, the sound comes out of the notebook speakers

[RICARDO DA SILVA LISBOA]

Thank you for the feedback!  I solved reinstalling the system. As I use 
a separated home partition, everything went back fast and perfect.

Ric

Em 11/10/2020 01:02, Hui Wang escreveu:
> According to the log in the #1, the bluetooth sound card is not in the
> pulseaudio.
>
> Default Sink: alsa_output.pci-_00_1f.3.analog-stereo
>

-- 
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/1899310

Title:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the bluetooth headphone, although connected, the sound comes out of
  the notebook speakers. I can only use wired headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ricardo1300 F pulseaudio
   /dev/snd/pcmC0D0p:   ricardo1300 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 10 23:23:53 2020
  InstallationDate: Installed on 2020-10-11 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RebootRequiredPkgs:
   linux-image-5.8.0-22-generic
   linux-base
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: T-Rex_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd08/11/2017:br1.11:efr1.8:svnAcer:pnAspireES1-572:pvrV1.11:rvnAcer:rnT-Rex_SK:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: SKL
  dmi.product.name: Aspire ES1-572
  dmi.product.sku: Aspire ES1-572_1085_V1.11
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899310/+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 1899376] [NEW] Confusing versioning of language-selector

[Gunnar Hjalmarsson]

Public bug reported:

My attention was called to the existence of version 0.304 of language-
selector in some of the 
PPAs. It happened in a rather annoying way:

https://discourse.ubuntu.com/t/request-better-arabic-font-for-
ubuntu-20-04/14573/183

I don't know how 'official' those PPAs are, but I see that the only
difference compared to language-selector in the official Ubuntu archive
is that users are not prompted to pull the fcitx-ui-qimpanel package.

Ok.. So maybe it's no longer suitable for UKUI to install that package.
But if that's the case, how about handling that in the official
language-selector version?

* If it's no longer useful for any Fcitx users, we could simply drop it
from pkg_depends

* If it's still useful for non-UKUI Fcitx users, we could stop language-
selector from pulling it for UKUI users

In any case it's highly desirable to get away from a situation where
some users have a version of language-selector which blocks them from
updates.

Please let me know how you think this should best be handled.

** Affects: ubuntukylin
 Importance: Undecided
 Status: New

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntukylin
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to language-selector in Ubuntu.
https://bugs.launchpad.net/bugs/1899376

Title:
  Confusing versioning of language-selector

Status in Ubuntu Kylin:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  My attention was called to the existence of version 0.304 of language-
  selector in some of the 
  PPAs. It happened in a rather annoying way:

  https://discourse.ubuntu.com/t/request-better-arabic-font-for-
  ubuntu-20-04/14573/183

  I don't know how 'official' those PPAs are, but I see that the only
  difference compared to language-selector in the official Ubuntu
  archive is that users are not prompted to pull the fcitx-ui-qimpanel
  package.

  Ok.. So maybe it's no longer suitable for UKUI to install that
  package. But if that's the case, how about handling that in the
  official language-selector version?

  * If it's no longer useful for any Fcitx users, we could simply drop
  it from pkg_depends

  * If it's still useful for non-UKUI Fcitx users, we could stop
  language-selector from pulling it for UKUI users

  In any case it's highly desirable to get away from a situation where
  some users have a version of language-selector which blocks them from
  updates.

  Please let me know how you think this should best be handled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1899376/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Paulinski]

Is there any chance that his patch will be part of the official kernel
build soon?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: 

[Desktop-packages] [Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)

[crysman]

@coulaud I had noticed that, too, but testing it today... it seems to
work just fine.

Unfortunately, user experience with pen/stylus on GNU/Linux is MUCH
WORSE than in Windows 10 :( namely because it behaves just like if it
was a mouse - simple mouse pointer. In Win10, it is smart and you can
move the screen... I wish it could be the same in my primary OS (here in
Ubuntu)

-- 
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/1884746

Title:
  Wacom stylus not identified/available (ACER SPIN 5)

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  There is "No stylus found" in the Settings. Stylus itself is working
  flawlessly in Windows 10 OS. What shall I do to make it work in Ubuntu
  20.04 (GNOME)?

  Here is the xsetwacom output:

  xsetwacom --list
  Wacom HID 495F Pen stylus id: 9   type: STYLUS
  Wacom HID 495F Finger touch   id: 10  type: TOUCH 
  Wacom HID 495F Pen eraser id: 18  type: ERASER

  
  PS: I am currently forced to use these kernel boot parameters:

  i8042.nopnp=1 pci=nocrs

  (because of this bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232 )

  Many Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 23 12:43:21 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-19 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1884746/+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 1899361] [NEW] udisk prevent disk from standby, standby timer is broken

[Mohammad Kazemi]

Public bug reported:

It seems udisks tries to access my HDD every 10 minute. So when I set standby 
timer less than 10 minutes, It can't go to standby. 
This bug has been reported before (+bug #1281588) and seems to be fixed, But 
I'm experiencing this again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: udisks2 2.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules
Date: Sun Oct 11 19:38:48 2020
InstallationDate: Installed on 2020-10-02 (8 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X510UF.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X510UF
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook S
dmi.product.name: VivoBook S15 X510UF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: udisks (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: udisks2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Also affects: udisks (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899361

Title:
  udisk prevent disk from standby, standby timer is broken

Status in udisks package in Ubuntu:
  New
Status in udisks2 package in Ubuntu:
  New

Bug description:
  It seems udisks tries to access my HDD every 10 minute. So when I set standby 
timer less than 10 minutes, It can't go to standby. 
  This bug has been reported before (+bug #1281588) and seems to be fixed, But 
I'm experiencing this again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udisks2 2.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules
  Date: Sun Oct 11 19:38:48 2020
  InstallationDate: Installed on 2020-10-02 (8 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X510UF.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X510UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook S
  dmi.product.name: VivoBook S15 X510UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+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 1281588] Re: Disk standby timer is broken

[Mohammad Kazemi]

** Changed in: udisks2 (Ubuntu)
 Assignee: Phillip Susi (psusi) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1281588

Title:
  Disk standby timer is broken

Status in udisks:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Trusty:
  Confirmed

Bug description:
  udisks' / gnome-disk-utility's support for the drive standby timer is
  broken.  If the standby timer is set to at least 10 minutes ( which is
  the minimum on many drives ), every 10 minutes udisks tries to update
  the smart status of the drive, which resets the standby timer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1281588/+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 1899352] Re: Pulseaudio cannot be kept from starting or respawning

[ralphb]

Also, as user:

cassiopeia ~ > pulseaudio -k
N: [pulseaudio] main.c: System mode refused for non-root user. Only starting 
the D-Bus server lookup service.

Then, as root, with system mode running:

cassiopeia:~# ps aux | grep pulse
pulse   2334  0.0  0.0 239320 10568 ?Shttps://bugs.launchpad.net/bugs/1899352

Title:
  Pulseaudio cannot be kept from starting or respawning

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my freshly installed system, I need to run pulseaudio in system
  mode.  Alas, by default, pulseaudio is run in user mode, and is set to
  respawn, so that I cannot kill the user process and start pulseaudio
  in system mode.

  I tried:

  1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
  2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
  3. I removed the file /usr/bin/start-pulseaudio.  Why   Of course, this 
did nothing.
  4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 
did NOTHING.

  User mode is still starting, and respawning is enabled.

  What the heck do I have to do to get rid of user mode pulseaudio?
  Could you please clean up this clusterfuck?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+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 1899356] [NEW] chromium's file chooser has no icons

[Marius Gedminas]

Public bug reported:

This is a freshly installed Ubuntu 20.04 LTS system.  I apt installed
chromium-browser, which pulled in the snap.  I'm in an Ubuntu on Wayland
session.

The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing all
of the icons (see screenshot).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:06:45 2020
InstallationDate: Installed on 2020-10-08 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121 
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

** Attachment added: "screenshot of chromium's file chooser"
   
https://bugs.launchpad.net/bugs/1899356/+attachment/5420916/+files/Screenshot%20from%202020-10-11%2018-08-27.png

-- 
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/1899356

Title:
  chromium's file chooser has no icons

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This is a freshly installed Ubuntu 20.04 LTS system.  I apt installed
  chromium-browser, which pulled in the snap.  I'm in an Ubuntu on
  Wayland session.

  The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing
  all of the icons (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 11 18:06:45 2020
  InstallationDate: Installed on 2020-10-08 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121 
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
  Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
  SourcePackage: 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/1899356/+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 1899351] Re: gnome-shell crashed with signal 5 in meta_window_actor_thaw()

[Apport retracing service]

*** This bug is a duplicate of bug 1898082 ***
https://bugs.launchpad.net/bugs/1898082

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1898082, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420870/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420872/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420877/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420878/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420879/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420881/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1899351/+attachment/5420882/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1898082

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1899351

Title:
  gnome-shell crashed with signal 5 in meta_window_actor_thaw()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happened while in Steam big picture mode. I don't know if it's
  related.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 11 00:19:54 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-10-17 (360 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_actor_thaw () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libgjs.so.0
   () at /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gnome-shell crashed with signal 5 in meta_window_actor_thaw()
  UpgradeStatus: Upgraded to groovy on 2020-10-02 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899351/+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 1899352] [NEW] Pulseaudio cannot be kept from starting or respawning

[ralphb]

Public bug reported:

On my freshly installed system, I need to run pulseaudio in system mode.
Alas, by default, pulseaudio is run in user mode, and is set to respawn,
so that I cannot kill the user process and start pulseaudio in system
mode.

I tried:

1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
3. I removed the file /usr/bin/start-pulseaudio.  Why   Of course, this did 
nothing.
4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 
did NOTHING.

User mode is still starting, and respawning is enabled.

What the heck do I have to do to get rid of user mode pulseaudio?  Could
you please clean up this clusterfuck?

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Pulseaudio cannot be stopped or kept from respawning
+ Pulseaudio cannot be kept from starting or respawning

-- 
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/1899352

Title:
  Pulseaudio cannot be kept from starting or respawning

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On my freshly installed system, I need to run pulseaudio in system
  mode.  Alas, by default, pulseaudio is run in user mode, and is set to
  respawn, so that I cannot kill the user process and start pulseaudio
  in system mode.

  I tried:

  1. Editing /etc/pulse/client.conf, setting autospawn = no.  This did nothing.
  2. Removing the file /etc/pulse/client.conf.d/01-respawn-something.  I cannot 
even begin to fathom why such a file would exist.  Anyway, this did nothing.
  3. I removed the file /usr/bin/start-pulseaudio.  Why   Of course, this 
did nothing.
  4. I removed the file /etc/xdg/autostart/pulseaudio.desktop.  Why on earth do 
you implement four different ways to annoy your users?  On the other hand, this 
did NOTHING.

  User mode is still starting, and respawning is enabled.

  What the heck do I have to do to get rid of user mode pulseaudio?
  Could you please clean up this clusterfuck?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899352/+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 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]

[Kai-Heng Feng]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

If the issue is not fixed upstream, please file an upstream bug at intel 
graphics:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

-- 
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/1896091

Title:
  [i915] graphic corruption following orkqueue: PF_MEMALLOC task
  131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work
  [i915]

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
  unattended for a while, and then got the error message and now have
  funny lines on activity, e.g. red lines flashing on top of gnome-shell
  bar when switching windows, or white blocks/lines around typing text.

  This is the second or third time it happened, reboot fixes it until
  the error pops up again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-19-generic 5.8.0-19.20
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 19:14:11 2020
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jak5052 F pulseaudio
   /dev/snd/controlC1:  jak5052 F pulseaudio
   /dev/snd/pcmC1D0p:   jak5052 F...m pulseaudio
   /dev/snd/controlC0:  jak5052 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (917 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-19-generic N/A
   linux-backports-modules-5.8.0-19-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2020
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  

[Desktop-packages] [Bug 1899349] [NEW] Jack_control in jackd2 1.9.14 will not accept char parameters

[Len Ovens]

Public bug reported:

trying to set self-connect-mode (for example):
$ jack_control eps self-connect-mode e
gives:
--- engine param set "self-connect-mode" -> "e"
Traceback (most recent call last):
  File "/usr/bin/jack_control", line 400, in 
main()
  File "/usr/bin/jack_control", line 283, in main
configure_iface.SetParameterValue(['engine', param], 
python_type_to_jackdbus_type(value, type_char))
  File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type
return dbus.Byte(value);
TypeError: Expected a bytes or str of length 1, or an int in the range 0-255

This bug has been fixed upstream in commit ba28ffa

@@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char):
if type_char == "b":
return bool_convert(value);
elif type_char == "y":
-return dbus.Byte(value);
+return dbus.Byte(ord(value));
elif type_char == "i":
return dbus.Int32(value)
elif type_char == "u":

** Affects: jackd2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899349

Title:
  Jack_control in jackd2 1.9.14 will not accept char parameters

Status in jackd2 package in Ubuntu:
  New

Bug description:
  trying to set self-connect-mode (for example):
  $ jack_control eps self-connect-mode e
  gives:
  --- engine param set "self-connect-mode" -> "e"
  Traceback (most recent call last):
File "/usr/bin/jack_control", line 400, in 
  main()
File "/usr/bin/jack_control", line 283, in main
  configure_iface.SetParameterValue(['engine', param], 
python_type_to_jackdbus_type(value, type_char))
File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type
  return dbus.Byte(value);
  TypeError: Expected a bytes or str of length 1, or an int in the range 0-255

  This bug has been fixed upstream in commit ba28ffa

  @@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char):
  if type_char == "b":
  return bool_convert(value);
  elif type_char == "y":
  -return dbus.Byte(value);
  +return dbus.Byte(ord(value));
  elif type_char == "i":
  return dbus.Int32(value)
  elif type_char == "u":

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Nicholas Guriev]

Marco Trevisan, as to your request, I am attaching logs that are
appearing in system journal while flameshort start. Debug level was been
raised as otherwise the journal was empty.

** Attachment added: "journalctl-b0-usr-bin-gnome-shell-ef.txt"
   
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+attachment/5420868/+files/journalctl-b0-usr-bin-gnome-shell-ef.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1897754

Title:
  flameshot: The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Nicholas Guriev]

I run into the issue when autostart feature of flameshot is activate. I
daresay there is some sort of race condition while system startup, and
the actual issue is in the gnome-shell-extension-appindicator package.
There is something in diff between 33-1 and 34-1 versions that is
breaking the app icon.

One possible workaround is to add a short delay before flameshort start
into the ~/.config/autostart/Flameshot.desktop file and make Exec
directive the following:

  Exec=sh -c 'sleep 1 && exec flameshot'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1897754

Title:
  flameshot: The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1897754

Title:
  flameshot: The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: flameshot (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1897754

Title:
  flameshot: The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Nicholas Guriev]

** Summary changed:

- The icon does not appear in the GNOME bar
+ flameshot: The icon does not appear in the GNOME bar

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1897754

Title:
  flameshot: The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Diogo André Cardoso Pereira]

I really would like to use pop os for my main os and i cant because of
this bug :( There is any update so far on this ? or any temporary fix
that anyone can help?

-- 
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/1553685

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 263505] Re: Wishlist: add "use input as a search term" to "address not found" page

[Paul White]

Upstream bug was closed "VERIFIED FIXED" on 2020-04-30.

Confirmed fixed in Ubuntu by using Firefox 81.0 and Ubuntu 20.04
by entering 'console.log' in the address bar and seeing a prompt
to search for that term and not being directed towards a
non-existent domain.


** Changed in: firefox (Ubuntu)
   Status: Incomplete => Fix Released

-- 
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/263505

Title:
  Wishlist: add "use input as a search term" to "address not found" page

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  Altogether too often when I get the "Address Not Found" page, it is
  because I expected too much from the Wonderful Bar or whatever it's
  called.  It would be a useful addition if the "Address Not Found" page
  could offer the option to use the stuff you typed into the location
  bar as input for your designated search engine, and/or perform history
  search on those terms.  (For me, the former is the more useful, but I
  expect both would be handy, and the effort to offer both is probably
  marginal if you decide to do one or the other.)

  All to often, what you typed in is no longer visible in the location
  bar, because http:// gets prepended and sometimes a .com appended to
  what is displayed in the location bar at the point you get the
  "Address Not Found" error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/263505/+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 1899340] [NEW] preinstall `plasma-discover-backend-flatpak` by default

[ruruoli]

Public bug reported:

Would be nice to have ability to use flatpak out of the box.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1899340

Title:
  preinstall `plasma-discover-backend-flatpak` by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Would be nice to have ability to use flatpak out of the box.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1899340/+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 1899337] Re: Xwayland crashed with SIGABRT in OsAbort()

[Apport retracing service]

*** This bug is a duplicate of bug 1751508 ***
https://bugs.launchpad.net/bugs/1751508

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1751508, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420796/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420799/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420811/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420813/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420814/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420815/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1899337/+attachment/5420816/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1751508
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError("Couldn't add screen\n") from InitOutput()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1899337

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  happens oftens and sometimes the desktop is not populated

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.8-2ubuntu6
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Oct  6 20:01:43 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GK208B [GeForce GT 710] 
[19da:6326]
  InstallationDate: Installed on 2016-10-30 (1441 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth 
/run/user/129/.mutter-Xwaylandauth.POD7R0 -listen 4 -displayfd 5 -listen 6 
-extension SECURITY
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-19-generic 
root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash
  Renderer: Software
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   InitOutput ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 04/06/2016
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GA-990FX-GAMING
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/06/2016:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.
  separator:
   
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.0-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.0-1
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1024700] Re: Session never locks automatically if no screen off timeout set

[Paul White]

This issue has sat "Incomplete" for more than seven years now without
any further comment. I'm going to close it as "Invalid".

Please feel free to re-open this bug report if this is still an issue
relevant to a currently supported release of Ubuntu.

** Changed in: hundredpapercuts
   Status: Incomplete => Invalid

** Changed in: gnome-power-manager (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ayatana-design
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1024700

Title:
  Session never locks automatically if no screen off timeout set

Status in Ayatana Design:
  Invalid
Status in One Hundred Papercuts:
  Invalid
Status in gnome-power-manager package in Ubuntu:
  Invalid

Bug description:
  My system settings for Brightness and Lock:

  Turn screen off when inactive for: Never
  Lock: On
  Lock screen after: 30 minutes

  The problem: when there is no screen off timeout but there is a lock
  timeout, the session never locks.

  Under this configuration, I expect the OS to show a black lock screen,
  in the same manner when I lock the session manually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1024700/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

[Michael Nazzareno Trimarchi]

** Patch added: 
"0001-dbus-Fix-GetAll-message-if-ap_ifaces-are-not-availab.patch"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+attachment/5420793/+files/0001-dbus-Fix-GetAll-message-if-ap_ifaces-are-not-availab.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  New

Bug description:
  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc. 
  The regression was introduced when someone try to have the Station attribute 
supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1899329] [NEW] symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO'

[m]

Public bug reported:

Hallo,

A similar bug has been described (and repaired) earlier. See

https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1070669.

I first encountered this typographical error on the website of Wikipedia
(using the Firefox web browser)

https://en.wikipedia.org/wiki/C0_and_C1_control_codes

when looking at the table representing ASCII control characters.

U+240e ␎ Shift Out should probably be represented by `SO' and not `SS'.
See for reference (as in the report referred to above) the following
document on the Unicode website

http://www.unicode.org/charts/PDF/U2400.pdf.

This typographical error also seems to appear in other programs such as
Libre Office Calc, the xfc4-terminal, chromium-browser. I am guessing it
is visible in most, and possibly in all programs.

Kind regards,
Michael

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gucharmap 1:10.0.4-1
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct 11 10:55:22 2020
InstallationDate: Installed on 2019-02-17 (601 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
SourcePackage: gucharmap
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gucharmap (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gucharmap in Ubuntu.
https://bugs.launchpad.net/bugs/1899329

Title:
  symbol U+240e seems to misrepresent the `Shift Out' character by `SS'
  instead of `SO'

Status in gucharmap package in Ubuntu:
  New

Bug description:
  Hallo,

  A similar bug has been described (and repaired) earlier. See

  https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1070669.

  I first encountered this typographical error on the website of
  Wikipedia (using the Firefox web browser)

  https://en.wikipedia.org/wiki/C0_and_C1_control_codes

  when looking at the table representing ASCII control characters.

  U+240e ␎ Shift Out should probably be represented by `SO' and not
  `SS'. See for reference (as in the report referred to above) the
  following document on the Unicode website

  http://www.unicode.org/charts/PDF/U2400.pdf.

  This typographical error also seems to appear in other programs such
  as Libre Office Calc, the xfc4-terminal, chromium-browser. I am
  guessing it is visible in most, and possibly in all programs.

  Kind regards,
  Michael

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gucharmap 1:10.0.4-1
  ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Oct 11 10:55:22 2020
  InstallationDate: Installed on 2019-02-17 (601 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gucharmap
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1899329/+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 1899326] [NEW] after install nvidia-340, unable to login with white screen with logout button only

[the Dee]

Public bug reported:

I just installed and updated Ubuntu 20.10.

During installation, the following error message is appeared
(Everythings were fine with Ubuntu 20.04


nvidia-340 (340.108-0ubuntu5) 설정하는 중입니다 ...
dpkg: 오류: version '-' has bad syntax: revision number is empty
dpkg: 오류: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
Adding system user `nvidia-persistenced' (UID 122) ...
Adding new group `nvidia-persistenced' (GID 130) ...
Adding new user `nvidia-persistenced' (UID 122) with group 
`nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-340-340.108 DKMS files...
Building for 5.8.0-20-generic 5.8.0-21-generic
Building for architecture x86_64
Building initial module for 5.8.0-20-generic
ERROR (dkms apport): kernel package linux-headers-5.8.0-20-generic is not 
supported
Error! Bad return status for module build on kernel: 5.8.0-20-generic (x86_64)
Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
dpkg: error processing package nvidia-340 (--configure):
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for libc-bin (2.32-0ubuntu3) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu4) ...
Processing triggers for initramfs-tools (0.137ubuntu12) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-21-generic
처리하는데 오류가 발생했습니다:
nvidia-340
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Uname: Linux 5.8.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 16:31:40 2020
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ko_KR.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Attachment added: "dkms_dbversion"
   
https://bugs.launchpad.net/bugs/1899326/+attachment/5420764/+files/dkms_dbversion

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1899326

Title:
  after install nvidia-340, unable to login with white screen with
  logout  button only

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I just installed and updated Ubuntu 20.10.

  During installation, the following error message is appeared
  (Everythings were fine with Ubuntu 20.04

  
  nvidia-340 (340.108-0ubuntu5) 설정하는 중입니다 ...
  dpkg: 오류: version '-' has bad syntax: revision number is empty
  dpkg: 오류: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  Adding system user `nvidia-persistenced' (UID 122) ...
  Adding new group `nvidia-persistenced' (GID 130) ...
  Adding new user `nvidia-persistenced' (UID 122) with group 
`nvidia-persistenced' ...
  Not creating home directory `/'.
  Loading new nvidia-340-340.108 DKMS files...
  Building for 5.8.0-20-generic 5.8.0-21-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-20-generic
  ERROR (dkms apport): kernel package linux-headers-5.8.0-20-generic is not 
supported
  Error! Bad return status for module build on kernel: 5.8.0-20-generic (x86_64)
  Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
  dpkg: error processing package nvidia-340 (--configure):
  installed nvidia-340 package post-installation script subprocess returned 
error exit status 10
  Processing triggers for mime-support (3.64ubuntu1) ...
  Processing triggers for libc-bin (2.32-0ubuntu3) ...
  Processing triggers for man-db (2.9.3-2) ...
  Processing triggers for desktop-file-utils (0.24-1ubuntu4) ...
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-21-generic
  처리하는데 오류가 발생했습니다:
  nvidia-340
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: 

[Desktop-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1

[Amr Ibrahim]

That .diff is actually auto-generated from the package in my PPA:
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

The package is built fine for all architectures in Focal and installs
and runs OK. Maybe the .diff got corrupted from downloading and
uploading again!

Could you please try the package from the PPA?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643

Title:
  [SRU] Update libgweather to 3.36.1

Status in libgweather:
  Unknown
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Focal:
  New
Status in libgweather package in Debian:
  Unknown

Bug description:
  [Impact]

  libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36.

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  This version works around the unavailability of the NOAA weather
  services by using very short-term forecasts as current weather
  conditions.

  Sometimes the current weather is not available because the NOAA
  weather servers aren't working correctly. Version 3.36.1 fixes the
  unavailability of current temperature in some locations.

  
  [Test case]

  Make sure that gnome-weather is still working properly and the weather
  in gnome-shell is shown when gnome-weather is installed.

  
  [Regression potential]

  The regression potential is low since the changes in version 3.36.1
  are small.

  
  [Other]

  libgweather 3.36.1 has been successfully built as a no-change backport
  from Groovy to Focal in my PPA and runs fine:

  
https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter=

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 23 19:05:21 2020
  InstallationDate: Installed on 2020-04-26 (119 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1892643/+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 1899152] Re: Resolution not set or inappropriate

[SatishVSS]

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

-- 
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/1899152

Title:
  Resolution not set or inappropriate

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Defaultly it is set to 1024x768. But my screen resolution is 1440x400.

  I tried using terminal to add newmode and saved with the desired
  resolution. When I aplied the new one, the system gets hanged
  everytime.

  Previuosly I used 14.04 version. Then there was no issue. I added
  newmode using terminal. And next it was fine.

  But now it is not allowing me to set.

  Please make this issue clear.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 16:03:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:29c2]
  InstallationDate: Installed on 2020-10-02 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: OEM OEM
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=948d3ae0-06d2-4522-8970-f6183d8b94fa ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2018
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: OEM
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  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/+bug/1899152/+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