[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Mikko Pohja]

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

Same issue here with Bose QC35 II and Thinkpad X1 Extreme (2nd gen).
Audio profile works just fine, but headset does not play any sound and the 
microphone does not get any input. It was like this already in April and 
currently on a fresh install of 20.04.

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

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

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

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

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

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

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

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

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

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

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

  Headset: Sennheiser HD 4.50 BTNC

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

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

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

[Coiby Xu]

Although Elan Touchpad is listed in the output of xinput, "0" in
"hid_elan 16384 0" shows hid_elan is not being used. Is there an entry
named "*:04F3:3140.*" under /sys/bus/hid/drivers/hid-elan/?

> plus I found that this device is already defined in hid-elan.c

I couldn't find the string 0x3140. Do you mean the device is defined in
another way?


Yesterday, I used evtest to monitor the Synaptics touchpad and was
surprised to find when hid_multitouch is taking over the device,
multiple fingers (up to 4) touching could be detected,

```
$ sudo evtest
/dev/input/event14: MSFT0001:00 06CB:7F28 Mouse
/dev/input/event15: MSFT0001:00 06CB:7F28 Touchpad
Select the device event number [0-21]: 15
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x6cb product 0x7f28 version 0x100
Input device name: "MSFT0001:00 06CB:7F28 Touchpad"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 272 (BTN_LEFT)
Event code 325 (BTN_TOOL_FINGER)
Event code 328 (BTN_TOOL_QUINTTAP)
Event code 330 (BTN_TOUCH)
Event code 333 (BTN_TOOL_DOUBLETAP)
Event code 334 (BTN_TOOL_TRIPLETAP)
Event code 335 (BTN_TOOL_QUADTAP)
  Event type 3 (EV_ABS)
Event code 0 (ABS_X)
  Value  0
  Min0
  Max 1224
  Resolution  12
Event code 1 (ABS_Y)
  Value  0
  Min0
  Max  804
  Resolution  12
Event code 47 (ABS_MT_SLOT)
  Value  0
  Min0
  Max4
Event code 53 (ABS_MT_POSITION_X)
  Value  0
  Min0
  Max 1224
  Resolution  12
Event code 54 (ABS_MT_POSITION_Y)
  Value  0
  Min0
  Max  804
  Resolution  12
Event code 55 (ABS_MT_TOOL_TYPE)
  Value  0
  Min0
  Max2
Event code 57 (ABS_MT_TRACKING_ID)
  Value  0
  Min0
  Max65535
  Event type 4 (EV_MSC)
Event code 5 (MSC_TIMESTAMP)
Properties:
  Property type 0 (INPUT_PROP_POINTER)
  Property type 2 (INPUT_PROP_BUTTONPAD)
Testing ... (interrupt to exit)
Event: time 1597225994.180980, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), 
value 0
Event: time 1597225994.180980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 765
Event: time 1597225994.180980, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 220
Event: time 1597225994.180980, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1597225994.180980, type 1 (EV_KEY), code 325 (BTN_TOOL_FINGER), 
value 1
Event: time 1597225994.180980, type 3 (EV_ABS), code 0 (ABS_X), value 765
Event: time 1597225994.180980, type 3 (EV_ABS), code 1 (ABS_Y), value 220
Event: time 1597225994.180980, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 0
Event: time 1597225994.180980, -- SYN_REPORT 
```

The only issue is the pointer won't move when I my fingers move on the
touchpad. Compared with a working touchpad, the only difference is the
lack of ABS_PRESSURE events. If I use hid-rmi, these ABS_PRESSURE events
would be generated. It seems ABS_PRESSURE events are needed to make the
pointer move. If I could let hid_multitouch collect ABS_PRESSURE events,
then the touchpad could work.


So I'm curious if hid_multitouch also handle your touchpad device by default, 
could you run `sudo evtest` on the device to see what kinds of events could be 
generated?

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ V

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[CGeng]

On Ubuntu 20.04, I have similar problem. Actually, I met this problem
since 19.10, however in 19.04, it was fine.

My default GUI env is GNOME, and I switched to KDE recently but the
problem still occur sometimes.

This problem is a little bit different from other people in these
aspects.

1. This problem not only happen in gnome-shell. it happens almost every
where, especially when you type in a textbox. For example, in chrome and
pycharm, I met the similar problem. Which indicates that this bug is a
general problem.

2. When my keyboard is freezing, I cannot type in the TEXTBOX. however,
other part of keyboard still work such as Capslock and Super(Meta)
button etc. Simply speaking, when the keyboard is freezing, I can still
push META button to present all windows, however I CANNOT type anything
to input in the TEXTBOX.

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

Title:
  Occasional Keyboard freeze

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/907

  ---

  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1734541] Re: encrypted home-directory is not unmounted on logout

[Dave J]

Note this was also reported in bug 1637710 back in 2016

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

Title:
  encrypted home-directory is not unmounted on logout

Status in gnome-session:
  New
Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Debian:
  New

Bug description:
  Current Situation:

  If you log out from an user account with an encrypted home directory,
  it is not automatically unmounted and encrypted again.

  Expected behaviour:

  If I log out from an user account with an encrypted home directory, Id expect 
the homedir to be unmounted and encrypted again.
  Stepts to reproduce:

  log into an account with encrypted home directory. (lets call it: user)
  Log out again
  log into another account (which has sudo rights, lets call it: user2)

  and now enter the following into a terminal:

  user2@ubuntu: sudo su
  user2@ubuntu: ls -la /home/user

  you can see the files of the user

  Reasons:
  This is a security issue, because as a user you can reasonable expect your 
data to be safe, if you log out. if you would simply log in as another user but 
keep your data accessable you would simply switch user, instead of loggin out.
  Many users only suspend their laptop while carrying it with them. Logging out 
and suspending the user expects to have at least the home directory encrypted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 16:18:39 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1734541/+subscriptions

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

[Desktop-packages] [Bug 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)

[Daniel van Vugt]

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

Yes, regressions can occur multiple times (sadly) and/or can be observed
in different circumstances with multiple different root causes.

I agree we're now talking about a regression that occurred after Ubuntu
18.04 but it's not worth starting a new upstream bug when they already
know about it, and continued to acknowledge it in the past year.

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

Title:
  Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Double-clicking a window title-bar now fully-maximizes the window,
  even though the action is set to "Toggle Maximize Vertically" or
  "Toggle Maximize Horizontally".

  In other words, those options now behave just like "Toggle Maximize".

  This problem started after I upgraded from Ubuntu 18.10 (gnome-shell
  3.30?) to Ubuntu 19.04 (gnome-shell 3.32.1).

  STEPS TO REPRODUCE:

  1. Run gnome-tweaks
  2. Click "Window Titlebars" in left menu panel
  3. Set "Titlebar Actions ... Double-Click" to "Toggle Maximize Vertically"
  4. Double-click a gnome-terminal titlebar

  RESULTS: WIndow maximizes fully (fills entire screen)

  EXPECTED RESULTS: Maximize in vertical direction only.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 22:53:16 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-05 (477 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-07-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language

[Amirhosein Rahmati]

** Description changed:

  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.
  
- Such as "آقوست" for August and "جومعه آخشامی" for Friday.
+ Such as "آقوست" for August and "جومعه آخشامی" for Thursday.
  
- But it should show in Iranian names such as "اوت" for August and "جمعه"
- for Friday.
+ But it should show in Iranian names such as "اوت" for August and
+ "پنجشنبه" for Thursday.
  
  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

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

Title:
  Iranian calendar shows in Azerbaijani language

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

  Such as "آقوست" for August and "جومعه آخشامی" for Thursday.

  But it should show in Iranian names such as "اوت" for August and
  "پنجشنبه" for Thursday.

  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

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

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

[Desktop-packages] [Bug 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)

[jimav]

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

Something is strange here: That upstream bug is 5+ years old, yet this
problem appeared in Ubuntu at most 3 years ago (vertical resize worked
in Ubuntu 18.10)

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

Title:
  Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Double-clicking a window title-bar now fully-maximizes the window,
  even though the action is set to "Toggle Maximize Vertically" or
  "Toggle Maximize Horizontally".

  In other words, those options now behave just like "Toggle Maximize".

  This problem started after I upgraded from Ubuntu 18.10 (gnome-shell
  3.30?) to Ubuntu 19.04 (gnome-shell 3.32.1).

  STEPS TO REPRODUCE:

  1. Run gnome-tweaks
  2. Click "Window Titlebars" in left menu panel
  3. Set "Titlebar Actions ... Double-Click" to "Toggle Maximize Vertically"
  4. Double-click a gnome-terminal titlebar

  RESULTS: WIndow maximizes fully (fills entire screen)

  EXPECTED RESULTS: Maximize in vertical direction only.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 22:53:16 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-05 (477 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-07-26 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Stefano Galassi]

but elan_i2c is not automatically loaded and even loading it manually
doesn't make any difference

if I blacklist i2c_hid, as proposed in other forums for issues with elan
touchpads, the touchpad even disappears from xinput devices

running out of options..

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1891313] Re: Xorg crash

[Daniel van Vugt]

At first I thought this might be boot failure bug 1872159. To test that,
just try removing the 'splash' kernel parameter. But maybe that's not
the problem...

I can see another problem; that your Nvidia driver is not only an
unsupported version, but it's also not installed properly. This seems to
be resulting in the open source driver running the Nvidia GPU when it
shouldn't.

So this bug is invalid for now. Please uninstall the Nvidia driver you
have and use the 'Additional Drivers' app to install the supported
version 440.

If you encounter any problems after that then please open new bugs for
them. Also, if you find any evidence of crashes in /var/crash then
please use the 'ubuntu-bug' command to turn those into new bugs.

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

** Summary changed:

- Xorg crash
+ [nvidia] Xorg crash

** Tags added: nvidia

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

Title:
  [nvidia] Xorg crash

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have a ACER Nitro 5 NVIDIA GTX 1650 Mobile with Ubuntu 20.04
  instated and i tryed to boot my notebook with a second monitor plugged
  by HDMI port. Now, my internal monitor can't be recognized and its
  crashing on the initial load screem. They can load only whit the HDMI
  is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.51.06  Sun Jul 19 
20:02:54 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 12 07:55:04 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 450.51.06, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1331]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1332]
  InstallationDate: Installed on 2020-08-05 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
   Bus 001 Device 002: ID 1a2c:0043 China Resource Semico Co., Ltd USB Mouse
   Bus 001 Device 004: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-54
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b286d151-6958-4e94-8f2b-2af178b1dc88 ro vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.30
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Octavia_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.30
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.30
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-54
  dmi.product.sku: 
  dmi.product.version: V1.30
  dmi.sys.vendor: Acer
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19

[Desktop-packages] [Bug 1870822] Re: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell crashed with assertion failure
  window.c:1552:meta_window_unmanage: assertion failed:
  (window->display->focus_window != window)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  just what I said in the title, the gnome user interface hung for a
  minute or so, after pressing 'x' to close a terminal window...

  been having other issues with the gnome-shell, in this ubuntu beta,
  this is new.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 18:40:19 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-04-03 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.so.0
   () at /lib/x86_64-linux-gnu/libmutter-6.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/+bug/1870822/+subscriptions

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

[Desktop-packages] [Bug 1891401] Re: gnome-shell crashed with SIGABRT in __GI_raise(), and the screen turned black and I was thrown to the Home Screen as a result

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1791574
   gnome-shell crashed with SIGABRT: assertion failed 
"window->display->focus_window != window" in meta_window_unmanage

** This bug has been marked a duplicate of bug 1870822
   gnome-shell crashed with assertion failure 
window.c:1552:meta_window_unmanage: assertion failed: 
(window->display->focus_window != window)

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise(), and the screen
  turned black and I was thrown to the Home Screen as a result

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happens whenever I use my computer unfortunately.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  3 12:00:21 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1591381250
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-07-06 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/seija
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Stefano Galassi]

plus I found that this device is already defined in hid-elan.c, thus it
should be recognized as elan touchpad using elan_i2c module..

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

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

[Stefano Galassi]

no luck man..
now I've got a hid_elan module loaded, but touchpad is still dead:


hid_magicmouse 20480  0
hidp   32768  1
bluetooth 737280  38 btrtl,hidp,btintel,btbcm,bnep,btusb,rfcomm
hid_elan   16384  0
led_class  20480  4 input_leds,iwlmvm,hid_elan,snd_hda_codec_realtek
i2c_hid32768  0
hid_generic16384  0
usbhid 65536  0
hid   147456  6 
i2c_hid,hidp,usbhid,hid_elan,hid_generic,hid_magicmouse
usbcore   335872  5 xhci_hcd,usbhid,uvcvideo,btusb,xhci_pci


and output of xinput:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ AKKO AKKO 3084BT Wireless Radio Control   id=12   [slave  pointer  (2)]
⎜   ↳ AKKO AKKO 3084BT Consumer Control id=13   [slave  pointer  (2)]
⎜   ↳ iTrobPad  id=15   [slave  pointer  (2)]
⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control  id=17   [slave  pointer 
 (2)]
⎜   ↳ MSFT0001:00 04F3:3140 id=20   [slave  pointer  (2)]
⎜   ↳ Elan Touchpad id=21   [slave  pointer  (2)]


both pointer devices with id 20 and 21 don't receive any event on their
respective /dev/input/event*

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(c

[Desktop-packages] [Bug 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu

[hatsune]

** Description changed:

  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.
  
  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter
  
  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
-   DeviceName: Realtek PCIe FE Family Controller
-   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
-   Kernel driver in use: r8169
-   Kernel modules: r8169
+  DeviceName: Realtek PCIe FE Family Controller
+  Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
+  Kernel driver in use: r8169
+  Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
-   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
-   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter
-   Kernel driver in use: rtl8723be
-   Kernel modules: rtl8723be
+  DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
+  Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
+  Kernel driver in use: rtl8723be
+  Kernel modules: rtl8723be
  
  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
- No network related change had made (IPv6 disabled through settings)
+ No network related change has made (IPv6 disabled through settings)
+ Only one SSID is in use: Dialog 4G
  
  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
   DeviceName: Realtek PCIe FE Family Controller
   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
   Kernel driver in use: r8169
   Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter
   Kernel driver in use: rtl8723be
   Kernel modules: rtl8723be

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change has made (IPv6 disabled through settings)
  Only one SSID is in use: Dialog 4G

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+subscriptions

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

[Desktop-packages] [Bug 1891407] Re: [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu

[hatsune]

** Description changed:

  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.
+ 
+ [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
+ PCIe Wireless Network Adapter
+ 
+ [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
+ 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
+   DeviceName: Realtek PCIe FE Family Controller
+   Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
+   Kernel driver in use: r8169
+   Kernel modules: r8169
+ 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
+   DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
+   Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter
+   Kernel driver in use: rtl8723be
+   Kernel modules: rtl8723be
  
  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change had made (IPv6 disabled through settings)
  
  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  [lspci]Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE
  PCIe Wireless Network Adapter

  [lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %]
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 0a)
DeviceName: Realtek PCIe FE Family Controller
Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet 
controller
Kernel driver in use: r8169
Kernel modules: r8169
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
DeviceName: Realtek Sanji2 RTL8723BE b/g/n 1x1 + BT 4 LE PCIe+USB M.2
Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter
Kernel driver in use: rtl8723be
Kernel modules: rtl8723be

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change had made (IPv6 disabled through settings)

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+subscriptions

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

[Desktop-packages] [Bug 1891407] [NEW] [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and better uninstall ubuntu

[hatsune]

Public bug reported:

Ubuntu 20.04.01 LTS (newly installed)
(Moved that device from windows 10, didnt had issue in it)
HP 15T-au000 device.

Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
No network related change had made (IPv6 disabled through settings)

I ran `journalctl --follow` and below is the log. let me know if
required to provide further details

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

Title:
  [journalctl --follow] Wi-Fi auto disconnect randomly, unable fix and
  better uninstall ubuntu

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.01 LTS (newly installed)
  (Moved that device from windows 10, didnt had issue in it)
  HP 15T-au000 device.

  Wi-Fi key is correct (i can use internet to visit sites, watch videos in 
youtube etc) however randomly disconnect and appear window to re-connect 
(sometimes constantly disconnect)
  No network related change had made (IPv6 disabled through settings)

  I ran `journalctl --follow` and below is the log. let me know if
  required to provide further details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891407/+subscriptions

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

[Desktop-packages] [Bug 1891221] Re: libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders

[Jan Claeys]

One can specify an alternative path, but it would be nice if the fact
that the tool was relocated to a non-default (or at least not-in-$PATH)
location was documented somewhere…

(Neither its manpage nor the other gdk-pixbuf documentation seems to
mention that.)

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

Title:
  libgdk-pixbuf2.0-bin package does not contain gdk-pixbuf-query-loaders

Status in gdk-pixbuf package in Ubuntu:
  Invalid

Bug description:
  Because EOG can't show webp images by default I tried to build
  https://github.com/aruiz/webp-pixbuf-loader but it complains that it
  can't find the 'gdk-pixbuf-query-loaders' tool it needs.

  I assume it should be in the 'libgdk-pixbuf2.0-bin' package, as that
  does contain a manpage for it, but not the tool itself?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891221/+subscriptions

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

[Desktop-packages] [Bug 1891338] Re: apparmor misconfigured for envice

[Seth Arnold]

Hello Kenneth, can you please include the DENIED lines from dmesg
output, /var/log/syslog, or /var/log/audit/audit.log ?

Thanks

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

Title:
  apparmor misconfigured for envice

Status in evince package in Ubuntu:
  New

Bug description:
  On a fully up to date xubuntu 20-04 system, when i run evince and
  click on a link, it fails to follow that link in my browser. This kind
  of thing happens when you are reading a technical paper and want to
  follow one of the references and click on the doi or url.

  When i click on the link i get a box that i cannot copy from that says:
  Failed to launch preferred application for category "WebBrowser".

  Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
  /exo-helper-2"(Permission denied).

  Did I say that it is annoying that i could not copy the text in this
  box!!

  The output of the ldd command you asked for is attached.

  I should also point out that this worked fine under xubuntu 18.04.

  I had originally posted this as an additional comment on
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
  but https://launchpad.net/~seb128 said that I should submit this as a
  separate bug because this is likely an apparmor configuration problem
  that is similar to the ancient bug
  https://bugs.launchpad.net/bugs/987578.

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

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

[Desktop-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Kuroš Taheri-Golværzi]

Just checked both my other (unaffected) drives. Neither Manjaro nor
CentOS have that line in the `/etc/pulse/default.pa` file. I used the
/ search in Less with the word "switch", and that line wasn't in
either of them.

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
  07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 19)
  07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 0a)
  07:05.3 System peripheral: Ricoh Co

[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

[Alan Pope 🍺🐧🐱 🦄]

I added a workaround to the askubuntu post.
https://askubuntu.com/a/1266706/612

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions

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

[Desktop-packages] [Bug 1889052] Re: 20.10: vlc crashes with seg fault when a video should be played

[Sebastian Ramacher]

** Package changed: vlc (Ubuntu) => mesa (Ubuntu)

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

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

Title:
  20.10: vlc crashes with seg fault when a video should be played

Status in mesa package in Ubuntu:
  New

Bug description:
  When I try to play "any" video vlc crashes with a seg fault.

  Tested: 
  - mkv + h.264
  - mp4 + h.264
  - wmv

  Maybe it's a good idea to choose a different vlc release for the
  repos?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vlc 3.0.9.2-1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jul 27 17:27:42 2020
  SourcePackage: vlc
  UpgradeStatus: Upgraded to focal on 2020-07-24 (3 days ago)

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

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

[Desktop-packages] [Bug 1889052] [NEW] 20.10: vlc crashes with seg fault when a video should be played

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I try to play "any" video vlc crashes with a seg fault.

Tested: 
- mkv + h.264
- mp4 + h.264
- wmv

Maybe it's a good idea to choose a different vlc release for the repos?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.9.2-1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon Jul 27 17:27:42 2020
SourcePackage: vlc
UpgradeStatus: Upgraded to focal on 2020-07-24 (3 days ago)

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


** Tags: amd64 apport-bug focal
-- 
20.10: vlc crashes with seg fault when a video should be played
https://bugs.launchpad.net/bugs/1889052
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mesa in Ubuntu.

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

[Desktop-packages] [Bug 1891401] Re: gnome-shell crashed with SIGABRT in __GI_raise(), and the screen turned black and I was thrown to the Home Screen as a result

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1791574
   gnome-shell crashed with SIGABRT: assertion failed 
"window->display->focus_window != window" in meta_window_unmanage

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise(), and the screen
  turned black and I was thrown to the Home Screen as a result

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happens whenever I use my computer unfortunately.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  3 12:00:21 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1591381250
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-07-06 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/seija
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
  
  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
  
  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).
  
  In general, the regression risks here are:
  - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
  - differences in dpkg and/or debhelper behavior in older ubuntu releases 
leading to unexpected results (should be covered by the test cases from this 
SRU)
  - xenial in particular is trickier, because src:base-files there does NOT use 
debhelper, so many of the things we take for granted have to be done by hand
  - have some sort of dpkg postinst or dependency error because of unpredicted 
scenarios. Certain assumptions are being made, like the renames that 
dpkg-maintscript-helper does, and that the filename 
/etc/default/motd-news.wasremoved that I'm touching and verifying is really 
mine and not something that was there already.
  - the versions 

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
  
  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
  
  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
- This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded, there will be a /e/d/motd-news.wasremoved leftover 
empty file (see "other info" below for details).
+ This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded and /e/d/motd-news was manually removed by the user, 
there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" 
below for details).
  
  In general, the regression risks here are:
  - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
  - differences in dpkg and/or debhelper behavior in older ubuntu releases 
leading to unexpected results (should be covered by the test cases from this 
SRU)
  - xenial in particular is trickier, because src:base-files there does NOT use 
debhelper, so many of the things we take for granted have to be done by hand
  - have some sort of dpkg postinst or dependency error because o

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
  
  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled
  
  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification
  
  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled
  
  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled
  
  e) removing motd-news-config will also remove ubuntu-server (since it's
  a depends, and not a recommends)
  
  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files
  
  g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
  news-server removes the /e/d/motd-news config file
  
  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0
  
  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled
  
  [Regression Potential]
+ This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
+ a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.
+ 
+ b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
+ This was trickier to handle, and we do it in base-files's postinst and 
motd-news-config's  postinst. The drawback is that in one scenario, where just 
base-files is upgraded, there will be a /e/d/motd-news.wasremoved leftover 
empty file (see "other info" below for details).
+ 
+ In general, the regression risks here are:
+ - have motd-news enabled again on a system where it was previously disabled. 
We tried to envision two ways it would have been disabled (set ENABLED=0, and 
remove the config file). There are probably others
+ - differences in dpkg and/or debhelper behavior in older ubuntu releases 
leading to unexpected results (should be covered by the test cases from this 
SRU)
+ - xenial in particular is trickier, because src:base-files there does NOT use 
debhelper, so many of the things we take for granted have to be done by hand
+ - have some sort of dpkg postinst or dependency error because of unpredicted 
scenarios. Certain assumptions are being made, like the renames that 
dpkg-maintscript-helper does, and that the filename 
/etc/default/motd-news.wasremoved that I'm touching and verifying is really 
mine and not something that was there already.
+ - the versions I'm breaking/replacing on, and using rm_conffiles on,

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Andreas Hasenack]

** Description changed:

- The motd-news script is largely useless for desktop users, as they
- rarely login via a text console. It makes more sense for server users.
+ [Impact] 
+ The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
  - have ubuntu-server depend on motd-news-config (or recommends)
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config
  
  Care must be taken to preserve a changed /etc/default/motd-news when the
  upgrade installs the new motd-news-config package. For example, on a
  server that has set ENABLED=0 in /etc/default/motd-news and upgrades to
  the new base-files and ubuntu-server, and gets the new motd-config-news
  package, ENABLED=0 must remain set.
+ 
+ [Test Case]
+ a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
+ apt install base-files
+ - upgrades ubuntu-server
+ - installs motd-news-config
+ - /e/d/motd-news remains, motd-news remains enabled
+ 
+ b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
+ apt install base-files
+ - upgrades ubuntu-server
+ - installs motd-news-config
+ - /e/d/motd-news remains with the original modification
+ 
+ c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
+ apt install base-files
+ - upgrades base-files
+ - removes /e/d/motd-news
+ - motd-news is disabled
+ 
+ d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
+ apt install base-files
+ - upgrades base-files
+ - /e/d/motd-news gets renamed to backup
+ - motd-news is disabled
+ 
+ e) removing motd-news-config will also remove ubuntu-server (since it's
+ a depends, and not a recommends)
+ 
+ f) upgrading just ubuntu-server should pull motd-news-config in, and
+ force-upgrade base-files
+ 
+ g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-
+ news-server removes the /e/d/motd-news config file
+ 
+ h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
+ - apt install base-files
+ - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
+ - /e/d/motd-news is installed with ENABLED=0
+ 
+ i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
+ - apt install base-files
+ - base-files is upgraded
+ - no /e/d/motd-news is installed, motd-news remains disabled
+ 
+ [Regression Potential]
+ 
+ 
+ [Other Info]
+ 
+ Testcase (i) will leave around an empty /etc/default/motd-news.wasremoved 
file, created by the base-files postinst. This file is removed by the 
motd-news-config postinst, but since that package doesn't get installed in that 
particular scenario, the file remains. I toyed with the idea of adding an extra 
check to base-file's postinst, like this:
+ --- a/debian/postinst.in
+ +++ b/debian/postinst.in
+ @@ -133,7 +133,11 @@ motd_news_config="/etc/default/motd-news"
+  if [ ! -e ${motd_news_config} ]; then
+if [ ! -e ${motd_news_config}.dpkg-remove ]; then
+  if [ ! -e ${motd_news_config}.dpkg-backup ]; then
+ -  touch ${motd_news_config}.wasremoved
+ +  # The .wasremoved file only matters if ubuntu-server is installed,
+ +  # because that's what will pull in motd-news-config
+ +  if dpkg -l ubuntu-server 2>/dev/null | grep -q ^i; then
+ +touch ${motd_news_config}.wasremoved
+ +  fi
+  fi
+fi
+  fi
+ 
+ But deemed it too risky, and not worth further potential regressions.

** Description changed:

- [Impact] 
+ [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.
  
  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
- - move /etc/default/motd-news from base-files into a NEW package 
(motd-news-config)
- - have ubuntu-server depend on motd-news-config (or recommends)
- - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends (or recommends) on motd-news-config
+ - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
+ - have ubuntu-server depend on motd-news-config
+ - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-con

[Desktop-packages] [Bug 1891373] [NEW] package chromium-browser (not installed) failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a rem

[MohammadHosein Arasteh]

Public bug reported:

I was trying to install chromium browser using atp, the progress bar was
stuck at 20% for a long while, so I forced closed the Terminal. I tried
again to install chromium but I faced with many errors. I've used some
of the solves that I found by searching web, such as removing package
and redownload it, reconfiguring atp and atp-get etc. but I hadn't any
progress!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
AptOrdering:
 chromium-browser:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Aug 12 12:08:24 2020
DpkgTerminalLog:
 dpkg: error processing package chromium-browser (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2020-08-11 (1 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: chromium-browser
Title: package chromium-browser (not installed) failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting a removal

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was trying to install chromium browser using atp, the progress bar
  was stuck at 20% for a long while, so I forced closed the Terminal. I
  tried again to install chromium but I faced with many errors. I've
  used some of the solves that I found by searching web, such as
  removing package and redownload it, reconfiguring atp and atp-get etc.
  but I hadn't any progress!

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  AptOrdering:
   chromium-browser:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Aug 12 12:08:24 2020
  DpkgTerminalLog:
   dpkg: error processing package chromium-browser (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2020-08-11 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1891373/+subscriptions

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

[Desktop-packages] [Bug 1065126] Re: "Always do this from now on" does not work

[Rüdiger Kupper]

I gave up on Firefox. Switched to Chromium instead. I'm sorry, but you
need to take action at some time (and time means: 7 years and 10 months
since I reported this). I hope the Firefox community can work this out,
I am not longer part of it.

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

Title:
  "Always do this from now on" does not work

Status in Mozilla Firefox:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Downloading an unknown file type in Firefox displays a dialog for choosing 
which application to use for opening the file.
  The dialog contains a check box labelled "Always do this action from now on".
  Checking this option does not work: When I download a file of the same type 
next time, the same dialog is displayed again.

  This feature is broken for as long as I can remember (> 10 years).
  It's time it was fixed (or removed).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 15.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
  Uname: Linux 3.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruediger   2536 F pulseaudio
  BuildID: 20120907231657
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49'
     Mixer name : 'Analog Devices AD1984'
     Components : 'HDA:11d41984,17aa20bb,00100400'
     Controls  : 32
     Simple ctrls  : 20
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
     Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Channel: Unavailable
  Date: Wed Oct 10 18:17:44 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  IpRoute:
   default via 172.31.0.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   172.31.0.0/20 dev wlan0  proto kernel  scope link  src 172.31.9.26  metric 2
  MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
   icedtea-6-plugin  1.2-2ubuntu1.2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 6457BBG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6457BBG
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions

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

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

why did you tag the report*

Bump.

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

[Alex A. D.]

Hi Sebastien. Thaks your for your reply.

I suggest you to do the following to see that even if file is starting
with proper tags it is recognized as `application/x-perl`:

$ tee "index.html" <
use strict
eol

$ xdg-mime query filetype index.html # -> application/x-perl - wrong
type

Why did you tagged report as invalid? 
I just got a file with minified JS code which has `use strict` burrowed deep 
somewhere inside correct html file but it's still recognized as perl script.

I can't use some tools to open the file in browser by using xdg-open and
forced to use browser-specific launcher.

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1891270] Re: Iranian calendar shows in Azerbaijani language

[Brian Murray]

** Project changed: apport => gnome-calendar (Ubuntu)

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

Title:
  Iranian calendar shows in Azerbaijani language

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
  After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

  Such as "آقوست" for August and "جومعه آخشامی" for Friday.

  But it should show in Iranian names such as "اوت" for August and
  "جمعه" for Friday.

  Description: Ubuntu 20.04.1 LTS
  Release: 20.04

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

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

[Desktop-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

[Sebastien Bacher]

the package has been removed from the archive which resolves the issue

** Changed in: evolution-indicator (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Committed
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Confirmed

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

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

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

[Desktop-packages] [Bug 1891270] [NEW] Iranian calendar shows in Azerbaijani language

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I already installed Ubuntu 20.04.1 LTS  and set location on Iran during 
installation.
After finishing installation successfully, I open the calendar by clicking at 
the top of the screen (where the clock is shown), I see the calendar with 
Azerbaijani names for month and weekdays.

Such as "آقوست" for August and "جومعه آخشامی" for Friday.

But it should show in Iranian names such as "اوت" for August and "جمعه"
for Friday.

Description: Ubuntu 20.04.1 LTS
Release: 20.04

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

-- 
Iranian calendar shows in Azerbaijani language
https://bugs.launchpad.net/bugs/1891270
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-calendar in Ubuntu.

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

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

[Coiby Xu]

Sorry I made another mistake. hid_rmi is specifically for the Synaptics
RMI4 touchpads. We use let hid_elan handle this device. The
vendor&product id should be added to elan_devices in drivers/hid/hid-
elan.c. Can you give the following patch a try?

diff --git a/drivers/hid/hid-elan.c b/drivers/hid/hid-elan.c
index 45c4f888b7c4..0cf427a94897 100644
--- a/drivers/hid/hid-elan.c
+++ b/drivers/hid/hid-elan.c
@@ -525,6 +525,7 @@ static const struct hid_device_id elan_devices[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_ELAN, USB_DEVICE_ID_HP_X2_10_COVER),
  .driver_data = ELAN_HAS_LED },
{ HID_I2C_DEVICE(USB_VENDOR_ID_ELAN, USB_DEVICE_ID_TOSHIBA_CLICK_L9W) },
+   { HID_I2C_DEVICE(USB_VENDOR_ID_ELAN, 0x3140) },
{ }
 }

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

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

[Desktop-packages] [Bug 1891345] [NEW] Update to 3.37.90

[Marcus Tomlinson]

Public bug reported:

Update to 3.37.90

** Affects: orca (Ubuntu)
 Importance: Wishlist
 Assignee: Marcus Tomlinson (marcustomlinson)
 Status: New


** Tags: upgrade-software-version

** Changed in: orca (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  Update to 3.37.90

Status in orca package in Ubuntu:
  New

Bug description:
  Update to 3.37.90

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

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

[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Timothy Clarke]

For those approaching the issue from afresh it looks like HSP/HFP shares
functionality with bluetooth modems rather than solely audio. As such
there's a disagreement between pulseaudio who are only interested in the
audio parts, ofono who deals with the modem parts and the bluetooth
stack (bluez) who connect the to the hardware.

The issue came about as support was dropped (assuming someone else would
pick it up) as pulse audio and bluez went to later versions. It hasn't
been resolved because no one wants to ether deal with the other part, or
have another abstraction layer to switch between modem and audio
functionality

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions

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

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Gunnar Hjalmarsson]

On 2020-08-12 13:57, Akbarkhon Variskhanov wrote:
> Restarting the GNOME Shell fixes the issue and the 'ru' layout gets
> added in /etc/default/keyboard configuration file: XKBLAYOUT=us,ru

If your system has one user only, and you add an XKB input source via
Settings, /etc/default/keyboard is also updated instantly. It's per
design; no need to restart anything.

> This may explain why rearranging the order of input sources
> magically fixes the bug: newly added input sources probably need to
> be put into defaults once to be recognized later.

Nope. When testing on 18.04, I added an additional user, so
/etc/default/keyboard did not get updated. It behaved the same way. The
input source settings for the user don't need to be synced with
/etc/default/keyboard.

I saw that your upstream issue was closed. If you want to help solve the
problem on 18.04, I would suggest that you look at upstream commits in
gnome-shell and/or gnome-control-center which might be related. After
all we know that the issue is not present in focal (GNOME 3.36).

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

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

[Desktop-packages] [Bug 1891342] [NEW] network manager does not auto connect to hidden wifi networks

[PC]

Public bug reported:

Environment:
Fresh installation of Lubuntu 20.04 (it also occurs in a fresh installation of 
Ubuntu 20.04)

Steps to reproduce the situation:
1) Lubuntu -> Network Manager -> Edit Connections -> Add SSID of a hidden WiFi 
network
2) Network Manager does not connect automatically with the hidden Wifi Network

However, once the WiFi network SSID is set to broadcast mode, it starts
connecting automatically.

The workaround suggested in Bug 1542733 works here.
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1542733

However, it was suggested to create a new bug report for later releases.
Please provide your assistance. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Wed Aug 12 20:11:18 2020
InstallationDate: Installed on 2020-08-09 (3 days ago)
InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IpRoute:
 default via 192.168.29.1 dev wlp2s0 proto dhcp metric 600 
 192.168.29.0/24 dev wlp2s0 proto kernel scope link src 192.168.29.22 metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
 wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  PCWiFi  
9a5f3d88-a43e-4862-9cac-b65102e9e135  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp3s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
 lo  loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug focal

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

Title:
  network manager does not auto connect to hidden wifi networks

Status in network-manager package in Ubuntu:
  New

Bug description:
  Environment:
  Fresh installation of Lubuntu 20.04 (it also occurs in a fresh installation 
of Ubuntu 20.04)

  Steps to reproduce the situation:
  1) Lubuntu -> Network Manager -> Edit Connections -> Add SSID of a hidden 
WiFi network
  2) Network Manager does not connect automatically with the hidden Wifi Network

  However, once the WiFi network SSID is set to broadcast mode, it
  starts connecting automatically.

  The workaround suggested in Bug 1542733 works here.
  https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1542733

  However, it was suggested to create a new bug report for later releases.
  Please provide your assistance. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Aug 12 20:11:18 2020
  InstallationDate: Installed on 2020-08-09 (3 days ago)
  InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  IpRoute:
   default via 192.168.29.1 dev wlp2s0 proto dhcp metric 600 
   192.168.29.0/24 dev wlp2s0 proto kernel scope link src 192.168.29.22 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
   wlp2s0  wifi  connectedfull  full  
/org/freedesktop/NetworkManager/Devices/3  PCWiFi  
9a5f3d88-a43e-4862-9cac-b65102e9e135  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo  loopback  unm

[Desktop-packages] [Bug 1891338] [NEW] apparmor misconfigured for envice

[Kenneth Zadeck]

Public bug reported:

On a fully up to date xubuntu 20-04 system, when i run evince and click
on a link, it fails to follow that link in my browser. This kind of
thing happens when you are reading a technical paper and want to follow
one of the references and click on the doi or url.

When i click on the link i get a box that i cannot copy from that says:
Failed to launch preferred application for category "WebBrowser".

Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
/exo-helper-2"(Permission denied).

Did I say that it is annoying that i could not copy the text in this
box!!

The output of the ldd command you asked for is attached.

I should also point out that this worked fine under xubuntu 18.04.

I had originally posted this as an additional comment on
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
but https://launchpad.net/~seb128 said that I should submit this as a
separate bug because this is likely an apparmor configuration problem
that is similar to the ancient bug
https://bugs.launchpad.net/bugs/987578.

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


** Tags: apparmor

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

Title:
  apparmor misconfigured for envice

Status in evince package in Ubuntu:
  New

Bug description:
  On a fully up to date xubuntu 20-04 system, when i run evince and
  click on a link, it fails to follow that link in my browser. This kind
  of thing happens when you are reading a technical paper and want to
  follow one of the references and click on the doi or url.

  When i click on the link i get a box that i cannot copy from that says:
  Failed to launch preferred application for category "WebBrowser".

  Failed to execute child process "/usr/lib/x86_64-linux-gnu/xfce4/exo-2
  /exo-helper-2"(Permission denied).

  Did I say that it is annoying that i could not copy the text in this
  box!!

  The output of the ldd command you asked for is attached.

  I should also point out that this worked fine under xubuntu 18.04.

  I had originally posted this as an additional comment on
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
  but https://launchpad.net/~seb128 said that I should submit this as a
  separate bug because this is likely an apparmor configuration problem
  that is similar to the ancient bug
  https://bugs.launchpad.net/bugs/987578.

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

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

[Desktop-packages] [Bug 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[Rudra Saraswat]

I can confirm that this issue is still present in Ubuntu 20.04.1 Focal
Fossa.

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

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in GLib:
  Expired
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
  Everything is working right, except applying settings related to custom 
key-bindings.

  I added following lines my gschema.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='w'
  email='e'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'g'

  I put my gschema.override file in the '/usr/share/glib-2.0/schemas' 
directory. After I added these lines, I ran 'glib-compile-schemas 
/usr/share/glib2.0/schemas' and no error was reported.
  For testing purposes I created a new user, logged out, and logged in with the 
new user. In the best case, the custom key-binding were applied automatically, 
but this has not happened. Other defined key-bindings were applied correctly.
  In the gnome-control-center's key-bindings tab, the table containing  custom 
shortcuts is empty, containing one row with empty columns.

  Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
  /media-keys/custom-keybindings/custom0/' shows, the name, command, and
  binding key pairs contain empty ('') values.

  If I manually run following commands, the custom key-binding is created 
correctly:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name "Launch Gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command "gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding "g"

  Am I doing anything wrong when I want to add a custom key-bindings in
  my schema file, or  is 'glib-compile-schemas' really not applying this
  part from the schema file?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+subscriptions

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

[Desktop-packages] [Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

[Thorsten Schneider]

Can confirm this still happens with kernel 5.8.1. While the device is
listed correctly with its full name in bluetoothctl and can be trusted,
the final pairing will not work. syslog will constantly have a
"Refusing" message for the device and the connection:

Aug 12 15:47:25 htpc blueman-mechanism: Exiting
Aug 12 15:47:38 htpc systemd[1]: Starting Stop ureadahead data collection...
Aug 12 15:47:38 htpc systemd[1]: Started Stop ureadahead data collection.
Aug 12 15:47:51 htpc bluetoothd[962]: Refusing input device connect: No such 
file or directory (2)
Aug 12 15:47:51 htpc bluetoothd[962]: Refusing connection from 
C8:3F:26:44:17:2D: unknown device

For example an 8bitdo Arcade Stick can be paired and connected without
issues over bluetooth.

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

Title:
  Xbox (One) Wireless Controller won't connect

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

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions

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

[Desktop-packages] [Bug 1890286] Re: ansi escape sequence injection in add-apt-repository

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.98.9.2

---
software-properties (0.98.9.2) focal-security; urgency=medium

  * SECURITY UPDATE: malicious repo could send ANSI sequences to terminal
(LP: #1890286)
- add-apt-repository: strip ANSI sequences from the description.
- CVE-2020-15709

 -- Marc Deslauriers   Fri, 07 Aug 2020
09:15:34 -0400

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

** Changed in: software-properties (Ubuntu)
   Status: New => Fix Released

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

Title:
  ansi escape sequence injection in add-apt-repository

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  This was reported to oss-security and to secur...@ubuntu.com, but I
  figure I should make a real bug report, as otherwise it'll probably be
  missed. Original post from https://www.openwall.com/lists/oss-
  security/2020/08/03/1 follows below.

  --

  Hi,

  I've found a rather low grade concern: I'm able to inject ANSI escape
  sequences into PPA descriptions on Launchpad, and then have them
  rendered by add-apt-repository *before* the user consents to actually
  adding that repository. There might be some sort of trust barrier
  issue with that. This could be used to clear the screen and imitate a
  fresh bash prompt, upload files, dump the current screen to a file, or
  other classic shenanigans, well chronicled in the archives of oss-sec.

  PoC time -- I'm using this "feature" for good at the moment to
  announce the deprecation in bold text of a PPA that I maintain:
  https://data.zx2c4.com/add-apt-repository-ansi-injection.png

  The proper fix to this is likely to do sanitization on the
  add-apt-repository side.

  Regards,
  Jason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890286/+subscriptions

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

[Desktop-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)

[Kai-Heng Feng]

Do unaffected distros have "module-switch-on-port-available" loaded?

Can you please try not loading the module?

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [HP Pavilion dv9000] Mute toggles on/off while plugged into the
  headphone/speaker jack (19.04+)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp-
  pavilion-dv9000/specs/) built many years ago.

  
  Whenever I'm using any distro that's based on Ubuntu which was published from 
Version 19.04 onwards, I've been having a major issue with the mute button 
toggling on and off whenever I have something plugged into the audio out jack. 
I know that it's not the fault of XFCE, because I also use the latest version 
of Manjaro with XFCE on this same computer, and it works fine. I also know it's 
not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 
6) also on this exact same computer, and it also works fine. Qubes, Mageia, and 
Fedora 31 also work perfectly fine and don't have this issue.

  My "lsb-release" is:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=19.10
  DISTRIB_CODENAME=eoan
  DISTRIB_DESCRIPTION="Ubuntu 19.10"

  and "apt-cache policy pulseaudio" outputs:
  pulseaudio:
Installed: 1:13.0-1ubuntu1.1
Candidate: 1:13.0-1ubuntu1.1
Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  I've uploaded a short video of the problem that I recorded with my phone here:
  https://www.youtube.com/watch?v=GXaHXQA-5uQ

  
  The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, 
Xubuntu 19.04, and Sparky 5.10 and 2020.02.

  
  I've checked pretty much everything I can think of. There's a log for my ALSA 
help diagnostics results on my current computer (which works properly with 
18.04) at:
  http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829

  
  the result output of lspci is:
  [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2)
  00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2)
  00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2)
  00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2)
  00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2)
  00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2)
  00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2)
  00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1)
  00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2)
  00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3)
  00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3)
  00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3)
  00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
  00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1)
  00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1)
  00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2)
  00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2)
  00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3)
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
HyperTransport Technology Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] 
Miscellaneous Control
  03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g 
WLAN (rev 01)
  05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] 
(rev a1)
  07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
  07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host 
Adapter (rev 19)
  07:05.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter 
(rev 0a)
  07:05.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev

[Desktop-packages] [Bug 1889106] Re: [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a higher version than the transitional deb in 20.04

[Robie Basak]

I asked about this on ubuntu-devel@. It'd be nice to have a solution
where we don't have to keep doing this.

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

Title:
  [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
  browser due to a higher version than the transitional deb in 20.04

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  Fix Committed

Bug description:
  This bug is another manifestation of bug #1858500, but with a different 
upgrade path.
  bionic-{security,updates} will soon have chromium-browser 
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and 
when that happens the version number in focal will be lower, meaning that 
chromium-browser won't be updated to the new package that installs the snap for 
a user upgrading from 18.04 to 20.04.

  Since chromium-browser in 20.04 is a mostly empty transitional package
  that installs the chromium snap, all that's needed to fix this is to
  bump its version number.

  [Impact]

  Users upgrading from 18.04 to 20.04 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 18.04 is (will soon be) greater than 
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.

  [Test Case]

   * Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in 
bionic-{security,updates}
   * On a machine running 18.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 20.04
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions
  compared to the deb package, they are being tracked at
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
  snap is the desired behaviour though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1889106/+subscriptions

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

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Akbarkhon Variskhanov]

Maybe the reconfiguration process is delayed as waiting for 20-30
minutes sometimes works, but it's unreliable and I can't seem to
reproduce it.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

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

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Akbarkhon Variskhanov]

I have tried to add an input source through gsettings
gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'us'), ('xkb', 
'ru')]"
but it still produced the same result: text input remains at default layout.

Restarting the GNOME Shell fixes the issue and the 'ru' layout gets
added in /etc/default/keyboard configuration file: XKBLAYOUT=us,ru

This may explain why rearranging the order of input sources magically
fixes the bug: newly added input sources probably need to be put into
defaults once to be recognized later.

However, manually editing the keyboard configuration file does nothing.

What probably happens is that gnome-shell recognizes the added input
sources but 'forgets' 1) to send the appropriate command to XKB
(setxkbmap ru) whenever the switch shortcut is invoked; or 2) to
reconfigure the keyboard settings.

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

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

[Desktop-packages] [Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager

[Bug Watch Updater]

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

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

Title:
  Thunderbolt 2 storage not auto mounted and  show in file manager

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in OEM Priority Project focal series:
  New
Status in udisks:
  New
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  OS 18.04 & 20.04

  Plug thunderbolt 2 storage device, can see the device in lsblk as
  /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in
  file manager (check attachment, it say TBT3 in the picture, however I
  use TBT2 and I can reproduce it)

  public bug: https://github.com/storaged-project/udisks/issues/793

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions

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

[Desktop-packages] [Bug 1891158] Re: riscv64 build - hang at the end of the build (groovy)

[Christian Ehrhardt ]

It turned out that this has happened in the past and then resolved, so this is 
a comeback.
For "dee" we can bump the timeout or skip the test on riscv64 for the immediate 
problem

But the "dbus-test-runner timeout makes riscv64 builds" hang is a problem on 
its own.
Therefore I added a bug task to dbus-test-runner

** Also affects: dbus-test-runner (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- riscv64 build - hang at the end of the build (groovy)
+ riscv64 build - hang at the end of the build with hanging "dbus-test-runner"

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

Title:
  riscv64 build - hang at the end of the build with hanging "dbus-test-
  runner"

Status in dbus-test-runner package in Ubuntu:
  New
Status in dee package in Ubuntu:
  Confirmed

Bug description:
  The builds for riscv64 on e.g.
  https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1
  hang eventually.

  All other architectures work fine.

  
  Build log tail will be like:
  ...
symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4
  pkgstripfiles: Running PNG optimization (using 8 cpus) for package dee-tools 
...
  pkgstripfiles: No PNG files.
  dpkg-deb: building package 'dee-tools' in 
'../dee-tools_1.2.7+17.10.20170616-6build1_riscv64.deb'.
  pkgstriptranslations: libdee-1.0-4-dbgsym does not contain translations, 
skipping
  pkgstriptranslations: no translation files, not creating tarball
  pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com
  pkgstripfiles: processing control file: 
debian/.debhelper/libdee-1.0-4/dbgsym-root/DEBIAN/control, package 
libdee-1.0-4-dbgsym, directory debian/.debhelper/libdee-1.0-4/dbgsym-root
  dpkg-deb: building package 'libdee-1.0-4-dbgsym' in 
'debian/.debhelper/scratch-space/build-libdee-1.0-4/libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'.
   Renaming libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to 
libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb
  pkgstriptranslations: dee-tools-dbgsym does not contain translations, skipping
  pkgstriptranslations: no translation files, not creating tarball
  pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com
  pkgstripfiles: processing control file: 
debian/.debhelper/dee-tools/dbgsym-root/DEBIAN/control, package 
dee-tools-dbgsym, directory debian/.debhelper/dee-tools/dbgsym-root
  dpkg-deb: building package 'dee-tools-dbgsym' in 
'debian/.debhelper/scratch-space/build-dee-tools/dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'.
   Renaming dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to 
dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb
   dpkg-genbuildinfo --build=any
   dpkg-genchanges --build=any -mLaunchpad Build Daemon 
 
>../dee_1.2.7+17.10.20170616-6build1_riscv64.changes
  dpkg-genchanges: info: binary-only arch-specific upload (source code and 
arch-indep packages not included)
   dpkg-source --after-build .
  dpkg-buildpackage: info: binary-only upload (no source included)

  
  Then it will be stuck until at 24h a timeout will reap the builder.

  It turned out (thanks cjwatson) that on these systems there is a
  leftover process

  Zombie schroot process
  Looks like there's a dbus-daemon process still running in the background of 
the build that the build didn't clean up properly
  buildd481987  0.0  0.0   5244  2780 ?SAug10   0:00 
dbus-daemon --config-file /usr/share/dbus-test-runner/session.conf 
--print-address
  # ls -l /proc/481987/cwd
  lrwxrwxrwx 1 buildd buildd 0 Aug 11 10:08 /proc/481987/cwd -> 
/home/buildd/build-PACKAGEBUILD-19646792/chroot-autobuild/build/dee-1HAMJl/dee-1.2.7+17.10.20170616/tests

  
  On #ubuntu-devel we discussed this and agreed that we should not just retry 
until it slips through by accident, we might never be able to build it again.

  Instead we should try looking for what actually hangs on riscv64 and
  why.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/1891158/+subscriptions

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

[Desktop-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

[Inkognitoo]

Hello, dreamcat4!

20.04 is only version I tested this case

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

Title:
  [xorg] multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions

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

[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged

[Akbarkhon Variskhanov]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3061
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3061

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3061
   Importance: Unknown
   Status: Unknown

** Description changed:

  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.
  
  Steps to reproduce this bug:
  
  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.
  
  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)
  
- or 5. Reboot.
+ or 5. Reboot or re-login (restarting gnome-shell works as well: killall
+ -3 gnome-shell or Alt+F2 > r > Enter)
  
- Screenshots are attached. The bug is easily reproduced as many times as
- possible.
+ 
+ Screenshots are attached. The bug is easily reproduced as many times as 
possible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

Title:
  Keyboard won't switch its layout to a newly added second input source
  unless their order is rearranged

Status in GNOME Shell:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  What should happen:
  Adding a second input source (Russian, in my case) should result in being 
able to switch to it and use it immediately.
  What happens now:
  It is not recognized until you rearrange its order, or reboot.

  Steps to reproduce this bug:

  1. Have English set as primary language.
  2. Go to Settings > Region & Language > Input Sources and add Russian.
  3. Russian layout is added to Input Sources and the indicator becomes visible 
in the Top Bar.
  4. You can switch between languages with the assigned keyboard shortcut but 
the text input won't change.

  5. Rearrange their order in Input Sources: make Russian primary, English 
secondary.
  6. You can now enter text in Russian.
  7. You can now put Russian back to being second in the list (so it does not 
cause problems at logic screen, opening up new browser window, etc.)

  or 5. Reboot or re-login (restarting gnome-shell works as well:
  killall -3 gnome-shell or Alt+F2 > r > Enter)

  
  Screenshots are attached. The bug is easily reproduced as many times as 
possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 13:39:01 2020
  InstallationDate: Installed on 2016-11-03 (1373 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)

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

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

[Desktop-packages] [Bug 1879479] Re: Saving doc/docx document with formula in table removes this formula

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => In Progress

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

Title:
  Saving doc/docx document with formula in table removes this formula

Status in LibreOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:
  Formula handling inside tables is broken in Microsoft Office DOC or DOCX file 
formats.

  Steps to Reproduce:
  1. Open LibreOffice Writer
  2. Insert table of any size - for example 4x4
  3. Enter some numbers in the table cells
  4. Go to the last (right bottom) cell, hit "=", enter "=sum()"
  5. Save the document as Microsoft Office DOC or DOCX and close document
  6. Open just saved DOC/DOCX document and change some numbers in table (try 
pressing F9 for sure)

  Actual Results:
  * the formula in the table is not saved, the user is unable to calculate with 
it after saving file as DOC / DOCX

  Expected Results:
  * the formula in the table is saved, the user is able to calculate with it 
after saving file as DOC / DOCX

  Notes: the same happens if original document is DOC / DOCX. Saving
  table with formula removes the formula on next open. Test ODT document
  is in attachment.

  The almost latest LO 6.4.3.2 as in Ubuntu 20.04 LTS is also affected
  by this bug:

  Version: 6.4.3.2
  Build ID: 1:6.4.3-0ubuntu0.20.04.1
  CPU threads: 1; OS: Linux 5.4; UI render: default; VCL: gtk3; 
  Locale: en-US (en_US.UTF-8); UI-Language: en-US
  Calc: threaded

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue May 19 13:37:57 2020
  InstallationDate: Installed on 2020-04-23 (25 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1879479/+subscriptions

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

[Desktop-packages] [Bug 1738774]

[Pmenzel+bugs-documentfoundation-org]

In Debian Sid/unstable with GNOME 3.36.4 and LibreOffice 7.0.0, I
switched the icon theme from *Elementary* to *Elementary (SVG)*, and the
icons still look blurry on a HiDPI monitor connected over HDMI.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

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

Bug description:
  LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled
  icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions

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

[Desktop-packages] [Bug 1891313] [NEW] Xorg crash

[Luan Orion de Oliveira Barauna Ferreira]

Public bug reported:

I have a ACER Nitro 5 NVIDIA GTX 1650 Mobile with Ubuntu 20.04  instated
and i tryed to boot my notebook with a second monitor plugged by HDMI
port. Now, my internal monitor can't be recognized and its crashing on
the initial load screem. They can load only whit the HDMI is connected.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.51.06  Sun Jul 19 20:02:54 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 12 07:55:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 450.51.06, 5.4.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1331]
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1025:1332]
InstallationDate: Installed on 2020-08-05 (7 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing
 Bus 001 Device 002: ID 1a2c:0043 China Resource Semico Co., Ltd USB Mouse
 Bus 001 Device 004: ID 8087:0029 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-54
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=b286d151-6958-4e94-8f2b-2af178b1dc88 ro vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.30
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Octavia_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.30
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.30
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-54
dmi.product.sku: 
dmi.product.version: V1.30
dmi.sys.vendor: Acer
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash 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/1891313

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a ACER Nitro 5 NVIDIA GTX 1650 Mobile with Ubuntu 20.04
  instated and i tryed to boot my notebook with a second monitor plugged
  by HDMI port. Now, my internal monitor can't be recognized and its
  crashing on the initial load screem. They can load only whit the HDMI
  is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/n

[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd

[Robie Basak]

The Ubuntu Xenial SRU looks fine in principle but is currently blocked
until the previous SRU is released. I've not reviewed this in detail
yet.

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

Title:
  rpcbind grabs ports used by other daemons such as cupsd

Status in cups package in Ubuntu:
  Invalid
Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  In Progress
Status in rpcbind source package in Bionic:
  Fix Committed
Status in rpcbind package in Debian:
  Fix Released
Status in Fedora:
  Confirmed

Bug description:
  [impact]

  rpcbind binds to a 'random' reserved port at startup, which can
  conflict with the reserved port number for other applications that
  actually 'own' the reserved port number. One example is cups, which
  uses the reserved port 631.

  This prevents the actual 'owner' of the reserved port from starting,
  since it can't bind to its reserved port.

  Additionally, this can raise alarms from security monitoring software
  that does not expect programs to be listening on random reserved
  ports.

  [test case]

  start rpcbind and check which ports it is listening on, e.g.:

  $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc
  udp0  0 0.0.0.0:614 0.0.0.0:* 
  4678/rpcbind

  each time rpcbind is restarted, it will be listening to a different
  'random' port.

  [regression potential]

  this adds a way to disable rpcbind from listening to the 'random'
  port. any regression would likely prevent rpcbind from starting, or
  may cause problems with the interaction between rpcinfo and rpcbind,
  as rpcinfo may use the random reserved port in some cases, as detailed
  in the Debian bug.

  [scope]

  This is needed only for Bionic and earlier.

  In Focal and later, and in Debian, rpcbind defaults to not opening the
  random reserved port.  The admin can use the -r parameter to cause
  rpcbind to restore the old behavior of opening the random reserved
  port.

  [other info]

  Note that the -r parameter is a Debian addition, and the upstream
  rpcbind has disabled the random port functionality at build time;
  there is no runtime parameter to allow the admin to choose the
  behavior.

  Also, as discussed in the Debian bug, disabling this rpcbind 'feature'
  is known to cause problems for the rpcinfo program, which is why
  Debian introduced the -r parameter. So, when this -r parameter is
  backported to Bionic and earlier, we must retain the default behavior
  for those releases, which is for rpcbind to open the random reserved
  port.

  Thus, the patch for this will first backport the upstream patch that adds 
functionality to be able to disable the 'remote calls' function, and also 
backports the debian patch to change that from a compile-time to run-time 
option. Then, another patch is added, which changes the default back to the 
behavior of x/b, which is for remote calls to be enabled by default,
  and also adds a check for the existence of an environment variable 
"RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change 
the default to disabled.

  This allows 1) retaining the existing default behavior of rpcbind in x
  and b, while also 2) providing a mechanism to change that default for
  anyone who does *not* want remote calls to be enabled, and 3) allowing
  the mechanism to change the default to remain in place after an
  upgrade to Focal. Using the environment variable allows anyone to
  disable the remote calls in x and/or b, and then upgrade to Focal
  without breaking rpcbind or needing to remove the env var. After the
  upgrade to Focal, the environment variable (defined in
  /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored
  without any change needed to the rpcbind package in Focal or later.

  [original description]

  Binary package hint: cups

  cups 1.3.9-2ubuntu4
  From /var/log/cups/error_log:
  cups: unable to bind socket for address 127.0.0.1:631 - Address already in 
use.

  Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd
  when started.

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

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

[Desktop-packages] [Bug 1891302] [NEW] udisks eats up 10GB RAM in ubuntu 18.04

[Syed Imran]

Public bug reported:

Problem: udisks is taking more than 10GB memory in my openstack VM (and
it keeps growing)

Note: more than 30 people have reported this so far.

I have already posted a question in askubuntu.com but no updates. 
(https://askubuntu.com/questions/1232439/udisks-eats-up-9gb-ram-in-ubuntu-18-04)
I see lots of people have reported such issue in Redhat and Fedora and got 
patch fixes for it.

But there is no such issues reported for ubuntu as per my analysis.

Please help in providing a patch for the same.

Thanks,
Syed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udisks2 2.7.6-3ubuntu0.2
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: GNOME
CustomUdevRuleFiles: 70-snap.postman.rules 70-snap.core.rules
Date: Wed Aug 12 15:50:01 2020
Ec2AMI: ami-165f
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: bh-dc-os-dhn-40_1
Ec2InstanceType: da.016-0044
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat OpenStack Compute
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=531ca97b-1d3e-4ed8-90ea-2026b3d64dd9 ro console=ttyS0
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.11.0-2.el7
dmi.chassis.type: 1
dmi.chassis.vendor: Red Hat
dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996)
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRedHat:pnOpenStackCompute:pvr17.0.12-1.el7ost:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996):
dmi.product.family: Virtual Machine
dmi.product.name: OpenStack Compute
dmi.product.version: 17.0.12-1.el7ost
dmi.sys.vendor: Red Hat

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


** Tags: amd64 apport-bug bionic ec2-images

** Description changed:

- Problem: udisks is taking more than 9GB memory in my openstack VM (keeps
- growing)
+ Problem: udisks is taking more than 10GB memory in my openstack VM (and
+ it keeps growing)
  
  Note: more than 30 people have reported this so far.
  
  I have already posted a question in askubuntu.com but no updates. 
(https://askubuntu.com/questions/1232439/udisks-eats-up-9gb-ram-in-ubuntu-18-04)
  I see lots of people have reported such issue in Redhat and Fedora and got 
patch fixes for it.
  
  But there is no such issues reported for ubuntu as per my analysis.
  
  Please help in providing a patch for the same.
  
  Thanks,
  Syed
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-3ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 70-snap.postman.rules 70-snap.core.rules
  Date: Wed Aug 12 15:50:01 2020
  Ec2AMI: ami-165f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: bh-dc-os-dhn-40_1
  Ec2InstanceType: da.016-0044
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb:
-  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
-  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat OpenStack Compute
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=531ca97b-1d3e-4ed8-90ea-2026b3d64dd9 ro console=ttyS0
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.0-2.el7
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.chassis.version: RHEL 7.6.0 PC (i440FX + PIIX, 1996)
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.0-2.el7:bd04/01/2014:svnRedHat:pnOpenStackCompute:pvr17.0.12-1.el7ost:cvnRedHat:ct1:cvrRHEL7.6.0PC(i440FX+PIIX,1996):
  dmi.product.family: Virtual Machine
  dmi.product.name: OpenStack Compute
  dmi.product.version: 17.0.12-1.el7ost
  dmi.sys.vendor: Red Hat

** Summary changed:

- udisks eats up 9GB RAM in ubuntu 18.04
+ udisks eats up 10GB RAM in ubuntu 18.04

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

Title:
  udisks eats up 10GB RAM in ubuntu 18.04

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Problem: udisks is taking more than 10GB memo

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

[Stefano Galassi]

other info that might be useful are:
xinput list-props 20

Device 'MSFT0001:00 04F3:3140':
Device Enabled (177):   1
Coordinate Transformation Matrix (179): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Natural Scrolling Enabled (339):   0
libinput Natural Scrolling Enabled Default (340):   0
libinput Scroll Methods Available (341):0, 0, 1
libinput Scroll Method Enabled (342):   0, 0, 1
libinput Scroll Method Enabled Default (343):   0, 0, 1
libinput Button Scrolling Button (358): 3
libinput Button Scrolling Button Default (359): 3
libinput Button Scrolling Button Lock Enabled (360):0
libinput Button Scrolling Button Lock Enabled Default (361):0
libinput Accel Speed (349): -1.00
libinput Accel Speed Default (350): 0.00
libinput Accel Profiles Available (362):1, 1
libinput Accel Profile Enabled (363):   1, 0
libinput Accel Profile Enabled Default (364):   1, 0
libinput Calibration Matrix (365):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Calibration Matrix Default (366):  1.00, 0.00, 
0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Left Handed Enabled (351): 0
libinput Left Handed Enabled Default (352): 0
libinput Send Events Modes Available (353): 1, 0
libinput Send Events Mode Enabled (354):0, 0
libinput Send Events Mode Enabled Default (355):0, 0
Device Node (297):  "/dev/input/event15"
Device Product ID (296):1267, 12608
libinput Drag Lock Buttons (356):   
libinput Horizontal Scroll Enabled (357):   1


and the output of: cat /dev/input/event15 is empty when I try to use the
touchpad, meaning that it's not sending events to that device..

-- 
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 linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

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

  xinput indentifies it as MSFT0001:00 04F3:3140

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
 

[Desktop-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz

[dreamcat4]

Did you see it work on previous ubuntu version (19.10)? Or is 20.04 the
first version you tested here?

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

Title:
  [xorg] multiple monitors: limits the framerate of faster 120/144hz
  monitors to 60hz

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  multiple monitors on xorg
  =

  Was recently discussed over on
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892

  Another user + myself have the following issue:

  The slowest connected display limits the FPS. The test case we used is
  over at the top of the other bug report ^^

  This we found today happens with either amd vega graphics, or nvidia
  pascal graphics, the vendor doesn't seem to matter. We have both seen
  the same issue (xorg).

  This is on 18.10, and booting into the 'Gnome (xorg)' login option.
  With the FPS being logged by journalctl -f. With only single monitor
  attached. Then it initially goes as high as the primary monitor can
  show. (And glmark2 running in background, to maintain a continued
  load). Which is 120fps for my case. Then as soon as secondary monitor
  is plugged in, which is a 60hz TV. This is being plugged into the HDMI
  port of the same graphics card in real time. Then the FPS logged by
  'journalctl -f' drops, and becomes capped to 60hz, in the output being
  printed by journalctl -f.

  My setup:
  kernel 5.0.0-05-lowlatency #201903032031
  NVIDIA Driver for UNIX platforms 415.27 (the closed source one)
  ubuntu 18.10

  mutter version:

  mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed]
  mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all 
[installed]

  To confirm where the '.4' at the very end of the ~ubuntu18.10.4
  version number, it seems to be that we have updated now on our client
  machines the be most recent bugfix updates, kindly provided by Daniel.
  Which closed the other bug
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being
  referred to, as being solved for people's single monitor scenarios.

  Thanks again for the other recent bug fixes in this area, it is a nice
  progress. Very helpful! We hope you can also look into this latest
  problem / issue for the multiple monitor scenario.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions

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

[Desktop-packages] [Bug 1888628] Re: not automatic connection to hidden wifi

[Kai-Heng Feng]

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

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

Title:
  not automatic connection to hidden wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after restart iḿ no automatically connected to my hidden wifi

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1896 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 10:05:31 2020
  InstallationDate: Installed on 2020-07-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP ProBook 6570b
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-42-generic 
root=UUID=fd19f40c-82a5-40ab-b14a-6d553d287752 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2019
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICE Ver. F.74
  dmi.board.name: 17AB
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICEVer.F.74:bd04/15/2019:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1102:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 6570b
  dmi.product.sku: B6P85EA#ABH
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1888628/+subscriptions

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

[Desktop-packages] [Bug 1888628] [NEW] not automatic connection to hidden wifi

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

after restart iḿ no automatically connected to my hidden wifi

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thomas 1896 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 23 10:05:31 2020
InstallationDate: Installed on 2020-07-22 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP ProBook 6570b
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-42-generic 
root=UUID=fd19f40c-82a5-40ab-b14a-6d553d287752 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2019
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICE Ver. F.74
dmi.board.name: 17AB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.38
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICEVer.F.74:bd04/15/2019:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1102:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 6570b
dmi.product.sku: B6P85EA#ABH
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug focal
-- 
not automatic connection to hidden wifi
https://bugs.launchpad.net/bugs/1888628
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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

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

[ejahn]

Agree with Joseph Borg about #8.  Evolution notifications are turned on
in Gnome Settings.  But popup reminders are turned off, yet they still
appear.

-- 
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 1890863] Re: Display does not come on after suspend

[Daniel van Vugt]

Perfect, thanks. It appears to be the 'amdgpu' driver crashing in the
kernel.

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

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

** Summary changed:

- Display does not come on after suspend
+ [amdgpu] Display does not come on after suspend

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

Title:
  [amdgpu] Display does not come on after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  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.:bvr2603:bd08/05/2020: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager

[Sebastien Bacher]

Thanks for forwarded upstream! They asked for some more informations now

** Bug watch added: github.com/storaged-project/udisks/issues #793
   https://github.com/storaged-project/udisks/issues/793

** Also affects: udisks via
   https://github.com/storaged-project/udisks/issues/793
   Importance: Unknown
   Status: Unknown

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

** Changed in: udisks2 (Ubuntu)
   Status: New => Triaged

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

Title:
  Thunderbolt 2 storage not auto mounted and  show in file manager

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in OEM Priority Project focal series:
  New
Status in udisks:
  Unknown
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  OS 18.04 & 20.04

  Plug thunderbolt 2 storage device, can see the device in lsblk as
  /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in
  file manager (check attachment, it say TBT3 in the picture, however I
  use TBT2 and I can reproduce it)

  public bug: https://github.com/storaged-project/udisks/issues/793

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions

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

[Desktop-packages] [Bug 1808702] Re: Bubblewrap integration broke user thumbnailers

[Sebastien Bacher]

The issue has been fixed upstream with that commit now
https://gitlab.gnome.org/GNOME/gnome-desktop/-/commit/df477a3d
the change will land in the next update (and is probably a candidate for a SRU)

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

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Bubblewrap integration broke user thumbnailers

Status in gnome-desktop3 package in Ubuntu:
  Fix Committed

Bug description:
  This bug is related to https://bugs.launchpad.net/ubuntu/+source
  /gnome-desktop3/+bug/1795668 and to the question in Ubuntu
  Stackexchange https://askubuntu.com/questions/1088539/custom-
  thumbnailers-don-t-work-on-ubuntu-18-10-and-18-04

  The recent hardening on thumbnailers by using bubblewrap is causing a
  problem with user-installed thumbnailers. Consider this (for example)
  thumbnailer to add a small Dilbert icon to the GIMP .xcf files:

  
  #!/bin/bash

  tmpfile1=$(tempfile --directory /tmp --prefix xcft --suffix .png)
  trap 'rm -rf $tmpfile1' INT EXIT TERM

  die() {
echo >&2 "$@"
rm -rf $tmpfile1
exit 1
  }
   
  # The script will be called with parameters : -s %s %u %o
  # -s %s: vertical size,  %u: input url, %o: output file

  if [ $1 = "-s" ]; then 
 size=$2
 uin=$3
 fout=$4
  else
 size=32 #default size
 uin=$1
 fout=$2
  fi

  # uin es una url, eliminar "file://"
  fin="${uin#file://*}"

  /usr/bin/gnome-xcf-thumbnailer -s $size "$fin" $tmpfile1 || die 
"gnome-xcf-thumbnailer failed"
  /usr/bin/composite-im6.q16  -gravity southeast  \
 \(  -resize $((size/2))x$((size/2)) /usr/share/gimp/2.0/images/wilber.png 
\) \
 \( -resize $sizex$size $tmpfile1 \)  "$fout" || die "convert failed"

  rm -rf $tmpfile1
  exit 0

  It used to work before the last update to use bubblewrap, and now
  doesn't work anymore. I tried to dig into https://github.com/GNOME
  /gnome-desktop/blob/master/libgnome-desktop/gnome-desktop-thumbnail-
  script.c to see what happens, and I concluded that the "reinforced"
  thumbnail generator do this:

  mkdir /tmp/temporary

  bwrap --ro-bind /usr /usr \
  --ro-bind /etc/ld.so.cache /etc/ld.so.cache \
  --ro-bind /bin /bin \
  --ro-bind /lib64 /lib64 \
  --ro-bind /lib /lib \
  --ro-bind /sbin /sbin \
  --proc /proc  \
  --dev   /dev  \
  --chdir   /  \
  --setenv   GIO_USE_VFS   local  \
  --unshare-all  \
  --die-with-parent  \
  --bind /tmp/temporary /tmp \
  --ro-bind /home/romano/software/thumbnailers/test/rgttiwm.xcf  
/tmp/gnome-desktop-file-to-thumbnail.xcf  \
  /usr/bin/xcf-thumb -s 128 file:///tmp/gnome-desktop-file-to-thumbnail.xcf 
/tmp/gnome-desktop-thumbnailer.png
  #
  cp /tmp/temporary/gnome-desktop-thumbnailer.png test.png

  ...and this way, my thumbnailer did succeed in creating the PNG with
  the correct preview. But when called internally by gnome, it fails,
  and creates a strange "~/.cache/thumbnailer/fail" file containing the
  following:

  �PNG
  
  
IHDR
ĉd�EtEXtThumb::URIfile:///home/romano/software/thumbnailers/test/rgttiwm.xcftEXtThumb::MTime1380735765�y�O
 tEXtSoftwareGNOME::ThumbnailFactoryo 
  [...]

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

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

[Desktop-packages] [Bug 1890863] Re: Display does not come on after suspend

[Nick]

Hello, here is the log as requested

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1890863/+attachment/5400918/+files/prevboot.txt

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

Title:
  Display does not come on after suspend

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  After coming out of suspend the display is not receiving any data and
  stays in power saving mode.  Only power cycling the system brings it
  back.  Unsure whether this is related to amdgpu or something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 12:51:28 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [1458:2314]
  InstallationDate: Installed on 2020-01-08 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  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.:bvr2603:bd08/05/2020: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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1890863/+subscriptions

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

[Desktop-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype

[Alexander Adam]

This bug is still present on Ubuntu 20.04.

Also you can find it on other places like

https://ubuntuforums.org/showthread.php?t=2398097
https://discourse.ubuntubudgie.org/t/online-accounts-cant-copy-and-paste-email-password/3212/3
or
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1510011

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

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

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

[Desktop-packages] [Bug 1867982] Re: unable to copy and paste login and password

[Alexander Adam]

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

** This bug has been marked a duplicate of bug 1703377
   Gnome online account login prevents paste or autotype

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

Title:
  unable to copy and paste login and password

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Select eg Google account when you have your user and password in clipboard.
  In the new account interface, cant paste into fields.
  Expected is paste.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Thu Mar 19 08:37:01 2020
  InstallationDate: Installed on 2020-03-15 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200312)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

[Colin Law]

Is this really related to the linked gnome-shell bug?  It doesn't look
related to me.  This bug is completely reproducible whereas the linked
one seems to be an intermittent complete failure of the shell.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1891272] Re: Ubuntu settings is still reporting 3.36.3 after update?

[Daniel van Vugt]

It appears that is copied from /usr/share/gnome/gnome-version.xml which
is provided by the package 'gnome-desktop3-data'

** Tags added: focal

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

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Ubuntu settings is still reporting 3.36.3 after update?

Status in gnome-desktop3 package in Ubuntu:
  Triaged

Bug description:
  I am a little unsure whether the gnome-shell package is the one used for the 
Ubuntu desktop. I know that the Ubuntu desktop is based on gnome-shell, but it 
seems that after upgrading to 3.36.4 from 3.36.3, that Ubuntu settings in About 
-> Gnome version -> 3.36.3, still reports 3.36.3 and not 3.36.4. 
  Is this a bug in the settings or has the update not been "applied" to the 
Ubuntu variant of Gnome yet?

  I am using Wayland and Ubuntu 20.04 LTS.

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

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

[Desktop-packages] [Bug 1831039] Re: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

[Daniel van Vugt]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Confirmed

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

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

** Tags added: focal

** Summary changed:

- The onscreen keyboard does not open in text inputs for non-GTK applications 
such as Firefox or Chrome
+ When using Wayland, the onscreen keyboard does not open in text inputs for 
non-GTK applications such as Firefox or Chrome

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

Title:
  When using Wayland, the onscreen keyboard does not open in text inputs
  for non-GTK applications such as Firefox or Chrome

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using wayland - onscreen keyboard not open in text inputs in many
  applications such as firefox or chrome.

  Ubuntu 18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-06-09 (1455 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-50-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1831039/+subscriptions

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