[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute

[Gunnar Hjalmarsson]

I noticed . It's not clear to me if the
OP had run into difficulties due to packages in the Ubuntu archive, or
because some Adobe repo was enabled among the apt sources. In case of
the former, the idea with replacing the packages with dummies soon
appears to be even more desirable than I first thought.

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

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 hirsute. Does our agreement with
  Adobe for distributing Flash installers or code allow us to skip
  shipping Flash in hirsute?

  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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Piotr Tomaszewski]

Ubuntu with kernel 5.11-rc2 from mainline - touchpad MSFT0001:00
04F3:3140 Touchpad - works out of the box. There is only problem with
nvidia drivers...

-- 
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:
  Update (#296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work. Before the
  release of v5.11, you are suggested to use #189 to save your touchpad.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  
  Original bug report
  ===

  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 

[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

[Stefan Bakic]

@Timo Aaltonen

What is the expected date for this patch to be merged with a main branch
or whatever. So I could get it with "apt update"?

Thanks

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Drag and drop files from Desktop to Nautilus freezes gnome-shell in
  Ubuntu 20.10. There is no way to recover without killing gnome-shell
  externally or rebooting.

  [Test Case]

  1. Create a file in ~/Desktop
  2. Open a nautilus (Files) window of a different directory.
  3. Drag the new file from the desktop into the nautilus (Files) window.

  The shell should not become unresponsive. Also, the drag is expected
  to fail and snap back. That's a different issue (bug 1813441) not
  being fixed here.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading.

  [Other Info]

  Patch is in bug 1898005.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1869734] Re: openjade segfaults on all arch

[Christian Ehrhardt ]

Synced the fix after Christoph uploaded it
=> https://launchpad.net/ubuntu/+source/openjade/1.4devel1-22

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

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Triaged
Status in pgpool2 package in Ubuntu:
  New
Status in openjade package in Debian:
  Unknown

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1909857] Re: NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10

[Nico]

Erm... No bite? Not the right place? Missing bits of info? No interest?

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

Title:
  NUC7i5 - No HBR, unstable EAC3 audio passthrough on Ubuntu 20.10

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Software is X11-based stable/up-to-date Kodi v18 on up-to-date Ubuntu 20.10.
  Hardware is an Intel NUC7i5BNH (Kaby Lake), latest available BIOS and latest 
available HDMI/LS-PCON firmware. The AVR is a Denon AVR-2310. The TV is an old 
Toshiba 1080p LCD. I make sure that the TV and AVR are turned on first so that 
EDID is available.

  When playing a file with HBR audio bitstreams (DTS-HD, Dolby TrueHD) I get no 
audio.
  When playing a file with EAC3/DD+ audio bitstreams, I get very regular 
dropouts.
  When I play a file with stereo/DTS/DD bitstreams, all is fine.
  When I play an audio file with 6 channels of LPCM, all is fine.

  I can play the same files with HBR or EAC3 audio on the same machine from a 
Windows install without any issue, right out of the box using the built-in 
software, using the default configs, which rules out hardware incompatibilities.
  I've spent some time with the Kodi guys who have come to the conclusion that 
the issue was not with them but higher in the software stack. So here I am! 
History here: https://forum.kodi.tv/showthread.php?tid=359371

  I've also filed a bug with Intel, but I'm not getting any traction there. 
Must be the holydays!
  https://gitlab.freedesktop.org/drm/intel/-/issues/2861

  Any help is welcomed.

  I'm no dev, but I know my way around Linux and systems, and I am not
  afraid of testing things and reporting data. Compiling code is usually
  something I can do, with instructions if it's less run-of-the-mill.

  Thanks in advance!

  More specific/detailed background data:

  BIOS: BNKBL357.86A.0083.2020.0714.1344 07/14/2020 (latest available from 
Intel)
  HDMI Firmware: 1.77.93 (the latest available from Intel, updated from a 
Windows install)
  System architecture: ("uname -m"): x86_64
  Kernel version: ("uname -r"): 5.8.0-33-generic
  Linux distribution: Ubuntu 20.10 kept up-to-date
  Machine or motherboard model (use dmidecode if needed): NUC7i5BNH - 
https://paste.ubuntu.com/p/J2V4mKFWSg/
  Display connector: physically HDMI, but I understand that it is internally a 
DP with a protocol converter leading to HDMI
  Full dmesg with debug information: From boot 
https://paste.ubuntu.com/p/53qVzpDJ76/
  I've played a file with DTS-HD HBR audio bitstream (no audio) towards the 
end, if it can help - https://paste.ubuntu.com/p/5pRRpmfT3P/
  I've played a file with EAC3 audio bitstream with dropouts towards the end of 
that one, if it can help - https://paste.ubuntu.com/p/xFPQY5Zzcb/
  xrandr --verbose: https://paste.ubuntu.com/p/V95ZWx9MNy/
  intel_reg_dumper output: https://paste.ubuntu.com/p/bWnjsvQ9t4/
  VBIOS dump: File available there https://youplala.net/~nico/intel/
  lsmod | grep snd: https://paste.ubuntu.com/p/hq9Bf87GbY/
  /proc/asound/card0/codec#2: https://paste.ubuntu.com/p/8JDwbj5pYs/
  /proc/asound/card0/eld#2.0: https://paste.ubuntu.com/p/KdZzHZxTsm/
  cat /sys/devices/pci:00/:00:02.0/drm/card0/card0-DP-1/edid | 
edid-decode: https://paste.ubuntu.com/p/vVjdSWh9Dz/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  2 12:59:50 2021
  InstallationDate: Installed on 2018-02-01 (1066 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to groovy on 2020-12-26 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1909857/+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 1909496] Re: Blinking login screen

[Kleber Sacilotto de Souza]

Hello Rohit or anyone else affected,

We have released a new Focal linux kernel (version 5.4.0-59.65) which
contains several bug fixes. Could you please update to this kernel and
report whether it fixes the issue?

Thank you.

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

Title:
  Blinking login screen

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

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909496/+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 1846423] Re: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION

[Pascal Tombelle]

I'm also experiencing this bug, with Win 10 and TB78.6.0 (32 bits).

Many occurences of :

BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-P2D
DESCRIPTION:Description par défaut Mozilla
X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
 ter with an illegal type for property: VALUE=DURATION
END:VALARM

Some events disappear when I close, then reopen TB

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

Title:
  Lightning: Cannot dismiss reminders. Got a VALUE parameter with an
  illegal type for property: VALUE=DURATION

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Cannot dismiss reminders for a recurrence with exceptions. Calendar entries 
like this are generated:
  BEGIN:VALARM
  ACTION:DISPLAY
  DESCRIPTION:My recurrence
  TRIGGER;VALUE=DURATION:-PT120M
  X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
   ter with an illegal type for property: VALUE=DURATION
  END:VALARM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2004 F pulseaudio
   /dev/snd/controlC0:  vectro 2004 F pulseaudio
  BuildID: 20190705212852
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Oct  2 17:50:39 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.sku: T4M40UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1910235] [NEW] The mouse stops working after taking a screenshot

[Andrey Plaksin]

Public bug reported:

Steps to reproduce this bug:

1. Open Chromium browser.
2. Go to the page with the form in which there is a standard browser drop-down 
menu (form select)
3. Open it
4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
5. Try to switch between applications using the panel and check the operation 
of the mouse in other applications besides browser (in my case Slack)

** Affects: gnome-shell (Ubuntu)
 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/1910235

Title:
  The mouse stops working after taking a screenshot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce this bug:

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mouse in other applications besides browser (in my case Slack)

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

Hi Mike Boruta (maridius),

> On Sun, Nov 29, 2020 at 08:07:43PM -, Mike Boruta wrote:
> >@Coiby Xu (coiby)
> >
> >Hello Coiby, had some time today so I compiled 5.7.19 from ubuntu
> >mainline (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7.19/) with
> >pinctrl_amd configured as a module, applied the patch in #171, and ran
> >the command you provided:
> >
> >$ sudo cat /sys/kernel/debug/gpio | grep -A1 pin130
> >pin130 Level trigger| Active low| interrupt is enabled| interrupt is 
> >unmasked| disable wakeup in S0i3 state| disable wakeup in S3 state|
> > disable wakeup in S4/S5 state| input is high| pull-up is disabled| 
> > Pull-down is disabled| output is disabled| 0x51bc8
> >
> Obviously, the patch in #171 didn't take into effect because 0x51bc8 means
> debounce filter is enabled and the debounce timeout is set to 124.8ms.
> So my best guess is
> /lib/modules/`uname -r`/kernel/drivers/pinctrl/pinctrl-amd.ko.xz
> hasn't been replaced by the patched one.

I had the same issue when using Fedora and find out it's caused by the
pinctrl-amd driver being stored into the initramfs. Maybe the same thing
happened to ubuntu. You can try re-building the initramfs by running
`sudo update-initramfs -u' after replacing the old module with the new
one.


** Description changed:

- Update (#296)
+ Update (based on #296)
  =
  
  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has
  the complete solution to fix this bug. So we can expect kernel v5.11 to
- fix this issue without any additional work. Before the release of v5.11,
- you are suggested to use #189 to save your touchpad.
+ fix this issue without any additional work.
+ 
+ Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
+ On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.
  
  The complete solution is three patches,
-  - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
-  - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
-  - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")
+  - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
+  - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
+  - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")
  
  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.
- 
  
  Original bug report
  ===
  
  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)]
  

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Matt Lee]

Hi Olivier,

Is this branch (and thread) dead? From your last comment, it sounds like
the VA-API code is getting merged into a more mainline branch

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1868561] Re: Xorg Crash on login

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Xorg Crash on login

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to focal development and rebooted. When I try to login, it
  doesn't allow me. Looking at the logs, there's a crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 23 21:44:35 2020
  DistUpgraded: 2020-03-23 21:13:09,930 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   88x2bu, 0.1, 5.3.0-42-generic, x86_64: installed
   88x2bu, 0.1, 5.4.0-18-generic, x86_64: installed
   rtl8812au, 4.3.14, 5.0.0-23-generic, x86_64: built
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: Super Micro Computer Inc ASPEED Graphics Family [15d9:0969]
  MachineType: Supermicro Super Server
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/lvmgrp0-os ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-03-23 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A2SDi-16C-HLN4F
  dmi.board.vendor: Supermicro
  dmi.board.version: 0123456789
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd12/12/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnA2SDi-16C-HLN4F:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868561/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Michel-Ekimia]

For once I'll make some noise :

It's been months , we are using chromium snap and Vaapi support is still
not really there on the stable branch, what's wrong ?

Migrating to snap has been painful to some users and the point for
canonical was to free some time to polish things , which I totally
understand , but then , if we still lack behind mac and windows in terms
of features like battery life , is this worth the hassle ?

Simple question  : does canonical run automatic vaapi test ( amd ,
nvidia , intel ) on each snap release to be sure support is here ?

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  News :

  - Candidate Chromium 83 Snap with vaapi enabled can be installed with
  :

  sudo snap install --channel=candidate/vaapi chromium

  Check that your vidéo is gpu decoded but checking "MojoVideoDecoder"
  in about:media-internals

  Widevine DRM streams will have DecryptingVideoDecoder

  Please report success/failure with

  - distro version
  - GPU Hardware used
  - Codec used

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1906877] Re: diagnostics panel can leave automatic crash reporting enabled

[Martin Wimpress]

** Changed in: gnome-control-center (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  diagnostics panel can leave automatic crash reporting enabled

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Focal:
  Incomplete
Status in gnome-control-center source package in Groovy:
  Incomplete
Status in gnome-control-center source package in Hirsute:
  Fix Released

Bug description:
  * Impact

  If one selects "Automatic" in the "Send error reports to Canonical"
  portion of "Problem Reporting" the file /var/lib/apport/autoreport is
  created. However, if you later switch to "Never" the file is not
  removed but the panel continues to show "Never".

  * Test case

  - change the automatic report option in settings to automatic and then
  to never, the /var/lib/apport/autoreport file should be removed

  * Regression potential

  The patch modifies the whoopsie configuration, check that the service
  status is right for the 3 auto/manual/never options

  

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  4 12:38:37 2020
  InstallationDate: Installed on 2016-01-22 (1778 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1906877/+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 1905825] Re: [SRU] Disable CRTCs when system becomes headless

[Martin Wimpress]

Assign to Marco, to backport the upstream fixes to Focal.

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: mutter (Ubuntu Focal)
 Assignee: Kai-Heng Feng (kaihengfeng) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  New
Status in mutter source package in Groovy:
  New
Status in mutter source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1905825/+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 1905370] Re: The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

[Martin Wimpress]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  The tray icon cannot be displayed when the Ubuntu 20.10 is turned on

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

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1905370/+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 1881926] Re: deja-dup fails with root account

[Martin Wimpress]

** Changed in: duplicity (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  deja-dup fails with root account

Status in Duplicity:
  Invalid
Status in duplicity package in Ubuntu:
  Fix Committed
Status in duplicity source package in Focal:
  Triaged

Bug description:
  I am running deja-dup in Ubuntu 20.04 (Focal Fossa), which has
  duplicity/focal,now 0.8.11.1612-1 and deja-dup/focal,now
  40.6-1ubuntu2.

  When I run deja-dup as myself, it runs fine, but when I launch it with
  sudo, it fails:

  Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 82, in __init__
  ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 37, in ensure_dbus
  output = p.communicate()[0].decode("utf8", errors="replace")
   AttributeError: 'str' object has no attribute 'decode'

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1881926/+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 1910254] [NEW] gnome-shell crash

[J-Paul BERARD]

Public bug reported:

cf bug 1907904

Frequently, GNOME Wayland session close suddenly or when the computer
awakes from stand-by mode

It doesn't appear always. The session may close suddenly (may be when I
do something with a file on the desktop) and more often when I put the
computer in stand-by mode and awake it again.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  5 15:41:47 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-10 (270 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-10-24 (72 days ago)

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


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

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

Title:
  gnome-shell crash

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  cf bug 1907904

  Frequently, GNOME Wayland session close suddenly or when the computer
  awakes from stand-by mode

  It doesn't appear always. The session may close suddenly (may be when
  I do something with a file on the desktop) and more often when I put
  the computer in stand-by mode and awake it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 15:41:47 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-10 (270 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910254/+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 1906539] Re: tex-common fails to configure in hirsute-proposed

[Martin Wimpress]

** Changed in: tex-common (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  tex-common fails to configure in hirsute-proposed

Status in tex-common package in Ubuntu:
  Incomplete

Bug description:
  tex-common fails to configure in hirsute-proposed:

  Setting up sbuild-build-depends-gcc-10-dummy (0.invalid.0) ...
  Processing triggers for tex-common (6.15) ...
  Running updmap-sys. This may take some time... done.
  Running mktexlsr /var/lib/texmf ... done.
  Building format(s) --all.
This may take some time... 
  fmtutil failed. Output has been stored in
  /tmp/fmtutil.a8TypC2W
  Please include this file if you report a bug.

  dpkg: error processing package tex-common (--configure):
   installed tex-common package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   tex-common
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  apt-get failed.
  Package installation failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1906539/+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 1908502] Re: [MIR] libtiff5 dependency on libdeflate0

[Martin Wimpress]

** Changed in: tiff (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [MIR] libtiff5 dependency on libdeflate0

Status in libdeflate package in Ubuntu:
  Incomplete
Status in tiff package in Ubuntu:
  Confirmed

Bug description:
  tiff 4.1.0+git201212-1 enabled deflate support, adding libdeflate0 as
  a dependency to libtiff5, making the package uninstallable.

  Therefor I uploaded 4.1.0+git201212-1ubuntu1 disabling the deflate
  support to make libtiff5 installable again.

  Either this package stays this way, or it needs a MIR for libdeflate.

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

[Eamon O Callaghan]

Thank you everyone for fixing this, I've been following this thread for
the last few weeks and today is the first time I've managed to get it
working.

For any noobs like me that are on Ubuntu this is the guide that I
followed to upgrade to kernel 5.11 and everything works perfectly for
me, both the touchpad and the brightness controls.

Upgrade kernel

Change current directory to /tmp
cd /tmp

Download the latest mainline kernel from 5.11.x branch by copying
and pasting this:

wget -c 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc2/amd64/linux-headers-5.11.0-051100rc2_5.11.0-051100rc2.202101032030_all.deb
wget -c 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc2/amd64/linux-headers-5.11.0-051100rc2-generic_5.11.0-051100rc2.202101032030_amd64.deb
wget -c 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc2/amd64/linux-image-unsigned-5.11.0-051100rc2-generic_5.11.0-051100rc2.202101032030_amd64.deb
wget -c 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc2/amd64/linux-modules-5.11.0-051100rc2-generic_5.11.0-051100rc2.202101032030_amd64.deb

Install new kernel
sudo dpkg -i *.deb

Reboot the system
sudo shutdown -r now

Update packages list
sudo apt-get update

Upgrade packages
sudo apt-get upgrade

Reboot the system if needed
sudo shutdown -r now

Check the OS distro
lsb_release -a

Check kernel version
uname -r

That's it, now you should be running on the Linux Kernel 5.11rc2

Guide taken from this wonderful page:
https://sypalo.com/how-to-upgrade-ubuntu

Thanks to everyone for their hard work, sorry for posting this noob
guide here but it took me weeks to figure out an easy way to do it
(patching was beyond my abilities).

-- 
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:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

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

[Desktop-packages] [Bug 1909012] Re: my display are disappeared with I used libreoffice or other software

[Heather Ellsworth]

Thanks for your bug report that helps make Ubuntu better!

Can you trigger the problem in a reproducible manner on your system?
How do you recover your system? Do you need to restart to get your displays 
back?

If you can reproduce the issue, can you please provide the system logs?
There are a couple of methods to grab them but I'd recommend opening a
terminal and watching the logs when you trigger the failure, then paste
them here:

In a terminal, start watching logs
$ sudo journalctl -f

Trigger the failure and copy/paste the logs here or in a text file and
upload it to this bug.

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

Title:
  my display are disappeared with I used libreoffice or other software

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I was using libreoffice writer while, pasting an image and printing it, the 
screen went black while I was moving the mouse, the menu of favorite programs 
remains clearly visible on the sides of the screen and at the top the bar with 
the clock in the center and on the right side the internet connection, audio 
volume and shutdown lights.
  This is not the first time this has happened, not only with libreoffice suite 
but also with other programs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909012/+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 1844024] Re: No exit and fails to quit when closed. .

[crvi]

Is this still relevant ?

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

Title:
  No exit  and fails to quit when closed. .

Status in rhythmbox package in Ubuntu:
  Opinion

Bug description:
  No exit  and fails to quit when closed. .

  Step to reproduce.


  Step 1. Launch Rhythmbox

  
  Issue.  No exit or quit option under the file menu. Simply one deceptive 
close option.

  
  Step to reproduce. 


  Step 1. Close Rhythmbox

  
  Issue.  Rhythmbox is still running.

  
  This is entirely unacceptable malware like behavior and makes the program 
unsuitable for use or distribution.

  This issue seems to be limited to bad patches in the Ubuntu version.

  
  We also need:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
Installed: 3.4.3-1ubuntu1
Candidate: 3.4.3-1ubuntu1
Version table:
   *** 3.4.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3) What you expected to happen
  To be able to close the program after opening it.
  4) What happened instead
  The program must be killed every time I want to close it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1844024/+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 1754125] Re: Rhythmbox stays running in the background after quit

[crvi]

"Stop & Quit" might not always work in slow / single core machines.

Issue: https://gitlab.gnome.org/GNOME/glib/-/issues/2284

MR: Please refer
https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/88

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2284
   https://gitlab.gnome.org/GNOME/glib/-/issues/2284

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

Title:
  Rhythmbox stays running in the background after quit

Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  If you do ps -alx you will see rhythmbox process still running. It
  causes opening rhythmbox to hang when trying to open again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rhythmbox 3.4.2-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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  7 13:21:51 2018
  InstallationDate: Installed on 2018-03-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1905825] Re: [SRU] Disable CRTCs when system becomes headless

[Kai-Heng Feng]

Backport for gnome-3-36 is here:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1656

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

Title:
  [SRU] Disable CRTCs when system becomes headless

Status in HWE Next:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  New
Status in mutter source package in Groovy:
  New
Status in mutter source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On new Intel SoCs, after all connectors are unplugged and the system becomes 
headless, it cannot detect monitor hotplug event from type-c port.

  [Fix]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561

  Based on "drm/i915 Intel GFX Driver, Hotplug" [1]:
  "Finally, the userspace is responsible for triggering a modeset upon 
receiving the hotplug uevent, disabling or enabling the crtc as needed."

  [Test]
  Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor 
back, monitor is blank.
  With the fix applied, the system can detect monitor again.

  [Where problems could occur]
  This fix disables CRTCs when there's no monitor, if driver has trouble 
dealing with it, we may see something break.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1905825/+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 1909463] Re: Libreoffice crashed when saving certain documents as docx, doc

[Heather Ellsworth]

Thanks for reporting your issue and helping make Ubuntu better!

Can you reproduce the crash reliably? If so what are the steps?

To debug the issue we need logs. Could you please do
$ sudo journalctl -f
then try to reproduce the crash and see if anything is printed in the log and 
paste it here?

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

Title:
  Libreoffice crashed when saving certain documents as docx, doc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice crashed when saving certain documents as docx, doc.
  test.odt attached.

  Also tested with libreoffice 7.0.4 from ppa, issue present.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 12:27:55 2020
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (234 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-04-04T09:25:22.888039

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909463/+subscriptions

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

[Desktop-packages] [Bug 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Kai Groner]

I've also had this problem with the flameshot icon disappearing after
upgrading to 20.04.

Reverting to gnome-shell-extension-appindicator 33-1 has fixed it for
now, but having broken dependencies isn't good (even if things seem to
be working).


Comments on https://github.com/flameshot-org/flameshot/issues/1206 also suggest 
this problem doesn't occur with the flameshot snap.  Testing the deb package 
specifically may be a good idea.

** Bug watch added: github.com/flameshot-org/flameshot/issues #1206
   https://github.com/flameshot-org/flameshot/issues/1206

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

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

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

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

  ---

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions

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

[Desktop-packages] [Bug 1805666] Re: Evolution Alarm Notify continues pop-up reminders even though notifications disabled

[Jon Cline]

Same issue for me as I'd like general notifications just not routed to
Gnome via the Evolution popup.

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

Title:
  Evolution Alarm Notify continues pop-up reminders even though
  notifications disabled

Status in evolution-data-server package in Ubuntu:
  Invalid

Bug description:
  I have turned off notifications for evolution alarm notify in settings:
  https://i.imgur.com/BNlfgzA.png

  But I still get pop-ups from the evolution alarm notify app for calendar 
events:
  https://i.imgur.com/BBdr9gm.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evolution-data-server 3.30.1-1build1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 28 11:31:46 2018
  ExecutablePath: 
/usr/lib/evolution/evolution-data-server/evolution-alarm-notify
  InstallationDate: Installed on 2018-07-14 (136 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to cosmic on 2018-10-29 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1805666/+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 1909463] Re: Libreoffice crashed when saving certain documents as docx, doc

[Eugene Romanenko]

"Can you reproduce the crash reliably? If so what are the steps?" - just
open attached test.odt and save as Word document (.docx or .doc).
LibreOffice will say it's crashed due to error and ask for document
recovery. For me it's 100% reproducible on all my laptops/PCs.

No info in logs, as LibreOffice handles this crash itself.

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

Title:
  Libreoffice crashed when saving certain documents as docx, doc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice crashed when saving certain documents as docx, doc.
  test.odt attached.

  Also tested with libreoffice 7.0.4 from ppa, issue present.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 12:27:55 2020
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (234 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-04-04T09:25:22.888039

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1909463/+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 1905186] Re: dock and top bar flashing non-stop at fullscreen

[sepukkuhero]

Update: the problem only happens in the session with xorg (gnome or
ubuntu) ...

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  
  This problem affects all extensions that alter the dock and top bar. 
Including the standard extension "Ubuntu dock". All extensions are duly updated 
to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905186/+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 1910275] [NEW] hotspot option is sometimes not clickable. And it doesn't have internet access.

[sepukkuhero]

Public bug reported:

The hotspot option is mostly gray (impossible to create, even if
properly connected to wifi, even on different networks). And when I can
create, the hotspot appears but does not have access to the internet.

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

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

Title:
  hotspot option is sometimes not clickable. And it doesn't have
  internet access.

Status in network-manager package in Ubuntu:
  New

Bug description:
  The hotspot option is mostly gray (impossible to create, even if
  properly connected to wifi, even on different networks). And when I
  can create, the hotspot appears but does not have access to the
  internet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1910275/+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 1905186] Re: dock and top bar flashing non-stop at fullscreen

[sepukkuhero]

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

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

** Also affects: gnome-shell-extension-dash-to-panel (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  dock and top bar flashing non-stop at fullscreen

Status in gnome-shell-extension-autohidetopbar package in Ubuntu:
  New
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  
  This problem affects all extensions that alter the dock and top bar. 
Including the standard extension "Ubuntu dock". All extensions are duly updated 
to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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

[Desktop-packages] [Bug 1897754] Re: flameshot: The icon does not appear in the GNOME bar

[Gerhard Beck]

But the problem is that it also affects e.g. the Nextcloud desktop
client, so just using the snap package is not the solution

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

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

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

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

  ---

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions

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

[Desktop-packages] [Bug 1910279] [NEW] mate-session starts instead when i3 was selected on login screen

[Norbert]

Public bug reported:

Steps to reproduce:

1. Have Ubuntu MATE 20.10 installed
2. Install i3 with `sudo apt-get install i3*`
3. Reboot machine 
4. Select i3 (or i3 with debug) on login screen

Expected results:

* i3 starts

Actual results:

* MATE starts instead of i3

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: mate-session-manager 1.24.1-1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Jan  5 22:27:29 2021
InstallationDate: Installed on 2020-10-23 (74 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: mate-session-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: arctica-greeter (Ubuntu)
 Importance: Undecided
 Status: New

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

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


** Tags: amd64 apport-bug groovy

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

** Also affects: arctica-greeter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+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 1905422] Re: CoinMP Solver not Available, option requires coinmp to be promoted

[Heather Ellsworth]

** Changed in: libreoffice (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  CoinMP Solver not Available, option requires coinmp to be promoted

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Hi! LibreOffice Calc supports the CoinMP Linear Solver, which is an
  excellent solver to be used in spreadsheets and makes LO Calc superior
  to other office suites in that regard.

  However, the build provided by this PPA does not come with CoinMP
  Solver enabled (see Tools > Solver > Options). I posted a question at
  Ask LibreOffice and I was informed that CoinMP is enabled by default
  during build and maybe the PPA maintainers chose to disable it.

  https://ask.libreoffice.org/en/question/240836/coinmp-solver-on-
  libreoffice-calc/

  In fact, I built LibreOffice from source and CoinMP was there.
  However, building from source is not convenient and I'd like to use
  the PPA.

  Is it possible that CoinMP Solver be included in future builds of
  LibreOffice provided by this PPA?

  I am currently using LibreOffice 7.0.3.1 on Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905422/+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 1785262] Re: arm64 autopkgtests are flaky

[Heather Ellsworth]

** Changed in: libreoffice (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  arm64 autopkgtests are flaky

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64.

  In the past 30 days, 8 out of 45 test runs failed. That a 18% failure
  rate. It would be good to understand if all those failures are
  similar, what's causing them, and if they can easily be made more
  robust.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1785262/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

It seems that ~/.dmrc

$ cat .dmrc 
[Desktop]
Session=i3-with-shmlog

is ignored or not written, or something similar.


So the workaround is a bit horrible and MATE-destructive:

```
sudo apt autopurge mate-session-manager
```

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Gunnar Hjalmarsson]

What does this command output:

sudo grep Session /var/lib/AccountsService/users/$USER

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

After entering to "i3" it says:

```
$ sudo grep Session /var/lib/AccountsService/users/$USER
Session=mate
XSession=mate
```

So there is something wrong with new arctica greeter.

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

After removing mate-session-manager it shows the following:

```
$ sudo grep Session /var/lib/AccountsService/users/$USER
Session=mate
XSession=i3
```

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

** Changed in: arctica-greeter (Ubuntu)
   Status: New => Confirmed

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Gunnar Hjalmarsson]

And I think that "XSession" is what counts.

Does it help if you switch to lightdm-gtk-greeter (but keep mate-
session-manager)?

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+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 1910287] [NEW] Touchpad Scrolling and Cursor Speed Reset on Awakening

[Mister Toszter]

Public bug reported:

As a user, when my computer reawakens from sleep, often the touchpad
(Apple Touchpad 2) settings are "reset to default" meaning that natural
scrolling becomes unnatural, right click is disabled, and cursor speed
is slow again. Sometimes the trackpad becomes altogether unresponsive
and needs disconnection and reconnection.

Ubuntu 20.04 LTS

I then have to open settings and cycle all the toggles for the old
settings to reengage.

That's about all.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 01:13:39 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan  5 13:05:51 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
 nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
 nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GP102 [TITAN X] [10de:119a]
 ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9]
InstallationDate: Installed on 2020-07-17 (172 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. Z10PE-D16 WS
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=1c2a4ecb-99e5-4bb1-bc33-e9769d76de0f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3407
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z10PE-D16 WS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3407:bd03/10/2017:svnASUSTeKCOMPUTERINC.:pnZ10PE-D16WS:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PE-D16WS:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: Server
dmi.product.name: Z10PE-D16 WS
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER 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 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1910287

Title:
  Touchpad Scrolling and Cursor Speed Reset on Awakening

Status in xorg package in Ubuntu:
  New

Bug description:
  As a user, when my computer reawakens from sleep, often the touchpad
  (Apple Touchpad 2) settings are "reset to default" meaning that
  natural scrolling becomes unnatural, right click is disabled, and
  cursor speed is slow again. Sometimes the trackpad becomes altogether
  unresponsive and needs disconnection and reconnection.

  Ubuntu 20.04 LTS

  I then have to open settings and cycle all the toggles for the old
  settings to reengage.

  That's about all.

  

[Desktop-packages] [Bug 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

Yes, it works with `lightdm-gtk-greeter`.

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Gunnar Hjalmarsson]

Ok, then we seem to have defined the problem: There is a need to make
arctica-greeter play well with accountsservice.

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+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 1910279] Re: mate-session starts instead when i3 was selected on login screen

[Norbert]

** No longer affects: lightdm (Ubuntu)

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

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Mike Boruta]

Hello Coiby Xu (coiby), thanks a lot for this information! Will
definitely try this should I encounter a similar error again; and its
just generally good knowledge. Completely forgot about the initramfs.

-- 
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:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

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

[Desktop-packages] [Bug 1908699] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  New bugfix release 20.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1908699] Re: New bugfix release 20.2.6

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 20.2.6-0ubuntu0.20.10.1

---
mesa (20.2.6-0ubuntu0.20.10.1) groovy; urgency=medium

  * New upstream bugfix release. (LP: #1908699)

 -- Timo Aaltonen   Fri, 18 Dec 2020 10:35:45 +0200

** Changed in: mesa (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  New bugfix release 20.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1902244] Re: Backport packages for 20.04.2 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package libdrm - 2.4.102-1ubuntu1~20.04.1

---
libdrm (2.4.102-1ubuntu1~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Thu, 17 Sep 2020 12:29:42 +0300

** Changed in: libdrm (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libglvnd source package in Focal:
  Fix Committed
Status in llvm-toolchain-11 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)

[Daniel van Vugt]

Upstream has closed the bug because it stopped happening with:

  mutter 3.38.2 + Xorg 1.20.10

We are about to get the first one in Ubuntu so we'll find out if it's
enough.

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

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  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
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  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
  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 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/gnome-shell/+bug/1896627/+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 1908699] Re: New bugfix release 20.2.6

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 20.2.6-0ubuntu0.20.04.1

---
mesa (20.2.6-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream bugfix release. (LP: #1908699)

mesa (20.2.1-1~ubuntu0.20.04.2) focal; urgency=medium

  * ppc64el-ftbfs-fix-type-collisions.diff: Fix build failure on ppc64el.
(LP: #1902244)

mesa (20.2.1-1~ubuntu0.20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Fri, 18 Dec 2020 10:35:45 +0200

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  New bugfix release 20.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 20.2.x-series, we should put it
  in groovy so latest bugfixes would get there, and for focal because
  that would minimize the risk of regressions when going from 20.0.x to
  20.2.x.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+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 1902244] Re: Backport packages for 20.04.2 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package llvm-toolchain-11 -
1:11.0.0-2~ubuntu20.04.1

---
llvm-toolchain-11 (1:11.0.0-2~ubuntu20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Fri, 30 Oct 2020 16:15:47 +0200

** Changed in: llvm-toolchain-11 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: libglvnd (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libglvnd source package in Focal:
  Fix Released
Status in llvm-toolchain-11 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.2 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package xorg-server -
2:1.20.9-2ubuntu1.1~20.04.1

---
xorg-server (2:1.20.9-2ubuntu1.1~20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Fri, 18 Dec 2020 15:08:03 +0200

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libglvnd source package in Focal:
  Fix Released
Status in llvm-toolchain-11 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.2 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 20.2.6-0ubuntu0.20.04.1

---
mesa (20.2.6-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream bugfix release. (LP: #1908699)

mesa (20.2.1-1~ubuntu0.20.04.2) focal; urgency=medium

  * ppc64el-ftbfs-fix-type-collisions.diff: Fix build failure on ppc64el.
(LP: #1902244)

mesa (20.2.1-1~ubuntu0.20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Fri, 18 Dec 2020 10:35:45 +0200

** Changed in: xorg-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libglvnd source package in Focal:
  Fix Released
Status in llvm-toolchain-11 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.2 HWE stack

[Launchpad Bug Tracker]

This bug was fixed in the package libglvnd - 1.3.2-1~ubuntu0.20.04.1

---
libglvnd (1.3.2-1~ubuntu0.20.04.1) focal; urgency=medium

  * Backport to focal. (LP: #1902244)

 -- Timo Aaltonen   Tue, 24 Nov 2020 12:55:47 +0200

** Changed in: mesa (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 20.04.2 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libglvnd package in Ubuntu:
  Invalid
Status in llvm-toolchain-11 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libclc source package in Focal:
  Fix Released
Status in libdrm source package in Focal:
  Fix Released
Status in libglvnd source package in Focal:
  Fix Released
Status in llvm-toolchain-11 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.2 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-11: a new package, no regression potential on it's own

  libclc: just a rebuild against the new llvm

  libglvnd: mostly just EGL headers sync from Khronos, needed by mesa

  mesa: a new major release, but we'll pull the final stable release of
  20.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell

[Daniel van Vugt]

The fix for this bug is a single package, so you can download it
directly right now, even before it becomes an official update:

https://launchpad.net/ubuntu/+archive/primary/+files/gnome-shell-
extension-desktop-icons_20.04.0+git20200908-5~ubuntu20.10.0_all.deb

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

Title:
  [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
  shell

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Drag and drop files from Desktop to Nautilus freezes gnome-shell in
  Ubuntu 20.10. There is no way to recover without killing gnome-shell
  externally or rebooting.

  [Test Case]

  1. Create a file in ~/Desktop
  2. Open a nautilus (Files) window of a different directory.
  3. Drag the new file from the desktop into the nautilus (Files) window.

  The shell should not become unresponsive. Also, the drag is expected
  to fail and snap back. That's a different issue (bug 1813441) not
  being fixed here.

  [Where problems could occur]

  An extension with syntax errors may fail to load leaving the user with
  reduced shell functionality. A more faulty extension might crash the
  entire shell after loading.

  [Other Info]

  Patch is in bug 1898005.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  4 12:19:26 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-03 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1909776] Re: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

[Launchpad Bug Tracker]

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

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

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

Title:
  Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It seems like this is an old bug and I'm noticing only in the last few
  months.

  Sometimes, after I leave my PC on or after a standby, my left mouse
  button seems stuck in two appimage applications (freecad 0.18.4 and
  cura 4.8.0).

  I found no way to workaround this if not just after a reboot.

  Thanks in advance,

  Massimo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
  Uname: Linux 4.15.0-128-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 31 18:59:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2015-12-12 (1846 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80HE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic 
root=UUID=691bfdf1-ec74-4a27-bfe5-b660d9b9531f ro noprompt quiet splash 
pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 
resume=UUID=9aa74165-44e7-42e8-8792-f50b6d875421 net.ifnames=0 biosdevname=0 
i8042.reset vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A6CN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 3 Pro-1370
  dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80HE
  dmi.product.version: Lenovo YOGA 3 Pro-1370
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Dec 31 12:49:57 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.8
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909776/+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 1040844] Re: Left Mouse Button Sometimes Gets Stuck in Unity (12.04)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1909776
   Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

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

Title:
  Left Mouse Button Sometimes Gets Stuck in Unity (12.04)

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The symptoms : I do "something" (haven't quite put my finger on it
  yet) that causes the left mouse button to appear stuck down (its like
  a MOUSE_DOWN event happened, but never a corresponding MOUSE_UP
  event).

  The stuck mouse button manifest itselfin Intellij IDEA, which
  basically becomes unusable.  Many times when this happens, the same
  behavior is also present on applications inside the virtual box VMs.

  I generally have the following three programs running at all times, so
  I think it is triggered by something in them (I have a sneaking
  suspicious its using the mousewheel to scroll up / scroll down in the
  virtualbox vm).

   - Intellij IDEA
   - Virtual Box (usually running a few windows VMs)
   - Chromium

  To solve the problem, I end up having to completely reboot (which
  kills a lot of time, because I have to alsy cycle the VMs).

  As far as what triggers this problem - it is somewhat hard to
  determine but I think it may have something to do with using the
  mousewheel while the focus is on one of the virtual box VMs.

  One other thing I've noticed is that the problem only seems to happen
  in Unity. If I choose Gnome shell then I've not had the issue (but I
  end up coming back to Unity since its grown on me).

  Other people have also reported the same or similar issue here (I also
  posted a description there) :

   http://askubuntu.com/questions/155499/regain-control-of-mouse-by-
  restarting-xorg/179571#179571

  I am using 12.04 64-bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1040844/+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 1909776] Re: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

[Daniel van Vugt]

Thanks for the bug report.

* Do you mean a mouse or touchpad?

* If it's an actual mouse then please try plugging in a different mouse.

* Are there any other apps affected?

* Please also try a newer kernel:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

  or more simply, try booting a newer Ubuntu release:

  https://ubuntu.com/download/desktop


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

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

Title:
  Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It seems like this is an old bug and I'm noticing only in the last few
  months.

  Sometimes, after I leave my PC on or after a standby, my left mouse
  button seems stuck in two appimage applications (freecad 0.18.4 and
  cura 4.8.0).

  I found no way to workaround this if not just after a reboot.

  Thanks in advance,

  Massimo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
  Uname: Linux 4.15.0-128-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 31 18:59:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2015-12-12 (1846 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80HE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic 
root=UUID=691bfdf1-ec74-4a27-bfe5-b660d9b9531f ro noprompt quiet splash 
pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 
resume=UUID=9aa74165-44e7-42e8-8792-f50b6d875421 net.ifnames=0 biosdevname=0 
i8042.reset vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A6CN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 3 Pro-1370
  dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80HE
  dmi.product.version: Lenovo YOGA 3 Pro-1370
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Dec 31 12:49:57 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.8
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1909776/+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 1909834] Re: [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  sound card disappeared
  just see rtp multicast sink - no sound card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  evstratios  10958 F pipewire-media-
   /dev/snd/seq:evstratios  10946 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Jan  1 17:49:50 2021
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio 
fails to detect card
  UpgradeStatus: Upgraded to groovy on 2020-12-31 (1 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0JF2P0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:br1.13:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0JF2P0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1909834/+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 1846837] Re: totem-video-thumbnailer in Ubuntu 20.04 is currently broken on aarch64

[RussianNeuroMancer]

Just noticed that this issue affect regular Totem video player too. And
it also is still reproducible on 20.10.

** Also affects: gcc-10 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- totem-video-thumbnailer in Ubuntu 20.04 is currently broken on aarch64
+ totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

** Summary changed:

- totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
+ Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken 
on aarch64

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #648
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/648

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

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in gst-libav1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello!

  I found that totem-video-thumbnailer is broken on aarch64. It fail
  with following error:

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  I tried to rollback all related packages I could think of (totem,
  gcc-9, ffmpeg) to previous releases, but for some reason this doesn't
  help. I remember video thumbnail generation on aarch64 worked fine few
  weeks ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1846837/+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 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

[RussianNeuroMancer]

https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/648

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

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in gst-libav1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello!

  I found that totem-video-thumbnailer is broken on aarch64. It fail
  with following error:

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  I tried to rollback all related packages I could think of (totem,
  gcc-9, ffmpeg) to previous releases, but for some reason this doesn't
  help. I remember video thumbnail generation on aarch64 worked fine few
  weeks ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1846837/+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 1909935] Re: no desktop icons/files after start

[Daniel van Vugt]

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

Thanks for the bug report. I've now generalized bug 1883174 so we can
group it with that.

** This bug has been marked a duplicate of bug 1883174
   Some (or all) desktop icons are missing

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

Title:
  no desktop icons/files after start

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

Bug description:
  After upgrading to Ubuntu 20.10 I don't see any files/launchers on the 
desktop after start. 
  But if I create a new Desktop folder per context menu, all files/launchers 
appear on the desktop.

  lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-desktop-icons 20.04.0+git20200908-1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 21:58:11 2021
  InstallationDate: Installed on 2019-08-04 (518 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to groovy on 2020-11-18 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1909935/+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 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64

[Daniel van Vugt]

** Tags removed: eoan
** Tags added: focal groovy

** Also affects: gstreamer via
   https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/648
   Importance: Unknown
   Status: Unknown

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

Title:
  Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
  broken on aarch64

Status in GStreamer:
  Unknown
Status in gcc-10 package in Ubuntu:
  New
Status in gcc-9 package in Ubuntu:
  New
Status in gst-libav1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  Hello!

  I found that totem-video-thumbnailer is broken on aarch64. It fail
  with following error:

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788:
  Failed to load plugin '/usr/lib/aarch64-linux-
  gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-
  gnu/libgomp.so.1: cannot allocate memory in static TLS block

  I tried to rollback all related packages I could think of (totem,
  gcc-9, ffmpeg) to previous releases, but for some reason this doesn't
  help. I remember video thumbnail generation on aarch64 worked fine few
  weeks ago.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1846837/+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 1883174] Re: Some (or all) desktop icons are missing

[Daniel van Vugt]

** Summary changed:

- Some desktop icons disappear
+ Some (or all) desktop icons are missing

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

Title:
  Some (or all) desktop icons are missing

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

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1910254] Re: gnome-shell crash

[Daniel van Vugt]

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

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


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

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

Title:
  gnome-shell crash

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  cf bug 1907904

  Frequently, GNOME Wayland session close suddenly or when the computer
  awakes from stand-by mode

  It doesn't appear always. The session may close suddenly (may be when
  I do something with a file on the desktop) and more often when I put
  the computer in stand-by mode and awake it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 15:41:47 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-10 (270 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910254/+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 1909946] Re: Gnome Wayland session starts, then quits.

[Daniel van Vugt]

Thanks for the log. This suggests gnome-shell died because Xorg or
Xwayland had already died:

Jan 04 12:21:10 stephen-desktop gnome-shell[83433]: gnome-shell: Fatal
IO error 11 (Resource temporarily unavailable) on X server :0.

So please:

1. Delete all existing files from /var/crash/

2. Reproduce the crash.

3. Use these instructions to report future crashes to us:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Gnome Wayland session starts, then quits.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  So, this started about a week ago after an update from Ubuntu. I can
  initially login with XWayland, but something loading after the desktop
  appears, causes the session to exit. The only thing I can find
  relevant in the logs at the timestamp this occurred are the following:

  -gkr-pam: unable to locate daemon control file

  -Failed to start Process error reports when automatic reporting is
  enabled.

  -A start job for unit UNIT has failed

  I hope this helps track down the issue. Thanks for reading.

  BTW I have to submit this as a bug on something else, launchpad keeps
  telling me that XWayland doesn't exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xwayland 2:1.20.9-2ubuntu1.1
  Uname: Linux 5.9.16-xanmod1 x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 19:33:28 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2020-04-25 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.9.16-xanmod1 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-1ubuntu1~g~mesarc0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.3.1+git2012290142.009e2aa5460~g~mesarc2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909946/+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 1910287] Re: Touchpad Scrolling and Cursor Speed Reset on Awakening

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1899206
   Input device settings not applied on hotplug/reconnect/resume in Xorg 
sessions

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

Title:
  Touchpad Scrolling and Cursor Speed Reset on Awakening

Status in xorg package in Ubuntu:
  New

Bug description:
  As a user, when my computer reawakens from sleep, often the touchpad
  (Apple Touchpad 2) settings are "reset to default" meaning that
  natural scrolling becomes unnatural, right click is disabled, and
  cursor speed is slow again. Sometimes the trackpad becomes altogether
  unresponsive and needs disconnection and reconnection.

  Ubuntu 20.04 LTS

  I then have to open settings and cycle all the toggles for the old
  settings to reengage.

  That's about all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 13:05:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GP102 [TITAN X] [10de:119a]
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9]
  InstallationDate: Installed on 2020-07-17 (172 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. Z10PE-D16 WS
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=1c2a4ecb-99e5-4bb1-bc33-e9769d76de0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3407
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z10PE-D16 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3407:bd03/10/2017:svnASUSTeKCOMPUTERINC.:pnZ10PE-D16WS:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PE-D16WS:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Server
  dmi.product.name: Z10PE-D16 WS
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER 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 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xse

[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes with [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed()

[Daniel van Vugt]

** Summary changed:

- 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() [desktopGrid.js:206]
+ gnome-shell crashes with [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: 
assertion failed: (priv->child == NULL)] called from 
DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206]

-- 
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 with [St:ERROR:../src/st/st-
  bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)]
  called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206]

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Groovy:
  Fix Committed
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Confirmed
Status in gnome-shell source package in Hirsute:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Hirsute:
  Confirmed

Bug description:
  [Impact]

  Gnome Shell crashes at random times.

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

  [Test Case]

  None known.

  [Where problems could occur]

  The proposed fix is from the stable upstream gnome-shell branch so
  potential problems could arise from the usual risk of patching stable
  branches resulting in new regressions.

  [Other Info]

  See also bug 1898005

  ---

  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: CrashDistroRelease: 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: 6SourcePackage: 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 1907904] Re: gnome-shell 20.10 crashes with Wayland

[Daniel van Vugt]

Thanks for reporting bug 1910254, that one is a duplicate of bug 1898910
for which a fix will soon be released.

Would you like to keep this bug open or mark it also as a duplicate of
bug 1898910?

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

Title:
  gnome-shell 20.10 crashes with Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Gnome 20.10 (upgraded from 20.04), 64 bits,Wayland session
  AMD CPU Fx
  GPU Radeon

  Very frequently, Gnome-shell crashes and difficult to understand why
  or when.

  Example : open a Libreoffice Calc file ; export it twice in PDF format on the 
Desktop. Right-click on this files icons on the desktop to delete them : for 
the 2nd, the screen becomes black (I can do nothing) and after about 20 s, I 
get the login screen.
  I exported the journal file (attached file) (and the session crashes again) 
because the system says nothing !

  Doesn't happen with X session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907904/+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 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions

[Daniel van Vugt]

** Also affects: mutter (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

** Also affects: gnome-shell (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Invalid

** No longer affects: gnome-shell (Ubuntu Hirsute)

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Input device settings not applied on hotplug/reconnect/resume in Xorg
  sessions

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  Mutter 3.36.2 breaks custom input settings

  [ Test case ]

  - Set custom settings using gnome-control-center (set custom Delay and
Speed in Settings > Accessibility > Repeat Keys) or gnome-tweaks (under
Additional Layout options)
  - Unplug / replug the input device or suspend / resume
  - Input device settings should be preserved

  [ Regression potential ]

  Devices added or removed may be not noticed by gnome-shell.

  ---

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

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

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

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

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

  Thanks!

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1899206/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Leslie Li]

This also affects me. Just thought I'd put a comment in the hope that
this will be fixed soon. Fingers crossed!

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

Title:
  [nvidia] Screen scaling 125% gives 200%

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

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1762595] Re: Thunar incorrectly thinks USB storage device hasn't finished ejecting

[Marvin]

This issue is still affecting my both operating systems, Ubuntu 20.04
and Ubuntu Studio 20. What should I do to fix it?

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

Title:
  Thunar incorrectly thinks USB storage device hasn't finished ejecting

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Released
Status in gvfs package in Arch Linux:
  Fix Released

Bug description:
  [Impact]

   * This bug affects Thunar, and likely other file managers relying on
  udisks2.

   * When ejecting a USB disk, the disk ejects normally. However, Thunar
  does not detect that it was successfully ejected.

   * The "Writing data to device" notification will be displayed for
  some time.

   * Eventually, Thunar pops up an error dialog saying 'Failed to eject
  "". Timeout was reached.'

   * Thunar will sometimes also exit at this point.

   * It has been determined that the upstream patch included in this
  upload resolves this error.

  [Test Case]

   1. Mount a partition of a USB hard disk or flash drive.

   2. Using the eject button in the Thunar window sidebar, eject the
  mounted partition of the USB HDD.

   3. The disk will spin down and eject normally. The "Writing data to
  device" notification will be displayed until  an error dialog saying
  'Failed to eject "". Timeout was reached.'

  [Regression Potential]

   * Regression potential is very minimal. The patch is from upstream
  gvfs, contains a single line change, and applies only to the drive
  stopping event.

  [Original Report]
   
  $ lsb_release -rd
  Description: Ubuntu 18.04 LTS
  Release: 18.04

  $ apt-cache policy thunar
  thunar:
Installed: 1.6.15-0ubuntu1
Candidate: 1.6.15-0ubuntu1
Version table:
   *** 1.6.15-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce:

  1) Mount a partition of a USB harddisk

  2) Using the eject button in the Thunar window sidebar, eject the
  mounted partition of the USB HDD.

  3) After the USB HDD is ejected and spins down, unplug it
  .

  At (2), the disk ejects normally. But Thunar thinks it hasn't been
  ejected and is still trying to eject. The "Writing data to device"
  notification continues to display. Eventually, Thunar pops up an error
  dialog saying 'Failed to eject "". Timeout was
  reached.' Sometimes Thunar will exit after this.

  Same thing happens with some USB flash drives, so the bug can also be
  tested with a pendrive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1762595/+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 1910235] Re: The mouse stops working after taking a screenshot

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1910235

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  The mouse stops working after taking a screenshot

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce this bug:

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mouse in other applications besides browser (in my case Slack)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910235/+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 1909944] Re: Dell XPS 13 Synaptics touch screen does not work after boot but will work after resume from sleep?

[Daniel van Vugt]

Please try selecting 'Ubuntu on Wayland' on the login screen, just
before you enter your password. Does the touch screen work any better in
a Wayland session?


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

** Summary changed:

- Dell XPS 13 Synaptics touch screen does not work after boot but will work 
after resume from sleep?
+ Dell XPS 13 9333 Synaptics touch screen does not work after boot but will 
work after resume from sleep?

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

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

Title:
  Dell XPS 13 9333 Synaptics touch screen does not work after boot but
  will work after resume from sleep?

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I freshly installed Ubuntu 20.10 and noticed that the touch screen
  does not work. Tried xinput --list and then xinput disable/enable
  [correct-id] but with no avail.

  However, if I close the laptop lid and open it, after the system
  resumes from sleep, the touch screen starts working.

  BUT, another anomaly happens, this could not necessarily be after the
  1st resume from sleep, it could be the 2nd+ ---> the "Windows" key on
  the keyboard stops working? So, I can't start apps by type and search?
  And when this happens, the whole screen sometimes freezes and becomes
  unresponsive ex. moving around the mouse (synaptic touch pad and not
  touchscreen), no matter where I click, no reaction... I tried
  CTRL+ALT+F1 then switch back and somehow it started working again? It
  also happened, that the synaptic touch pad was not moving the mouse
  cursor on the screen (and the mouse cursor just disappeared)? Luckily,
  the keyboard was still reacting for the CTRL+ALT+T and the terminal
  window showed up, from where I used sudo modprobe -r psmouse and then
  sudo modprobe psmouse and also xinput disable/enable [touch-pad-id]
  and it got back to work.

  Many things happen in this one bug it seems?

  NOTE: when running 20.10 from USB (Live CD), then the touchscreen
  works perfectly! Only after install do these anomalies happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 22:55:01 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2021-01-01 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS13 9333
  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-5.8.0-33-generic 
root=UUID=fe6e5482-378f-4c13-9039-8b11eba4af45 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:br0.1:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1909944/+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 1905186] Re: dock and top bar flashing non-stop at fullscreen

[Daniel van Vugt]

It's not surprising this bug would only affect Xorg sessions because
only Xorg sessions supported the fullscreen unredirect optimization,
until recently.

** No longer affects: xorg (Ubuntu)

** Summary changed:

- dock and top bar flashing non-stop at fullscreen
+ dock and top bar flashing non-stop at fullscreen in Xorg sessions

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

Title:
  dock and top bar flashing non-stop at fullscreen in Xorg sessions

Status in gnome-shell-extension-autohidetopbar package in Ubuntu:
  New
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  
  This problem affects all extensions that alter the dock and top bar. 
Including the standard extension "Ubuntu dock". All extensions are duly updated 
to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-autohidetopbar/+bug/1905186/+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 1909496] Re: [i915] Blinking unlock screen

[Daniel van Vugt]

** Summary changed:

- Blinking login screen
+ [i915] Blinking unlock screen

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

Title:
  [i915] Blinking unlock screen

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

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909496/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

[Launchpad Bug Tracker]

[Expired for xf86-video-armsoc (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xf86-video-armsoc (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  Expired
Status in xf86-video-armsoc package in Ubuntu:
  Expired

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  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: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  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 N/A
  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/mesa/+bug/1902652/+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 1902652] Re: [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

[Launchpad Bug Tracker]

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

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

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

Title:
  [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow

Status in mesa package in Ubuntu:
  Expired
Status in xf86-video-armsoc package in Ubuntu:
  Expired

Bug description:
  3d rendering is very slow, also when surfing the internet, webpages
  take a while to render. Internet access is not the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.19.64+ aarch64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: arm64
  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: XFCE
  Date: Tue Nov  3 05:42:00 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  Lspci:
   
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ 
root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet 
splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
Identifier  "Allwinner sun4i DRM driver"
Driver  "armsoc"
Option  "DRI2"  "true"
   EndSection
  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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  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 N/A
  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/mesa/+bug/1902652/+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