[Desktop-packages] [Bug 1899235] [NEW] Touchpad freeze after overnight sleep

[Meir Levi]

Public bug reported:

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

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


** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu

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

Title:
  Touchpad freeze after overnight sleep

Status in xorg package in Ubuntu:
  New

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 

[Desktop-packages] [Bug 1890843] Re: Freeze

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Freeze

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug:
  1. double left mouse click on launcher icon on left toolbar (usually happens 
with Chromium Browser icon)
  2. Desired result: Drop down menu appears with options to open Chromium 
browser 
  3. Actual result when bug appears: Drop down menu appears then whole desktop 
freezes. No further mouseclicks on display work. Dropdown menu remains frozen 
on display.
  4. Current workaround:
  When bug appears, the  desktop can be unfrozen via cntl-alt-del keys but the 
drop-down menu remains frozen in place. Next, the frozen drop-down menu can now 
be closed by clicking on the "Activities" menu on the upper-left corner of the 
desktop and then clicking on the icon with the frozen drop-down menu. These 
actions close the frozen drop-down menu and restore normal operation of the 
Gnome III for a while until the bug pops up again. This bug has become 
especially common now rendering the desktop almost unusable and I'm thinking of 
replacing Gnome III due to this.
  Thanks, Phil

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:82:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  7 12:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951]
  InstallationDate: Installed on 2018-06-01 (798 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Supermicro X9DR3-F
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DR3-F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X9DR3-F
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1890494] Re: Closing Rhythmbox does not free the media keys

[Launchpad Bug Tracker]

[Expired for rhythmbox (Ubuntu) because there has been no activity for
60 days.]

** Changed in: rhythmbox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Closing Rhythmbox does not free the media keys

Status in rhythmbox package in Ubuntu:
  Expired

Bug description:
  Closing Rhythmbox, does not free the media keys, and no program can
  use them after that, not even Rhythmbox if you restart it.

  This seems to be very close to bug #1036489, but that one was active 8
  years ago, and was marked as expired 6 years ago.

  Restarting the machine frees the media keys again.

  Steps to reproduce:

  1. Verify that the media keys work (restart the machine if not)
  2. close rhythmbox with right click on the taskbar icon, use "stop & quit"
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. End the 'rhythmbox' process
  3. reopen rhythmbox, the media keys do not work.

  1. Verify that the media keys work (restart the machine if not)
  2. in rhythmbox go to preferences -> plugins -> click preferences for any 
plugin
  3. click the 'restart' next to "Restart the player for the changes to take 
effect"
  4. once rhythmbox restarts, the media keys do not work anymore.

  
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  
  $ apt-cache policy rhythmbox
  rhythmbox:
Installed: 3.4.4-1ubuntu2
Candidate: 3.4.4-1ubuntu2
Version table:
   *** 3.4.4-1ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1890494/+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 1716205] Re: slovak keyboard does not work in kde

[Launchpad Bug Tracker]

[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  slovak keyboard does not work in kde

Status in ibus package in Ubuntu:
  Expired

Bug description:
  KDE Plasma 5.9.5. I have the Slovak QWERTY keyboard as the secondary
  one. However when I switch to SK keyboard I am not able to input
  slovak-based keys. It is as if the keyboard was not switched at all
  and the layout stays at US-EN. For example pressing + c should yield č
  but it instead prints +c. Previously this randomly failed in some
  apps, e.g. it worked in Libre Office Writer but did not work in
  Konsole; now it doesn't work at all. Pressing 3 should yield š but
  instead types 3.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep 10 10:28:48 2017
  InstallationDate: Installed on 2014-03-07 (1282 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to zesty on 2017-03-29 (165 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1716205/+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 1898713] Re: Xorg crashes sometimes with Easystrokes

[DarkTrick]

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

> Separately, I notice you seem to be using the *old* 'intel' graphics
driver

Maybe that explains crashes with VLC since upgrade to 20.04, I recently 
reported.
Shouldn't the system change it at some point? E.g. during the upgrade process? 
Is that actually another bug report?

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

Title:
  Xorg crashes sometimes with Easystrokes

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg crashes, session closes, all unsaved data is gone.

  What I did / Reproducing
  ===

  It happens when I use Easystrokes to emulate `Ctrl+F4` or
  `Ctrl+PageUp/Down`.

  So far it happened about 5 recognized times, 3 recorded within the
  last 3(?) month. twice during tab switching in incognito Firefox and
  once in VSCode.

  Reproducability
  
  I feel it's very consistent in crashing in Firefox incognito. But it's not 
purposely reproducible 100%.

  I would give more information, but the stacktrace of the crashdump
  does not tell much. I installed debug symbols for xorg, but they made
  no change viewing it.

  Here is the (obscured) stack trace:

  ```
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
  [New LWP 100716]
  [New LWP 100705]
  [New LWP 100704]
  [New LWP 100707]
  [New LWP 100709]
  [New LWP 100708]
  [New LWP 100706]
  [New LWP 100711]
  [New LWP 100710]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  --Type  for more, q to quit, c to continue without paging--
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x55a0da61fe9c in miPointerSetPosition (
  pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
  screenx=screenx@entry=0x7f707b57d570, 
  screeny=screeny@entry=0x7f707b57d578, 
  nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
  at ../../../../mi/mipointer.c:610
  610   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
  (gdb) 
  (gdb) 
  (gdb) bt full
  #0  0x55a0da61fe9c in miPointerSetPosition
  (pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0, 
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578, 
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at 
../../../../mi/mipointer.c:610
  pScreenPriv = 
  pScreen = 
  newScreen = 0x254
  x = 802
  y = 596
  switch_screen = 0
  should_constrain_barriers = 0
  i = 
  pPointer = 0x0
  #1  0x55a0da4ec840 in positionSprite
  (dev=dev@entry=0x55a0dc969400, mode=mode@entry=0, 
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580, 
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570, 
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 801.02961125081322
  tmpy = 595.47038874918678
  #2  0x55a0da4ecf4d in positionSprite
  (events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578, 
scre--Type  for more, q to quit, c to continue without paging--
  enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580, 
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at 
../../../../dix/getevents.c:952
  scr = 0x0
  num_events = 2
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0 
}, unaccelerated = {0 }}
  scr = 
  num_barrier_events = 0
  #3  fill_pointer_events (events=0x7f708d903c20, 
  events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, 
type=, buttons=buttons@entry=0, ms=ms@entry=289728198, 
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at 
../../../../dix/getevents.c:1434
  num_events = 2
  --Type  for more, q to quit, c to continue without paging--
  event = 
  raw = 0x7f708d903010
  screenx = 801.02961125081322
  screeny = 595.47038874918678
  devx = 801.02961125081322
  devy = 595.47038874918678
  sx = 0
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 

[Desktop-packages] [Bug 1733292] Re: Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events

[DarkTrick]

3 years later.
I support Wes's statement about the importance of the bug. This is a real 
dealbreaker.

I cannot write any short notes, no unsaved emails, temporary documents,
draw temporary images, because I use my OS in constant fear it might
break down out of a sudden.

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

Title:
  Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition
  from positionSprite from positionSprite from fill_pointer_events

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  occasional screen locks up, the session ends, reverts to display
  manager (lightdm?), have to log in again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Nov 20 09:11:46 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.0, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:05a4]
  InstallationDate: Installed on 2014-08-13 (1194 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  MachineType: Dell Inc. OptiPlex 9020
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e2d4a833-d4fd-4295-95a5-57c52551e6ba ro splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x56286fd4bad0:movswl 0x8(%rdi),%ecx
   PC (0x56286fd4bad0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   miPointerSetPosition ()
   ()
   ()
   GetPointerEvents ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd05/23/2017:svnDellInc.:pnOptiPlex9020:pvr00:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.88-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Sep 12 12:13:51 2017
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1733292/+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] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1896440/+attachment/5420225/+files/Stacktrace.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/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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896440/+subscriptions

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

[Desktop-packages] [Bug 1896440] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1896440/+attachment/5420227/+files/ThreadStacktrace.txt

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

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

** 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/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 this bug go to:

[Desktop-packages] [Bug 1896440] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1896440/+attachment/5420226/+files/StacktraceSource.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/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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896440/+subscriptions

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

[Desktop-packages] [Bug 1896440] gnome-shell crashed with SIGABRT in __GI_raise()

[Apport retracing service]

StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
 __GI_abort () at abort.c:79
 ?? () from 
/tmp/apport_sandbox_jvswt3b7/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.0
 g_assertion_message_expr () from 
/tmp/apport_sandbox_jvswt3b7/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.0
 st_bin_destroy () from 
/tmp/apport_sandbox_jvswt3b7/usr/lib/gnome-shell/libst-1.0.so

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

[Desktop-packages] [Bug 1895897] Re: Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: Assertion `pScreen->myNum < xf86NumScreens' failed.

[Apport retracing service]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


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

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

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

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

Status in xorg-server package in Ubuntu:
  Invalid

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
  

[Desktop-packages] [Bug 1896273] Re: emacs-gtk crashed with SIGABRT in raise()

[Apport retracing service]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


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

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

** Tags removed: need-amd64-retrace

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

Title:
  emacs-gtk crashed with SIGABRT in raise()

Status in emacs package in Ubuntu:
  Invalid

Bug description:
  The emacs application was sitting idle at the time of the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: emacs-gtk 1:26.3+1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 18 10:29:27 2020
  ExecutablePath: /usr/bin/emacs-gtk
  ExecutableTimestamp: 1585172759
  InstallationDate: Installed on 2020-04-17 (154 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: emacs --daemon
  ProcCwd: /home/nbock/Work/github.com/nicolasbock/anbox-setup
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  Signal: 6
  SourcePackage: emacs
  StacktraceTop:
   raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: emacs-gtk crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (60 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  separator:

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

[Apport retracing service]

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

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 #1543192, 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/1896653/+attachment/5413267/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from 
WakeupHandler()

** 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/1896653

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  System program problem detected error message after logging in on Ubuntu 
Budgie 20.10.
  This error happens approximately 50% of the time when logging in.  After 
logging in, everything then seems to work normally.  Aside from the error 
message, there seems to be no noticeable effect of the crash.

  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
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Sep 22 14:33:54 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1599226356
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x55e7786bbf90, argc=11, argv=0x7ffd94d62b18, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd94d62b08) at ../csu/libc-start.c:314
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  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.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1897388] Re: gnome-shell crashed with SIGABRT in __GI_raise()

[Apport retracing service]

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

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 #1898005, 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/1897388/+attachment/5414453/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1897388

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash reporting
  with automatically created report.

  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
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 26 19:28:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.notifications' b'application-children' 
b"['usb-creator-gtk', 'org-gnome-nautilus', 'update-manager', 'apport-gtk', 
'firefox']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2020-09-26 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs:
   linux-image-5.8.0-19-generic
   linux-base
  RelatedPackageVersions: mutter-common 3.38.0-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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897388/+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 1896831] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1867763, 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/1896831/+attachment/5413613/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1867763
   gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: 
assertion failed: (priv->child == NULL)

** 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/1896831

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  updated to latest packages on groovy (apt update, apt upgrade) and
  rebooted.  Logged in and left system unattended to make dinner, on
  return gnome-shell had crashed and dumped me back to login screen.

  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-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 23 20:34:15 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-12-02 (1391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to groovy on 2020-08-10 (44 days ago)
  UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
  separator:

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

[Apport retracing service]

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

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 #1898005, 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/1897789/+attachment/5415377/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1897789

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I was working with gnome-control-center.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  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 15:33:20 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897789/+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

[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/1897765/+attachment/5415319/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/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 1895442] 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/1895442/+attachment/5410378/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1895442/+attachment/5410397/+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/1895442

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Every time when I restart my msi notebook this xorg crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: xwayland 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
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep 13 07:09:58 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.66, 5.4.0-42-generic, x86_64: installed
   nvidia, 450.66, 5.8.0-18-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 
(Mobile) [1462:1214]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 
1060 Mobile] [1462:1214]
  InstallationDate: Installed on 2020-09-01 (11 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
  MachineType: Micro-Star International Co., Ltd. GE63 Raider RGB 8RE
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth 
/run/user/126/.mutter-Xwaylandauth.7N1LQ0 -listen 4 -listen 5 -displayfd 6 
-listen 7
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=9926a422-c14f-4e67-9f7e-4b93bff19305 ro persistent quiet splash 
vt.handoff=7
  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: 10/18/2018
  dmi.bios.release: 1.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16P5IMS.10D
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16P5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16P5IMS.10D:bd10/18/2018:br1.13:svnMicro-StarInternationalCo.,Ltd.:pnGE63RaiderRGB8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16P5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GE
  dmi.product.name: GE63 Raider RGB 8RE
  dmi.product.sku: 16P5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  separator:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  

[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

[Apport retracing service]

** Tags added: 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/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 1896440] Re: gnome-shell crashed with SIGABRT in __GI_raise()

[Apport retracing service]

** Tags added: 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/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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896440/+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 1895837] Re: [groovy] totem crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

** Tags added: need-amd64-retrace

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

Title:
  [groovy] totem crashed with SIGSEGV in g_main_context_dispatch()

Status in totem package in Ubuntu:
  Fix Released

Bug description:
  This same video was played ok by totem few days ago.
  This video is played ok by mpv.

  corrado@corrado-n4-gg-0905:~/Videos$ totem DSCF0010.AVI

  (totem:2316): GLib-CRITICAL **: 15:04:52.090: g_propagate_error:
  assertion 'src != NULL' failed

  (totem:2316): GLib-GIO-CRITICAL **: 15:04:52.090: g_task_return_error:
  assertion 'error != NULL' failed

  (totem:2316): GLib-GIO-CRITICAL **: 15:04:52.092: g_task_propagate_boolean: 
assertion 'task->result_set' failed
  Segmentation fault (core dumped)
  corrado@corrado-n4-gg-0905:~/Videos$ 

  totem last changes are:

  totem (3.38.0-1ubuntu1) groovy; urgency=medium

* Merge with debian, remaining changes:
  - debian/control.in:
+ Use ubuntu-desktop vcs
  - debian/gbp.conf: Use ubuntu settings
  - Add dont-make-compulsory.patch:
+ Allow Totem to be uninstalled from the GNOME Software app.
  - Add 91_quicklist_entries.patch:
+ Add static quicklist.
  - Add Add-Mute-action.patch:
+ Add Mute action so that we can use it as a Desktop Action
* debian/patches: Refresh

   -- Marco Trevisan (Treviño)   Tue, 15 Sep 2020
  03:05:46 +0200

  totem (3.38.0-1) unstable; urgency=medium

[ Marco Trevisan (Treviño) ]
* New upstream release:
  - Add support for Tracker 3 indexer
  - Support auto-loading VTT subtitles
  - Fix some stutters on some systems when current state is being
saved to disk
  - Better error messages when SSL/TLS support is missing
  - Improve the search entry's behaviour
  - Improve the way time is written in some places
  - Remove association with audio files, as we really don't want
to be an audio player
  - Fix YouTube search not working
  - Fix a number of keyboard shortcuts not working
  - Remove a number of deprecated calls
* debian/control: Bump dependencies to match upstream
* debian/patches: Refresh
* d/p/test-totem-Properly-handle-menu-text-for-undetermined-lan.patch:
  - Ensure that menu-text uses generic values on undefined language.
Tests were failing with recent gstreamer as the returned language was
not "NULL", but "Undetermined", causing this value to be used as
language instead of the generic fallback.
* debian: Depend on debhelper-compat = 13.
  As per this we can remove the --fail-missing flag on dh_missing (as it's
  already the default)

[ Laurent Bigonville ]
* Disable integration at-spi2 for the tests and fix the nocheck 
build-profile

   -- Marco Trevisan (Treviño)   Tue, 15 Sep 2020
  02:47:32 +0200

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: totem 3.38.0-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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 16 15:04:52 2020
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2020-09-05 (11 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200905)
  ProcCmdline: totem DSCF0010.AVI
  SegvAnalysis:
   Segfault happened at: 0x7fdf99b96cd8:mov0x8(%rax),%rcx
   PC (0x7fdf99b96cd8) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libtotem.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: totem crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1895837/+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.

[Apport retracing service]

** Tags added: 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/1895897

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

Status in xorg-server package in Ubuntu:
  New

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 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895897/+subscriptions

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

[Desktop-packages] [Bug 1844627] Re: gnome-shell crashed with SIGSEGV after updating eoan VM and rebooting

[Apport retracing service]

** Tags added: 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/1844627

Title:
  gnome-shell crashed with SIGSEGV after updating eoan VM and rebooting

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I updated my eoan VM to get the latest updates, then rebooted, and
  upon login gnome-shell crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 19 09:23:31 2019
  Disassembly: => 0x7f8bad4cd3eb:   Cannot access memory at address 
0x7f8bad4cd3eb
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'mru-sources' b"[('xkb', 'fr+bepo'), 
('xkb', 'fr+oss')]"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'fr+bepo')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['update-manager', 'gnome-control-center', 'org-gnome-dejadup', 
'org-gnome-software', 'apport-gtk']"
  InstallationDate: Installed on 2018-08-21 (393 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f8bad4cd3eb:Cannot access memory at address 
0x7f8bad4cd3eb
   PC (0x7f8bad4cd3eb) ok
   SP (0x7ffe67129250) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f8bad4cd3eb in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffe67129250
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-05 (105 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

[Apport retracing service]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


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

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

** Tags removed: need-amd64-retrace

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

Title:
  orca crashed with signal 5 in _atspi_bus()

Status in orca package in Ubuntu:
  Invalid

Bug description:
  Testing Ubuntu MATE Groovy 20200810 build 'live session' test case.
  When launched, Orca did not start and received crash report screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: orca 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: MATE
  Date: Mon Aug 10 17:20:20 2020
  ExecutablePath: /usr/bin/orca
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200810)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/orca --replace
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  Signal: 5
  SourcePackage: orca
  StacktraceTop:
   _atspi_bus () from /lib/x86_64-linux-gnu/libatspi.so.0
   ?? () from /lib/x86_64-linux-gnu/libatspi.so.0
   _atspi_ref_accessible () from /lib/x86_64-linux-gnu/libatspi.so.0
   ?? () from /lib/x86_64-linux-gnu/libffi.so.7
   ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  Title: orca crashed with signal 5 in _atspi_bus()
  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/orca/+bug/1891067/+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 1681290] Re: UI experiences delay when menu / tooltip disappears

[Matt]

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

Bug 1181666 does not at all describe the issue we are having 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/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 1896931] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1898005, 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/1896931/+attachment/5413827/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1896931

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ...

  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
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 24 11:11:42 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=sv_SE.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/ubuntu/+source/gnome-shell/+bug/1896931/+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 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()

[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 system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1867480

Title:
  scp-dbus-service.py crashed with SIGSEGV in
  _PyObject_GC_UNTRACK_impl()

Status in System Config Printer:
  Fix Released
Status in python-cups package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  not sure what it is I just saw there was n bug - I am new to Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 15 02:22:17 2020
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  InterpreterPath: /usr/bin/python3.8
  Lpstat: device for L365: 
dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/
  MachineType: Universal Exports Group Limited ITL 1403-I3 128
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/L365.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x506f57:  mov%rcx,(%rdx)
   PC (0x00506f57) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so
   __nptl_deallocate_tsd () at pthread_create.c:301
   __nptl_deallocate_tsd () at pthread_create.c:256
   start_thread (arg=) at pthread_create.c:488
  Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 0429
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Default
  dmi.board.vendor: Default
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion:
  dmi.product.family: Notepad
  dmi.product.name: ITL 1403-I3 128
  dmi.product.sku: ITL 1403-I3 128
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Universal Exports Group Limited
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1867480/+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()

[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/1898471/+attachment/5417559/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1898471/+attachment/5417570/+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/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 1898671] Re: gnome-shell crashed with SIGABRT in __GI_raise()

[Apport retracing service]

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

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 #1898005, 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/1898671/+attachment/5418193/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1898671

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  oazisn@wcjongkoks:~$ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10
  oazisn@wcjongkoks:~$ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.38.0-1ubuntu2
Candidate: 3.38.0-1ubuntu2
Version table:
   *** 3.38.0-1ubuntu2 500
  500 http://id.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  oazisn@wcjongkoks:~$ 

  
  Honestly, I don't really know what happen. I was switch to ubuntu on wayland 
and open google chrome and everything freeze. I think gnome-shell is crashing. 
So it return tu gdm login 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-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  6 11:53:04 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-10-06 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898671/+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 1878715] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()

[Apport retracing service]

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

** This bug is no longer 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()
** This bug has been marked a duplicate of private bug 1898005

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  
  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.36.2-1ubuntu1
Candidate: 3.36.2-1ubuntu1
Version table:
   *** 3.36.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Shell crashed, and shouldn't have.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu34
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 18:04:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-30 (14 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
  Signal: 6
  SourcePackage: 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: Upgraded to groovy on 2020-05-14 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878715/+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

[Apport retracing service]

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

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 #1898005, 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/1898910/+attachment/5419011/+files/CoreDump.gz

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

-- 
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 1868017] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:st_bin_destroy

[Apport retracing service]

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

** This bug is no longer 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()
** This bug has been marked a duplicate of private bug 1898005

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:st_bin_destroy

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.35.91-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 
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/1868017/+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 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()

[Till Kamppeter]

python3-cups 2.0.1 is already in Groovy.

** Changed in: python-cups (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  scp-dbus-service.py crashed with SIGSEGV in
  _PyObject_GC_UNTRACK_impl()

Status in System Config Printer:
  Fix Released
Status in python-cups package in Ubuntu:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  not sure what it is I just saw there was n bug - I am new to Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 15 02:22:17 2020
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  InterpreterPath: /usr/bin/python3.8
  Lpstat: device for L365: 
dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/
  MachineType: Universal Exports Group Limited ITL 1403-I3 128
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/L365.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x506f57:  mov%rcx,(%rdx)
   PC (0x00506f57) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so
   __nptl_deallocate_tsd () at pthread_create.c:301
   __nptl_deallocate_tsd () at pthread_create.c:256
   start_thread (arg=) at pthread_create.c:488
  Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 0429
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Default
  dmi.board.vendor: Default
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion:
  dmi.product.family: Notepad
  dmi.product.name: ITL 1403-I3 128
  dmi.product.sku: ITL 1403-I3 128
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Universal Exports Group Limited
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1867480/+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 1898885] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1867763, 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/1898885/+attachment/5418956/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1867763
   gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: 
assertion failed: (priv->child == NULL)

** 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/1898885

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  went away from computer for 10 minutes and this welcomed me

  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  7 16:26:40 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=sv_SE.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/ubuntu/+source/gnome-shell/+bug/1898885/+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

[Coiby Xu]

@Piotr Tomaszewski (nfm886)

> Hey Coiby Xu (coiby),
> That's does not works. Manjaro Linux 5.8.11-1-MANJARO x86_64 20.1.1 Mikah
> and make ending up with error 2

> translated error is
> make [1]: *** No objects found and no makefile found. Stop

You should run make in the folder where you see "Makefile". After
unzipping the downloaded archive in #189, you should run make after
going into the child folder, i.e., "cd standone_pinctrl-amd" (sorry for
the typoin the name, I meant standalone_pinctrl-amd).

-- 
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: 

[Desktop-packages] [Bug 1896935] Re: gnome-shell crashed with SIGABRT in __GI_raise()

[Apport retracing service]

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

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 #1898005, 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/1896935/+attachment/5413847/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1896935

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ## What happened

  When fractional scaling is enabled in Settings -> Displays, gnome-
  shell crashed

  ### OS
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  ### Gnome Shell
  gnome-shell:
Installed: 3.38.0-1ubuntu2
Candidate: 3.38.0-1ubuntu2
Version table:
   *** 3.38.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  ## Expected

  gnome-shell to not crash

  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
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 24 12:38:51 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-09-23 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896935/+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

[Coiby Xu]

@PD (pd1986)
> If I am not misunderstanding, does it mean that only patch for pinctrl-amd.c 
> without changing i2c-hid-core.c should solve the problem?

Yes, you are right! Only commenting out one line of code in pinctrl-
amd.c would be sufficient for fixing this laptop model. But for now we
are not sure how will it affect other touchpads, so only use it for this
laptop.

-- 
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: 

[Desktop-packages] [Bug 1898106] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1898005, 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/1898106/+attachment/5416292/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1898106

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Again, I didn't see what happened here.

  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 12:00:18 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/1898106/+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 1898090] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1867763, 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/1898090/+attachment/5416256/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1867763
   gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: 
assertion failed: (priv->child == NULL)

** 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/1898090

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Believe this crash is related to bug 1897959 which has to do with the
  audio turning off at the same time the screen blanking timeout occurs.
  Was trying to reproduce that bug then this crash occurred.

  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: Wed Sep 30 15:10:10 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/cliff
  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/ubuntu/+source/gnome-shell/+bug/1898090/+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 1898895] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()

[Apport retracing service]

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

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 #1867763, 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/1898895/+attachment/5418977/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1867763
   gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: 
assertion failed: (priv->child == NULL)

** 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/1898895

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  started to crash after i've added to sources.list:
  deb http://de.archive.ubuntu.com/ubuntu groovy main universe restricted 
multiverse
  deb-src http://de.archive.ubuntu.com/ubuntu groovy main 

  how could i fix it?

  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-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  7 18:11:04 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-09-16 (21 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 6
  SourcePackage: 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/+bug/1898895/+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 1899056] Re: gnome-shell crashed with SIGABRT

[Apport retracing service]

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

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 #1898005, 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/1899056/+attachment/5419588/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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/1899056

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm on Ubuntu 20.10 - Groovy Gorilla (development branch)

  I was using Google Chrome (two tabs open and at first desktop) and
  Mozilla Firefox (one tab open), Anki and gedit (at second desktop)
  when I pressed (ALT + TAB) to switch between gedit and Firefox, it
  crashed and I had to login into my account again.

  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-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  8 13:01:36 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-09-14 (24 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt: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: Upgraded to groovy on 2020-09-18 (20 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/1899056/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost

[Launchpad Bug Tracker]

This bug was fixed in the package xorg - 1:7.7+19ubuntu15

---
xorg (1:7.7+19ubuntu15) groovy; urgency=medium

  * debian/local/Xsession.d/60x11-common_localhost: Dropped, it's
provided by 35x11-common_xhost-local now. (LP: #1576454)

 -- Timo Aaltonen   Fri, 09 Oct 2020 11:17:12 +0300

** Changed in: xorg (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Superfluous Xsession.d script: 60x11-common_localhost

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Both of these scripts do the same thing, and both are installed by
  x11-common:

  /etc/X11/Xsession.d/35x11-common_xhost-local
  /etc/X11/Xsession.d/60x11-common_localhost

  35x11-common_xhost-local is present in debian, while
  60x11-common_localhost is not. I suspect the latter should be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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

[Piotr Tomaszewski]

Hey Coiby Xu (coiby),
That's does not works. Manjaro Linux 5.8.11-1-MANJARO x86_64 20.1.1 Mikah 
and make ending up with error 2

translated error is 
make [1]: *** No objects found and no makefile found. Stop.

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

[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

[Dan Streetman]

ok, very sorry for my delay in looking at this.

a quick scan of the results for x/b/f show:

ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:00.893145-04:00'
88: boot-smoke   FAIL non-zero exit status 1
(amd64:87 arm64:1)
39: systemd-fsckdFAIL non-zero exit status 1
(amd64:39)
47: boot-and-servicesFAIL non-zero exit status 1
(amd64:41 arm64:6)
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r bionic -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:53:18.194358-04:00'
132: systemd-fsckdFAIL non-zero exit status 1
 (i386:14 amd64:117 ppc64el:1)
15: upstream FAIL non-zero exit status 1
(i386:3 amd64:10 ppc64el:1 arm64:1)
29: boot-smoke   FAIL non-zero exit status 1
(i386:2 amd64:27)
ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r focal -cv 
--since 2month --minimum 6
parsed '2month' as '2020-08-09T14:56:04.065710-04:00'
96: systemd-fsckdFAIL non-zero exit status 137
(amd64:68 ppc64el:20 s390x:8)
21: systemd-fsckdFAIL non-zero exit status 1
(amd64:1 ppc64el:4 s390x:16)


I think the systemd-fsckd failures are issues with how the test is
trying to detect 'good' and 'bad' service status, but in any case i
rewrote some of the details of how the test works to be simpler and
(hopefully) more accurate/reliable, I'm running it through tests from my
ppa now, before I upload the test change.

I'll take a look at the other test failures; the boot-and-services test
has typically had a lot of trouble with services randomly not starting
ok, but i'll check on the details.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in linux-meta package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Invalid
Status in linux-meta source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in build-essential source package in Focal:
  Confirmed
Status in linux-meta source package in Focal:
  New
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B 

[Desktop-packages] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

[Apport retracing service]

** Tags added: groovy

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("Couldn't add screen\n") from InitOutput()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashed with VS Code.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Feb 24 18:28:10 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3820]
  InstallationDate: Installed on 2018-02-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  MachineType: LENOVO 80NE
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 
-listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=0beb58c8-0bf5-4e01-95dd-ae78f4ce0dea ro quiet splash vt.handoff=1
  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:
   
  dmi.bios.date: 09/09/2015
  dmi.bios.vendor: Lenovo
  dmi.bios.version: BDCN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-14IBD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-14IBD
  dmi.modalias: 
dmi:bvnLenovo:bvrBDCN61WW:bd09/09/2015:svnLENOVO:pn80NE:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80NE
  dmi.product.version: Lenovo Yoga 500-14IBD
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751508/+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 1898800] 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/1898800/+attachment/5418616/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1898800/+attachment/5418635/+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/1898800

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After upgrading to groovy, on login apport appeared with this crash...

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.8-2ubuntu6
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Oct  7 01:27:01 2020
  DistUpgraded: 2020-10-07 01:17:30,292 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:225c]
  InstallationDate: Installed on 2019-11-18 (323 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20KHCTO1WW
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth 
/run/user/124/.mutter-Xwaylandauth.AQH7R0 -listen 4 -displayfd 5 -listen 6 
-extension SECURITY
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash psmouse.synaptics_intertouch=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   InitOutput ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (0 days ago)
  UserGroups: N/A
  dmi.bios.date: 06/03/2020
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET74W (1.49 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET74W(1.49):bd06/03/2020:br1.49:efr1.21:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  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.8-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.1.8-1
  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: 

[Desktop-packages] [Bug 1330232] Re: remmina opens then closes immesiately. Trying to connect win win 8 server. Has been working fine until 3 days ago. same problem on 2 seperate machines

[rukib shevek]

I had the same problem. Changing the color depth didn't help, but I kept
tinkering with the configurations. Eventually I removed the entry
"||explorer" from the "startup program" field in the "advanced" tab. It
worked like a charm immediately after that.

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

Title:
  remmina opens then closes immesiately. Trying to connect win win 8
  server. Has been working fine until 3 days ago. same problem on 2
  seperate machines

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  source package the bug is in : /usr/bin/remmina
  1 : Ubuntu 12.04
  2 : remmina-common 1.0.0-1ubuntu6.3
  3 : I expected to log into a remote desktop environment hosted on a Win8 
Server using RDP
  4 : It opens briefely then closes or freezes. Only when the security setting 
is set to "Negotiate" or "NLA" will I get that far. Using "RDP" or "TLA" I just 
get a window saying "Unable to connect to RDP server"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1330232/+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

[Apport retracing service]

** Tags added: need-amd64-retrace

-- 
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 1846299] Re: Xwayland crashed with SIGABRT in OsAbort()

[Apport retracing service]

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

** Tags added: 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/1846299

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Rocket League keeps on crashing. First it mixes up controller settings
  and after few secs game/graphics hangs completely that I have to press
  power button.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: xwayland 2:1.20.5+git20190820-0ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Oct  1 21:02:51 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:1091]
  InstallationDate: Installed on 2019-09-29 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_R504ZA
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth 
/run/user/124/.mutter-Xwaylandauth.39W18Z -listen 4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=babb7231-be77-4774-9855-b4cdc53faaad ro quiet splash vt.handoff=7
  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:
   
  dmi.bios.date: 05/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505ZA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505ZA
  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.:bvrX505ZA.311:bd05/21/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_R504ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUS Laptop X505ZA_R504ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  separator:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846299/+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 1867480] Re: scp-dbus-service.py crashed with SIGSEGV in _PyObject_GC_UNTRACK_impl()

[Apport retracing service]

** Tags added: need-amd64-retrace

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

Title:
  scp-dbus-service.py crashed with SIGSEGV in
  _PyObject_GC_UNTRACK_impl()

Status in System Config Printer:
  Fix Released
Status in python-cups package in Ubuntu:
  Triaged
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  not sure what it is I just saw there was n bug - I am new to Linux

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Mar 15 02:22:17 2020
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  InterpreterPath: /usr/bin/python3.8
  Lpstat: device for L365: 
dnssd://EPSON%20L365%20Series._pdl-datastream._tcp.local/
  MachineType: Universal Exports Group Limited ITL 1403-I3 128
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/L365.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/L365.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=464449a8-03b3-4536-9504-744640ef4b27 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x506f57:  mov%rcx,(%rdx)
   PC (0x00506f57) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so
   __nptl_deallocate_tsd () at pthread_create.c:301
   __nptl_deallocate_tsd () at pthread_create.c:256
   start_thread (arg=) at pthread_create.c:488
  Title: scp-dbus-service.py crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 0429
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Default
  dmi.board.vendor: Default
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr0429:bd04/29/2019:svnUniversalExportsGroupLimited:pnITL1403-I3128:pvrTBDbyOEM:rvnDefault:rnDefault:rvrType2-BoardVersion:cvnChassisManufacture:ct10:cvrChassisVersion:
  dmi.product.family: Notepad
  dmi.product.name: ITL 1403-I3 128
  dmi.product.sku: ITL 1403-I3 128
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Universal Exports Group Limited
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1867480/+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 1893168] Re: groovy gnome-shell crash

[Apport retracing service]

** Tags added: 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/1893168

Title:
  groovy gnome-shell crash

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  How I produced the crash:
  * sudo service gdm3 stop
  * launch Xorg as root
  * open another tty
  * export DISPLAY=:0
  * gnome-shell
  * CTRL-ALT-F1 to see gnome-shell, all I see is the mouse cursor blinks over a 
black background then stops blinking
  * when I go back to the previous terminal I see:

  $ gnome-shell
  Segmentation fault (core dumped)

  Restarting gdm3 doesn't produce the crash file but only produces a
  black screen with mouse pointer blinking initially.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu2~build1
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Aug 27 12:19:38 2020
  DisplayManager:
   
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1597769943
  GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport
  InstallationDate: Installed on 2015-09-28 (1794 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: gnome-shell
  ProcCwd: /root
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_PH:en
   LANG=en_PH.UTF-8
   TERM=linux
   PATH=(custom, no user)
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2
  SegvAnalysis: Skipped: missing required field "Disassembly"
  ShellJournal:
   -- Logs begin at Thu 2020-08-27 11:28:20 PST, end at Thu 2020-08-27 12:20:01 
PST. --
   -- No entries --
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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

[Apport retracing service]

** Tags added: 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/1846330

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  When RAM is full gnome-shell crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 14:38:01 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-02-12 (232 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fe3394e0d24:lock addl $0x1,(%rax)
   PC (0x7fe3394e0d24) ok
   source "$0x1" ok
   destination "(%rax)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846330/+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 1836070] Re: seahorse crashed with signal 5

[Apport retracing service]

** Tags added: need-amd64-retrace

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

Title:
  seahorse crashed with signal 5

Status in seahorse package in Ubuntu:
  Invalid

Bug description:
  I just opened the application and it froze.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: seahorse 3.32-1
  Uname: Linux 5.2.0-050200rc7-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 10 10:17:19 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2018-12-02 (219 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
  Signal: 5
  SourcePackage: seahorse
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XGetRequest () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XShmCreatePixmap () at /usr/lib/x86_64-linux-gnu/libXext.so.6
  Title: seahorse crashed with signal 5
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (219 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1836070/+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 1842204] Re: gnome-control-center crashed with SIGABRT in raise()

[Apport retracing service]

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

** Tags added: 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/1842204

Title:
  gnome-control-center crashed with SIGABRT in raise()

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

Bug description:
  Error will appear if I launch gnome-control-center by root

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  1 12:47:01 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-09-01 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830)
  ProcCmdline: gnome-control-center
  Signal: 6
  SourcePackage: gnome-control-center
  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
   cc_shell_model_set_panel_visibility ()
   ?? ()
   cc_wifi_panel_static_init_func ()
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842204/+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

[Shatakhtsyan Artem]

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

This is also happening with my JBL TUNE120TWS on Ubuntu 20.04.1
Can not switch to HFP/HSP profile in a GUI-settings menu.
Sound works fine, but have nothing to pick up from in the list of inputs.
Hope this could help.

-- 
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 1876219] Re: iris driver for old cpu

[Sebastian Ramacher]

Broken driver or invalid driver selection is nothing we can fix in vlc.

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

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

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in ring package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1876219/+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 1876219] Re: iris driver for old cpu

[Adrien Béraud]

** Bug watch added: git.jami.net/savoirfairelinux/ring-daemon/issues #264
   https://git.jami.net/savoirfairelinux/ring-daemon/issues/264

** Also affects: mesa via
   https://git.jami.net/savoirfairelinux/ring-daemon/issues/264
   Importance: Unknown
   Status: Unknown

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

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

** Changed in: mesa
   Importance: Unknown => Undecided

** Changed in: mesa
   Status: Unknown => New

** Changed in: mesa
 Remote watch: git.jami.net/savoirfairelinux/ring-daemon/issues #264 => None

** Changed in: mesa
   Status: New => Confirmed

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

Title:
  iris driver for old cpu

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in ring package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  New

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1876219/+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 1899188] [NEW] erratic behavior when trying to select files in large folders

[Georg Baker]

Public bug reported:

I have several folders with as many as 5000 files. When I open one of
these folders and then scroll down to the file I wish to work on (for
this purpose rename) I left click on the file and nautilus jumps up to
the top and selects a random file near to top of the column the original
file was in. When I scroll down to the original file, it is outlined. If
I try right clicking on the outlined file it jumps back up to the
randomly select file and displays the menu of actions I wish,
unfortunately on the randomly selected file not the original file I
tried to select. after playing with the speed of clicking and double
clicking I was able to get the needed file selected but when I right
clicked to bring up the action menu it jumped back up towards the top of
that column and selected another file. No matter what I try I can't
rename the file I want to if it is down several scrolls below the
original screen when nautilus is invoked.

After playing around with this the behavior explained above happens on
smaller folders as well.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
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: Fri Oct  9 11:30:20 2020
InstallationDate: Installed on 2016-05-01 (1622 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  erratic behavior when trying to select files in large folders

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have several folders with as many as 5000 files. When I open one of
  these folders and then scroll down to the file I wish to work on (for
  this purpose rename) I left click on the file and nautilus jumps up to
  the top and selects a random file near to top of the column the
  original file was in. When I scroll down to the original file, it is
  outlined. If I try right clicking on the outlined file it jumps back
  up to the randomly select file and displays the menu of actions I
  wish, unfortunately on the randomly selected file not the original
  file I tried to select. after playing with the speed of clicking and
  double clicking I was able to get the needed file selected but when I
  right clicked to bring up the action menu it jumped back up towards
  the top of that column and selected another file. No matter what I try
  I can't rename the file I want to if it is down several scrolls below
  the original screen when nautilus is invoked.

  After playing around with this the behavior explained above happens on
  smaller folders as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  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: Fri Oct  9 11:30:20 2020
  InstallationDate: Installed on 2016-05-01 (1622 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899188/+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 1899147] Re: gnome-terminal drops display scaling on new tab creation

[Pavel Vasilyev]

Doing `gsettings set org.gnome.desktop.interface scaling-factor 2` helps
to keep the display scaling, but it anyway tries to re-scale every time
I open a new tab or start new terminal session.

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

Title:
  gnome-terminal drops display scaling on new tab creation

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In my setup I have Ubuntu 20.04 running in VirtualBox on Windows. I
  connect to the Windows machine through Microsoft Remote Desktop from
  Macbook Pro with Retina Display:

  Mac OS Catalina -- (RDP) --> Windows 10 -- (VirtualBox) --> Ubuntu
  20.04 -> gnome-terminal

  Since it is retina display, Windows does rescaling. In Ubuntu I have
  to go to Settings -> Display and set Scale to 200%. I had opened
  gnome-terminal before, so I just press Ctrl-Shift-T to create a new
  tab.

  After opening a new tab, the display scaling drops to a default value
  which is 100%. Same can be reproduced if I run tmux session in the
  gnome-terminal.

  So, whenever I try to open a new tab, the display scaling restores to
  100%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1899147/+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 1896316] Re: tracker-extract crashed with signal 31 in statx()

[Sebastien Bacher]

the issue is fixed now in the update
https://launchpad.net/ubuntu/+source/tracker-miners/2.3.5-1

** Changed in: tracker-miners (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  tracker-extract crashed with signal 31 in statx()

Status in tracker-miners package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 20.10

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: tracker-extract 2.3.3-2build1
  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
  CurrentDesktop: KDE
  Date: Sat Sep 19 10:36:18 2020
  ExecutablePath: /usr/libexec/tracker-extract
  InstallationDate: Installed on 2020-05-21 (120 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200521)
  ProcCmdline: /usr/libexec/tracker-extract
  ProcEnviron:
   LANG=de_CH.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 31
  SourcePackage: tracker-miners
  StacktraceTop:
   statx (fd=-100, path=0x7fd6b401cd10 "/home/username/Downloads/Jenevieve - 
Baby Powder (Official Video).mp3", flags=2304, mask=4095, buf=0x7fd6c9727580) 
at ../sysdeps/unix/sysv/linux/statx.c:29
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   tracker_file_get_size () from 
/usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-mp3.so
   tracker_extract_get_metadata () from 
/usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-mp3.so
  Title: tracker-extract crashed with signal 31 in statx()
  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/tracker-miners/+bug/1896316/+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 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts

[Jean-]

I was referred here by Gunnar Hjalmarsson following a question on
askubuntu [1] regarding incorrect layout for hotkeys in at least
intellij idea and vscode.


In both cases, hotkeys seem to be pinned to the layout corresponding to the 
first input source declared in the gnome Language and Region settings. 
For shortcuts ( and for shortcuts only which makes it really painful) the 
layout doesn't change but normal typing is correctly remapped.

I have read through this thread but am still unsure if the issue is 
- in ubuntu/gnome/linux
- in the apps themselves
- in my own configuration

What I observe :
- setup an azerty layout then a qwerty layout (both are latin compatible)
- in azerty text typing and hotkeys behave as expected in vscode and intellij 
- in qwerty text typing behaves correctly but hotkeys are still mapped to the 
physical keys they would be bound to in the azerty layout
- reverse azerty and qwerty in gnome settings
- in qwerty text typing and hotkeys behave as expected in vscode and intellij 
- in azerty text typing behaves correctly but hotkeys are still mapped to the 
physical keys they  
would be bound to in the qwerty layout
  

What I expect : 
- setup an azerty layout then a qwerty layout (both are latin compatible)
- in azerty text typing and hotkeys are bound to azerty keys both in vscode and 
intellij 
- in qwerty text typing and hotkeys are bound to qwerty keys both in vscode and 
intellij
- reverse azerty and qwerty in gnome settings
- in azerty text typing and hotkeys are bound to azerty keys both in vscode and 
intellij 
- in qwerty text typing and hotkeys are bound to qwerty keys both in vscode and 
intellij

I tried various combinations of configurations at various layers to try
and make this work to no avail for now. my latest config state is in the
askubuntu post

[1] https://askubuntu.com/questions/1281251/keyboard-shortcuts-do-not-
honor-selected-input-source-in-some-apps

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

Title:
  Keyboard shortcuts (hotkeys) not functional in some cases in non-latin
  keyboard layouts

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  Fix Released
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in Mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in kdevelop package in Ubuntu:
  Confirmed
Status in mc package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in terminator package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in gnome-terminal source package in Xenial:
  Triaged
Status in kdevelop source package in Xenial:
  Confirmed
Status in mc source package in Xenial:
  Confirmed
Status in openjdk-7 source package in Xenial:
  Incomplete
Status in terminator source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  In Progress
Status in gnome-shell package in Fedora:
  Won't Fix
Status in openoffice package in Fedora:
  Won't Fix

Bug description:
  Keyboard shortcuts are key combinations like Alt+F (usually opens the
  File menu) and Ctrl+O (usually opens the File→Open... dialog box).

  There is an issue with non-latin keyboard layouts that the keys under F or O 
(for Alt+F and Ctrl+O respectively) would correspond to some other character.
  What should happen then? There is some smart functionality (at least in the 
GTK+ library) that when we press a shortcut, it will try to make Alt+F or 
Ctrl+O work, even if the active keyboard layout is not English.

  For this smart functionality to work, it requires us to have as first 
keyboard layout the English (en) layout. Then, GTK+ will be able to
  check whether the shortcut makes sense for English, and if so, will run it.
  All that even if the active layout is Greek or Russian or something else. 

  This report has over 300 comments and these comments include all sort of 
corner cases that indeed shortcuts do not work. In general, shortcuts work,
  but in specific cases there are issues that need to be fixed.

  What we need to do, is collect those corner cases and create new
  separate reports.

  Here are the corner cases:

  1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, 
Russian), but they do not work for Super+A/F/M/C/V. 
  Report: 

  2. Java 

[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

[Kopa Rebu]

Hi,

Today I could install the new mutter version in my computer, and it
seems this problem got fixed.

Here the details:

> $ apt-cache policy mutter
> mutter:
>   Installed: 3.36.6-1ubuntu0.20.04.2
>   Candidate: 3.36.6-1ubuntu0.20.04.2
>   ...

Thanks!

-- 
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:
  Incomplete

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 1899184] [NEW] CPU spikes and system hangs from gnome-shell every 5-10 seconds

[Radon Rosborough]

Public bug reported:

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)

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


** Tags: amd64 apport-bug focal

** Description changed:

  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
+ 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
+ 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 

[Desktop-packages] [Bug 1899184] Re: CPU spikes and system hangs from gnome-shell every 5-10 seconds

[Radon Rosborough]

Reattached GsettingsChanges.txt since the apport version contained
private information.

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899184/+attachment/5419988/+files/GsettingsChanges.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/1899184

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

Status in gnome-shell package in Ubuntu:
  New

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 1616332] Re: gnome-software using hundreds of MB of memory when not in use

[J. Greg Mackinnon]

I also can confirm that this issue persists in Ubuntu 20.04 (focal).
It's pretty irritating... it's bad enough that all of these Electron-
based apps and chromium-based browsers are chewing up ~400-500Mb each.
I don't need a silly software management UI doing it, too!

I recognize that gnome-software may not be a default-installed package on 
Ubuntu 20.04, but it 
still is widely used (I have several Flatpaks I need for work, and 
gnome-software offers the ability to easily install and coordinate their 
updates).  Can't some developers at Red Hat and Canonical put their heads 
together for a few minutes and get this corrected, please?

I also will second Meluco's comment.  We should not all have to buy new
32Gb laptops just to run a simple productivity workstation.

This really needs to get corrected.  I am seeing reports of memory leaks
in gnome-software going back as far as Ubuntu 16.04.

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+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 1899156] Re: VPN through Network Manager GUI with Pulse Connect Secure host name problem

[Brian Murray]

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  VPN through Network Manager GUI with Pulse Connect Secure host name
  problem

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release version: Ubuntu 20.04.1 LTS
  Version of network-manager-openconnect: 1.2.6-1
  Version of openconnect: 8.05-1

  VPN connection created through Network Manager GUI with VPN Protocol: Pulse 
Connect Secure converts gateway host name to IP when making a connection. It 
results in getting HTTP 404 error in NetworkManager.service logs because of 
failed SSL certificate validation. Screenshot attached.
  Gateway in Network Manager GUI is in URL format: https://xxx

  When using openconnect command: sudo openconnect --protocol=pulse
  https://xxx all works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1899156/+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 1899156] [NEW] VPN through Network Manager GUI with Pulse Connect Secure host name problem

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Release version: Ubuntu 20.04.1 LTS
Version of network-manager-openconnect: 1.2.6-1
Version of openconnect: 8.05-1

VPN connection created through Network Manager GUI with VPN Protocol: Pulse 
Connect Secure converts gateway host name to IP when making a connection. It 
results in getting HTTP 404 error in NetworkManager.service logs because of 
failed SSL certificate validation. Screenshot attached.
Gateway in Network Manager GUI is in URL format: https://xxx

When using openconnect command: sudo openconnect --protocol=pulse
https://xxx all works fine.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
VPN through Network Manager GUI with Pulse Connect Secure host name problem
https://bugs.launchpad.net/bugs/1899156
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager 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 1899147] Re: gnome-terminal drops display scaling on new tab creation

[Brian Murray]

** Package changed: ubuntu => gnome-terminal (Ubuntu)

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

Title:
  gnome-terminal drops display scaling on new tab creation

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In my setup I have Ubuntu 20.04 running in VirtualBox on Windows. I
  connect to the Windows machine through Microsoft Remote Desktop from
  Macbook Pro with Retina Display:

  Mac OS Catalina -- (RDP) --> Windows 10 -- (VirtualBox) --> Ubuntu
  20.04 -> gnome-terminal

  Since it is retina display, Windows does rescaling. In Ubuntu I have
  to go to Settings -> Display and set Scale to 200%. I had opened
  gnome-terminal before, so I just press Ctrl-Shift-T to create a new
  tab.

  After opening a new tab, the display scaling drops to a default value
  which is 100%. Same can be reproduced if I run tmux session in the
  gnome-terminal.

  So, whenever I try to open a new tab, the display scaling restores to
  100%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1899147/+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 1871471] Re: flash end of life soon, suggest remove from groovy

[Gunnar Hjalmarsson]

On 2020-10-09 16:15, Steve Langasek wrote:
> flashplugin-nonfree, at least, has been removed from Debian, and we
> have now followed this removal for groovy.

It's not the same package. The Ubuntu variant, unlike Debian's, builds
flashplugin-installer which depends on adobe-flashplugin.

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

Title:
  flash end of life soon, suggest remove from groovy

Status in adobe-flashplugin package in Ubuntu:
  New
Status in flashplugin-nonfree package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Hello, Adobe has said they will not be supporting Flash beyond 2020:

  https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html
  https://theblog.adobe.com/adobe-flash-update/

  I think we shouldn't ship Flash in groovy. Does our agreement with
  Adobe for distributing Flash installers or code allow us to skip
  shipping Flash in groovy?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+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 1899147] [NEW] gnome-terminal drops display scaling on new tab creation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In my setup I have Ubuntu 20.04 running in VirtualBox on Windows. I
connect to the Windows machine through Microsoft Remote Desktop from
Macbook Pro with Retina Display:

Mac OS Catalina -- (RDP) --> Windows 10 -- (VirtualBox) --> Ubuntu 20.04
-> gnome-terminal

Since it is retina display, Windows does rescaling. In Ubuntu I have to
go to Settings -> Display and set Scale to 200%. I had opened gnome-
terminal before, so I just press Ctrl-Shift-T to create a new tab.

After opening a new tab, the display scaling drops to a default value
which is 100%. Same can be reproduced if I run tmux session in the
gnome-terminal.

So, whenever I try to open a new tab, the display scaling restores to
100%.

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


** Tags: bot-comment
-- 
gnome-terminal drops display scaling on new tab creation
https://bugs.launchpad.net/bugs/1899147
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-terminal 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 1899179] [NEW] autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3

[Balint Reczey]

Public bug reported:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/x/xdg-desktop-
portal/20200921_121654_3c330@/log.gz

autopkgtest [12:16:41]: test gnome-desktop-testing: [---
Running test: xdg-desktop-portal/testdb.test
# random seed: R02Sa8a2f882d5b075ef4489c354fb44d94b
1..3
# Start of db tests
ok 1 /db/open
ok 2 /db/serialize
ok 3 /db/modify
# End of db tests
PASS: xdg-desktop-portal/testdb.test
Running test: xdg-desktop-portal/test-doc-portal.test
# random seed: R02S8cb58d429c0a974cbecf54d1746d684e
outdir: /tmp/xdp-test-Q3WHR0
dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service 
name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1000 pid=1200 
comm="/usr/libexec/installed-tests/xdg-desktop-portal/te" label="unconfined")
dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service 
name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.1' 
(uid=1000 pid=1207 comm="/usr/libexec/xdg-document-portal " label="unconfined")
dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 
'org.freedesktop.impl.portal.PermissionStore'
dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 
'org.freedesktop.portal.Documents'
1..4
# Start of db tests
ok 1 /db/create_doc
path: /tmp/xdp-test-Q3WHR0/doc/387dfbb5/recursive-file
ok 2 /db/recursive_doc
ok 3 /db/create_docs
**
xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion 
failed (error == NULL): Can't open 
/tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23)
Bail out! xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: 
assertion failed (error == NULL): Can't open 
/tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23)
cleaning up pid 1202
FAIL: xdg-desktop-portal/test-doc-portal.test (Child process killed by signal 6)
SUMMARY: total=2; passed=1; skipped=0; failed=1; user=0.0s; system=0.0s; 
maxrss=9600
autopkgtest [12:16:42]: test gnome-desktop-testing: ---]
autopkgtest [12:16:42]: test gnome-desktop-testing:  - - - - - - - - - - 
results - - - - - - - - - -
gnome-desktop-testing FAIL non-zero exit status 2

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: xdg-desktop-portal (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: xdg-desktop-portal (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released


** Tags: update-excuse-bionic

** Summary changed:

- autopkgtest fails in bionic (almost always) starting with 1.0.3
+ autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3

** Also affects: xdg-desktop-portal (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: xdg-desktop-portal (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Fix Released

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

Title:
  autopkgtest (almost always) fails in bionic on ppc64el starting with
  1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Bionic:
  New
Status in xdg-desktop-portal source package in Focal:
  Fix Released

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-bionic/bionic/ppc64el/x/xdg-desktop-
  portal/20200921_121654_3c330@/log.gz

  autopkgtest [12:16:41]: test gnome-desktop-testing: [---
  Running test: xdg-desktop-portal/testdb.test
  # random seed: R02Sa8a2f882d5b075ef4489c354fb44d94b
  1..3
  # Start of db tests
  ok 1 /db/open
  ok 2 /db/serialize
  ok 3 /db/modify
  # End of db tests
  PASS: xdg-desktop-portal/testdb.test
  Running test: xdg-desktop-portal/test-doc-portal.test
  # random seed: R02S8cb58d429c0a974cbecf54d1746d684e
  outdir: /tmp/xdp-test-Q3WHR0
  dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service 
name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1000 pid=1200 
comm="/usr/libexec/installed-tests/xdg-desktop-portal/te" label="unconfined")
  dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service 
name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.1' 
(uid=1000 pid=1207 comm="/usr/libexec/xdg-document-portal " label="unconfined")
  dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 
'org.freedesktop.impl.portal.PermissionStore'
  dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 
'org.freedesktop.portal.Documents'
  1..4
  # Start of db tests
  ok 1 /db/create_doc
  path: 

[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3

[Balint Reczey]

I've filed LP: #1899179 for the autopkgtest failure on Bionic

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

Title:
  SRU xdg-desktop-portal 1.0.3

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Xenial:
  Fix Released
Status in xdg-desktop-portal source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * To improve the snap experience on the desktop we have been working with 
xdg-desktop-portal upstream to enable snap support.  Portals will greatly 
improve the snap experience.  Full snap support landed in xdg-desktop-portal 
1.0.  We're SRU'ing 1.0.3 as it includes bug fixes.
   
   * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, 
so these will be promoted to main as well.
   
   https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672
   

  [Test Case]

   * This can be tested by installing the portal-test snap from the edge
  channel and xdg-desktop-portal-gtk also from proposed.  Verify the
  file selection lets you select a file and open local opens test.txt in
  a text editor of your choice.

  [Regression Potential]

   * No regression potential.  This package was not seeded by default.  It 
could only have been used by flatpak, however, the version in bionic had 
limited functionality.  The package was never available in xenial.
   
  [Other Info]
   
   * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and 
disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+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 1871471] Re: flash end of life soon, suggest remove from groovy

[Steve Langasek]

flashplugin-nonfree, at least, has been removed from Debian, and we have
now followed this removal for groovy.

Removing packages:
flashplugin-nonfree 32.0.0.414ubuntu1 in groovy
flashplugin-installer 32.0.0.414ubuntu1 in groovy amd64
Comment: (From Debian) RoQA, unmainained, several RC bugs, techology 
deprecated; Debian bug #969112


** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Fix Released

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

Title:
  flash end of life soon, suggest remove from groovy

Status in adobe-flashplugin package in Ubuntu:
  New
Status in flashplugin-nonfree package in Ubuntu:
  Fix Released
Status in pepperflashplugin-nonfree package in Ubuntu:
  New

Bug description:
  Hello, Adobe has said they will not be supporting Flash beyond 2020:

  https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html
  https://theblog.adobe.com/adobe-flash-update/

  I think we shouldn't ship Flash in groovy. Does our agreement with
  Adobe for distributing Flash installers or code allow us to skip
  shipping Flash in groovy?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+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 1899172] [NEW] Cannot join an external screen and the screen of the labtop

[DESBIOLLES Pierre]

Public bug reported:

I can use either the labtop screen OR the DELL external screen but I
cannot join the two screens, as it was possible (and very easy) with
Ubuntu 16.04. It did not work with 18.04, it does not work with 20.04.
It is very frustrating since it works when I start the computer, I can
see the "Ubuntu" word on both the screens, but after I enter my password
I can use only one of the screen (I change from "parameters").

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-session-utils 7.7+4
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 non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct  9 15:20:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
InstallationDate: Installed on 2020-10-09 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Latitude E4300
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=bb032965-73b6-4d9f-b40a-5f7813dbb097 ro quiet splash
SourcePackage: x11-session-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0D201R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/22/2009:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D201R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4300
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

** Affects: x11-session-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Cannot join an external screen and the screen of the labtop

Status in x11-session-utils package in Ubuntu:
  New

Bug description:
  I can use either the labtop screen OR the DELL external screen but I
  cannot join the two screens, as it was possible (and very easy) with
  Ubuntu 16.04. It did not work with 18.04, it does not work with 20.04.
  It is very frustrating since it works when I start the computer, I can
  see the "Ubuntu" word on both the screens, but after I enter my
  password I can use only one of the screen (I change from
  "parameters").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-session-utils 7.7+4
  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 non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  9 15:20:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:024d]
  InstallationDate: Installed on 2020-10-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E4300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=bb032965-73b6-4d9f-b40a-5f7813dbb097 ro quiet splash
  SourcePackage: x11-session-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0D201R
  dmi.board.vendor: Dell 

[Desktop-packages] [Bug 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name

[Gunnar Hjalmarsson]

Thanks for your report!

I could reproduce the problem and have uploaded a fix.

** Information type changed from Private to Public

** Package changed: language-selector (Ubuntu) => accountsservice
(Ubuntu)

** Changed in: accountsservice (Ubuntu)
   Status: New => Fix Committed

** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  gnome-language-selector crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is
  not a valid locale name

Status in accountsservice package in Ubuntu:
  Fix Committed

Bug description:
  USB live disk (20.04 beta)

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: language-selector-gnome 0.203
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  CurrentDesktop: MATE
  Date: Sun Apr 19 17:07:26 2020
  ExecutablePath: /usr/bin/gnome-language-selector
  InterpreterPath: /usr/bin/python3.8
  LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonArgs: ['/usr/bin/gnome-language-selector']
  PythonDetails: N/A
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a 
valid locale name
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+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 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors

[AaronMa]

Updated to xserver-xorg-core:amd64 (2:1.19.6-1ubuntu4.6,
2:1.19.6-1ubuntu4.7)

Stock Bionic got multiple resolutions to set.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Only timing mode list in EDID supported on continuous freq monitors

Status in HWE Next:
  New
Status in X.Org X server:
  New
Status in xf86-video-intel:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  [Impact]
  Some new laptop display set EDID continuous freq bit 1.
  Then Xorg only uses the timing modes defined in EDID, no other modes are 
shown on Xorg.

  Upstream Bug:
  https://gitlab.freedesktop.org/drm/intel/-/issues/313

  Fix of Xorg in merge request:
  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

  
https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

  this is required to support new laptop models which use such panels

  [Test case]
  Test that a proper list of modes is shown with a panel that uses the new EDID.

  [Regression potential]
  The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883497/+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 1898416] Re: Wine failed to install

[Launchpad Bug Tracker]

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

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

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

Title:
  Wine failed to install

Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 20.04
  Tried to download wine from store, download failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libvdpau1 (not installed)
  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
  CompositorRunning: None
  Date: Sun Oct  4 18:32:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libvdpau1:(not installed)
   Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-rmJMEd/144-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different 
from other instances of package libvdpau1:amd64
  ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is 
different from other instances of package libvdpau1:amd64
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon 
Vega Series / Radeon Vega Mobile Series] [1462:7a40]
  MachineType: Micro-Star International Co., Ltd. MS-7A40
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=c257c1a8-59c6-4967-add4-929a999d1246 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libvdpau
  Title: package libvdpau1 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other 
instances of package libvdpau1:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450I GAMING PLUS AC (MS-7A40)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.70:bd07/10/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A40
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  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/libvdpau/+bug/1898416/+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 1351527] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

[nilandenterprise]

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

Mine is version Ubuntu 14.04.5 with gnome desk-top. and the crash report 
indicates nautilus 1:3.10.1 0ubutntu 9.11
Where do I find the report sent to add it here? dose not seem to be in /var/log 
or /var/crash?

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

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu12
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Aug  1 21:21:22 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-04-27 (96 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x479e69:  cmp%rax,(%rdx)
   PC (0x00479e69) ok
   source "%rax" ok
   destination "(%rdx)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

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

[Launchpad Bug Tracker]

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

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

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

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

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu12
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Aug  1 21:21:22 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-04-27 (96 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x479e69:  cmp%rax,(%rdx)
   PC (0x00479e69) ok
   source "%rax" ok
   destination "(%rdx)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1351527/+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

[PD]

If I am not misunderstanding...

-- 
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: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 

[Desktop-packages] [Bug 1899152] [NEW] Resolution not set or inappropriate

[SatishVSS]

Public bug reported:

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

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


** Tags: amd64 apport-bug focal resolution 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/1899152

Title:
  Resolution not set or inappropriate

Status in xorg package in Ubuntu:
  New

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
  

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[PD]

I am not misunderstanding, does it mean that only patch for pinctrl-
amd.c without changing i2c-hid-core.c should solve the problem?

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

[Desktop-packages] [Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c

[Hui Wang]

@YC,

This SRU is not to fix the 3 profiles in the combo list, it is to fix
the issue of "no active profile in the combo list" after plugging the
hdmi/dp monitor.

Without this SRU, after users plug a hdmi/dp monitor, the profile combo
list is empty, need users manually to select profile from 3 ones.

After the SRU, an active profile will be shown automatically in the
combo list after users plug a hdmi/dp monitor, no need users to manually
select the profile, but there are still 3 profile options in the combo
list. This is same as the 18.04.

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

Title:
  [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the
  combo list after selecting the hdmi/dp audio in the g-c-c

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  After we plugging a hdmi/dp monitor with audio capability, we could
  select hdmi audio as output device in the g-c-c, but after we do
  that, the profile combo list will show up in the g-c-c and this combo
  list is empty, it should be stereo-hdmi by default according to 18.04

  [Fix]
  Backport a fix from g-c-c upstream, after applying this patch, the
  combo list update signals will be recevied after the pa finishes the
  changing active profile.

  [Test Case]
  Plug the hdmi/dp monitor with audio capability, then choose hdmi audio
  as active output device from g-c-c, we will find the profile combo list
  has hdmi-steoreo as the default profile. This is same as 18.04.

  [Regression Risk]
  It is possible to make the output and input device can't work after
  applying this patch, that is because the active profile is not set as
  our expected. But this possibility is very low, I tested this patch on
  2 lenovo and 2 dell laptops, there is no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1896919/+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 1898138] Re: Desktop doesn't populate

[Bill Farina]

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

Additional information. By deactivating and reactivating Desktop Icons, the
icons appeared on my desktop.

Thank you


-Original Message-
From: boun...@canonical.com  On Behalf Of Daniel van
Vugt
Sent: Thursday, October 8, 2020 6:41 PM
To: bfar...@yahoo.com
Subject: [Bug 1898138] Re: Desktop doesn't populate 

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

No the 'Extensions' app is not part of Tweaks any more. Please don't use
Tweaks for that.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1898138

Title:
  Desktop doesn't populate

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

Bug description:
  Since the upgrade to 20.04, there are no icons on my desktop. When I
  try to drop a file to the desktop, I'm unable to and the file bounces
  back to it's original location.

  My desktop directory is still located in the user root directory and
  all the files that are supposed to be in it, are.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 18:52:15 2020
  InstallationDate: Installed on 2017-11-09 (1057 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
(20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-10-01 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-ico
ns/+bug/1898138/+subscriptions

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

Title:
  Desktop doesn't populate

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

Bug description:
  Since the upgrade to 20.04, there are no icons on my desktop. When I
  try to drop a file to the desktop, I'm unable to and the file bounces
  back to it's original location.

  My desktop directory is still located in the user root directory and
  all the files that are supposed to be in it, are.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 18:52:15 2020
  InstallationDate: Installed on 2017-11-09 (1057 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-10-01 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898138/+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 1898138] Re: Desktop doesn't populate

[Bill Farina]

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

Okay, found the Extensions App and Desktop Icons are enabled.

-Original Message-
From: boun...@canonical.com  On Behalf Of Daniel van
Vugt
Sent: Thursday, October 8, 2020 6:41 PM
To: bfar...@yahoo.com
Subject: [Bug 1898138] Re: Desktop doesn't populate 

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

No the 'Extensions' app is not part of Tweaks any more. Please don't use
Tweaks for that.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1898138

Title:
  Desktop doesn't populate

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

Bug description:
  Since the upgrade to 20.04, there are no icons on my desktop. When I
  try to drop a file to the desktop, I'm unable to and the file bounces
  back to it's original location.

  My desktop directory is still located in the user root directory and
  all the files that are supposed to be in it, are.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 18:52:15 2020
  InstallationDate: Installed on 2017-11-09 (1057 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
(20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-10-01 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-ico
ns/+bug/1898138/+subscriptions

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

Title:
  Desktop doesn't populate

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

Bug description:
  Since the upgrade to 20.04, there are no icons on my desktop. When I
  try to drop a file to the desktop, I'm unable to and the file bounces
  back to it's original location.

  My desktop directory is still located in the user root directory and
  all the files that are supposed to be in it, are.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  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
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  1 18:52:15 2020
  InstallationDate: Installed on 2017-11-09 (1057 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-10-01 (0 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898138/+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 1576454] Re: Superfluous Xsession.d script: 60x11-common_localhost

[Timo Aaltonen]

fixed in git now

** Changed in: xorg (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Superfluous Xsession.d script: 60x11-common_localhost

Status in xorg package in Ubuntu:
  In Progress

Bug description:
  Both of these scripts do the same thing, and both are installed by
  x11-common:

  /etc/X11/Xsession.d/35x11-common_xhost-local
  /etc/X11/Xsession.d/60x11-common_localhost

  35x11-common_xhost-local is present in debian, while
  60x11-common_localhost is not. I suspect the latter should be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576454/+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 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c

[Sebastien Bacher]

@Hui, could you check that verification failed comment, is that the same
issue than is addressed here or a different one, the 'three items'
description sounds a bit different

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

Title:
  [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the
  combo list after selecting the hdmi/dp audio in the g-c-c

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  After we plugging a hdmi/dp monitor with audio capability, we could
  select hdmi audio as output device in the g-c-c, but after we do
  that, the profile combo list will show up in the g-c-c and this combo
  list is empty, it should be stereo-hdmi by default according to 18.04

  [Fix]
  Backport a fix from g-c-c upstream, after applying this patch, the
  combo list update signals will be recevied after the pa finishes the
  changing active profile.

  [Test Case]
  Plug the hdmi/dp monitor with audio capability, then choose hdmi audio
  as active output device from g-c-c, we will find the profile combo list
  has hdmi-steoreo as the default profile. This is same as 18.04.

  [Regression Risk]
  It is possible to make the output and input device can't work after
  applying this patch, that is because the active profile is not set as
  our expected. But this possibility is very low, I tested this patch on
  2 lenovo and 2 dell laptops, there is no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1896919/+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 1898153] Re: screen locking doesn't work when using lightdm

[Daniel van Vugt]

Please merge this with the similar bugs like bug 1864982, bug 1853709,
bug 1812556 and more...

https://bugs.launchpad.net/ubuntu/+source/lightdm/+bugs?field.searchtext=lock

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

Title:
  screen locking doesn't work when using lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.  I think this issue also effects the shortcuts
  not working also.

  I'm using nemo as my file manager I followed these instructions below

  https://itsfoss.com/install-nemo-file-manager-ubuntu/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898153/+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 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Sebastien Bacher]

> `ubuntu-bug` requires a PID. '

it doesn't, see the manpage, you can also specify a package name as
argument

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as
  well, I haven't tested) causes fstab binds to appear as mounts in
  Nautilus (and in Deepin Dock - Deepin is based on Gnome).

  Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour.

  I first noted this bug behaviour here:
  https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049

  Details of my particular system and issue with what I tried to resolve
  it can be found here:
  https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030

  1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux.

   OS: Arch Linux 
   Kernel: x86_64 Linux 4.10.13-1-ARCH
   Shell: bash 4.4.12
   Resolution: 1920x1200
   DE: Deepin 15.4
   WM: Deepin WM
   WM Theme: Arc-Darker
   GTK Theme: Arc-Darker [GTK2/3]
   Icon Theme: deepin
   Font: Noto Sans 11
   CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C]
   GPU: GeForce GTX 950
   RAM: 2598MiB / 15990MiB

  2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the
  problem).

  3. Nautilus to list internal physical drives (my SSD and 1TB HDD)
  only.

  4. Nautilus listed my system disk (as expected) but also listed all of
  my fstab binds as removable drives (Downloads, Music, Pictures, Videos
  and Documents although this was not listed as "Documents" but instead
  listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide
  those drives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+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 1899089] Re: Ubuntu 20.04 file browser showing all zfs mounts explicitly in side-panel

[Sebastien Bacher]

Thank you for the bug report. Are those also listed in gtk's
fileselector dialog? (you can try to open a document on evince for
example)

It's weird that they are not listed by gio

Could you also include the output of 'mount'?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  Ubuntu 20.04 file browser showing all zfs mounts explicitly in side-
  panel

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have installed Ubuntu 20.04 on zfs. I had previously had zfs
  datasets mounted into my 18.04 system. Those mounts are all working in
  the new system, but they are displaying as mounts in my file browser
  with unmount buttons next to them. I certainly don't want this
  function. it is also cluttering my display. It appears similar to Bug
  1691908.

  My zfs mounts are not removable volumes, they are not in fstab.

  I was advised to report the output of `gio mount -li`:

  ```
  Volume(0): efi
Type: GUnixVolume
ids:
 uuid: '8799-8F8E'
themed icons:  [drive-removable-media]
symbolic themed icons:  [drive-removable-media-symbolic]
can_mount=1
can_eject=0
should_automount=1
Mount(0): efi -> file:///boot/efi
  Type: GUnixMount
  default_location=file:///boot/efi
  themed icons:  [drive-harddisk]
  symbolic themed icons:  [drive-harddisk-symbolic]
  can_unmount=1
  can_eject=0
  is_shadowed=0
  Mount(1): SPACE -> file:///media/peterg/SPACE
Type: GUnixMount
default_location=file:///media/peterg/SPACE
themed icons:  [drive-harddisk]
symbolic themed icons:  [drive-harddisk-symbolic]
can_unmount=1
can_eject=0
is_shadowed=0
  ```

  I tried Ask-Ubuntu. No answers at this time:
  
https://askubuntu.com/questions/1280941/ubuntu-20-04-file-browser-showing-all-zfs-mounts-explicitly-in-side-panel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct  9 08:41:22 2020
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-10-01 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201001)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899089/+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 1899041] Re: Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - patch available

[Sebastien Bacher]

** Changed in: wpa (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Gnome-Network-Displays chrashes with Intel Wireless AC due to
  wpasupplicant - patch available

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  When using Gnome-Network-Displays on a laptop with an Intel Wireless
  AC 9462/9560 card, wpasupplicant crashes. This reproducible bug can be
  fixed with this patch:

  
https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/

  A further description can be found here:

  https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899041/+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 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.

[Sebastien Bacher]

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

** Summary changed:

- I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go blank at 
the set time.
+ screen locking doesn't work when using lightdm

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

Title:
  screen locking doesn't work when using lightdm

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from 18.04 to 20.04.1 and  the screen doesn't lock or go
  blank at the set time.  I think this issue also effects the shortcuts
  not working also.

  I'm using nemo as my file manager I followed these instructions below

  https://itsfoss.com/install-nemo-file-manager-ubuntu/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898153/+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 1899025] Re: Thunderbird 78.3.2 snap translations issue during 1st launch after update

[Sebastien Bacher]

Thank you for your bug report, that's pretty weird since the
translations are included in the snap, unsure what could change between
the first start and the next one...

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Thunderbird 78.3.2 snap translations issue during 1st launch after
  update

Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I updated today from 78.3.1 to 78.3.2, after the first launch of the 
updated 78.3.2, I got some untranslated strings (Inbox in mailboxes folder 
list, e.g.).
  After the 2nd launch, all became normal.

  AFAICR, it was the case during previous updates too.
  Not a big deal, though...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+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 1866277] Re: Power Saving settings "Wi-Fi can be turned off to save power" does not work as advertised

[Sebastien Bacher]

Thank you for your bug report, that's a known gnome-control-center issue
due to confusing wording, details upstream on

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/681

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

** Changed in: gnome-power-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-power-manager (Ubuntu)
   Status: Confirmed => 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/1866277

Title:
  Power Saving settings "Wi-Fi can be turned off to save power" does not
  work as advertised

Status in gnome-power-manager package in Ubuntu:
  Invalid

Bug description:
  In Settings -> Power  under the "Power Saving" section, there are the
  following two on/off slider options:


  Wi-Fi
  Wi-Fi can be turned off to save power.

  Bluetooth
  Bluetooth can be turned off to save power.

  
  Rather than controlling something to do with power-saving, eg. when battery 
is low or the system is inactive, these appear to immediately turn off wifi, 
and bluetooth, respectively, when the machine is a laptop and is unplugged.

  Instead, they should control something more useful, or be relabeled.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-power-manager 3.32.0-1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 19:09:48 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-11-26 (100 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1866277/+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 1813441] Re: Can no longer drag and drop files between desktop and applications

[Norbert]

This functionality should exist without damn extensions. It is essential
functionality of normal feature-rich desktop.

Shame on GNOME!
Normal traditional users should use MATE, KDE or Xfce instead of supporting
GNOME illness.

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1813441] Re: Can no longer drag and drop files between desktop and applications

[Paddy Landau]

The updated Desktop Icons, "Desktop Icons NG (DING)" (by the same
author), fixes these problems.

Canonical could make its life easier by simply replacing the old Desktop
Icons with the new Desktop Icons NG (DING).

Desktop Icons:
https://extensions.gnome.org/extension/1465/desktop-icons/

Desktop Icons NB (DING):
https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1899125] Re: Font scaling factor is lost after loging out

[Daniel van Vugt]

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

You are probably missing the fix that's in mutter 3.36.6? Try updating.

** Tags added: focal

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

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

** This bug has been marked a duplicate of bug 1892440
   Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on 
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/1899125

Title:
  Font scaling factor is lost after loging out

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell source package in Focal:
  Incomplete

Bug description:
  I have a font scaling factor set in gnome-tweaks. If I logout and back
  in the fonts are no longer scaled even though gnome-tweaks still shows
  the scaling factor.

  This problem showed up after a Focal update a couple of weeks ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899125/+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 1899125] [NEW] Font scaling factor is lost after loging out

[Juerg Haefliger]

Public bug reported:

I have a font scaling factor set in gnome-tweaks. If I logout and back
in the fonts are no longer scaled even though gnome-tweaks still shows
the scaling factor.

This problem showed up after a Focal update a couple of weeks ago.

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

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

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Font scaling factor is lost after loging out

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New

Bug description:
  I have a font scaling factor set in gnome-tweaks. If I logout and back
  in the fonts are no longer scaled even though gnome-tweaks still shows
  the scaling factor.

  This problem showed up after a Focal update a couple of weeks ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899125/+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