date:20200718

There is a regression of this bug in Ubuntu 20.04 using the default Gnome
desktop

Setup is a Shuttle POS P511
using a Weida CoolTouch controller with driver integrated into the Linux kernel
Second screen is a AOC USB-3.1 Display Link monitor without display
capabilities only (no touch).

When the AOC screen is disconnected the touch works normally.
When the AOC screen is connected the touch is out of sync and touches over both
screens from the Shutlle/Weida screen.

Here is xinput list-props with both screens connected.

xinput list-props 11
Device 'Weida Hi-Tech CoolTouch® System':
Device Enabled (169): 1
Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Calibration Matrix (308): 1.00, 0.00, 0.00,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Calibration Matrix Default (309): 1.00, 0.00,
0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Send Events Modes Available (291): 1, 0
libinput Send Events Mode Enabled (292):0, 0
libinput Send Events Mode Enabled Default (293):0, 0
Device Node (294): "/dev/input/event4"
Device Product ID (295):9589, 49920

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

Title:
Touchscreen controls both screens in dual-monitor setup

Status in GNOME Settings Daemon:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in OEM Priority Project trusty series:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Triaged
Status in unity-settings-daemon package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Trusty:
Confirmed
Status in unity-settings-daemon source package in Trusty:
Fix Released

Bug description:
SRU Request:

Laptops and all-in-one systems with touchscreens don't currently map
the touch input device onto the internal display. As a result, when
the screen changes (e.g. the main output is rotated or an external
output is connected), the touch input device maps onto the entire
screen, regardless of the only relevant area, thus making the
touchscreen completely useless.

[Impact]
* The touchscreen becomes unusable if an external output is connected or if
the main output is rotated.

[Test Case]
* Either plug in an external monitor or rotate the internal monitor
- Expected: the touchscreen should respond to touch as usual.
- Bad behavior: the touchscreen is unusable and responds by selecting
areas other than the one the user actually selects.

[Regression Potential]
* Low, it only affects the main touchscreen (tablets or multiple
touchscreens are not supported) and it only adds a feature that is currently
missing.

[Other Info]
* N/A

---

My laptop has a touchscreen. It works fine in 14.04 until I plug in an
external monitor. When using an external monitor, input from the
touchscreen is remapped so that the touchscreen provides input to both
monitors. The result is that there is no longer a 1:1 correspondence
between moving your finger and the cursor. This is confusing and
difficult to use.

A touchscreen is a direct input device (vs an indirect one like a
mouse/touchpad); input from the touchscreen should be bound to the
physical display that it's attached to.

To reproduce:
1) On a computer with a touchscreen, use the touchscreen to move a window
around, including to the edges of the screen. Note that the window moves
exactly with your finger.
2) Plug in an external monitor
3) Try the same actions as in step 1

Expected results:
The touchscreen continues to operate as in step 1, allowing you to manipulate
items on the display that contains the touchscreen. The touchscreen does not
interact with windows, etc on the external monitor

Actual results:
The touchscreen is remapped across both displays. The result is that touch
events no longer happen 'under the finger'. Assuming the two displays are the
same size and resolution, moving your finger 1cm will cause the window or other
objects to move 2cm onscreen. It becomes impossible to use the touchscreen to
interact with widgets (menus, buttons, etc).

This is described in couple places:

http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system

http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xinput 1.6.1-1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins:
[core,commands,composit

[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup

Here is the xinput list-props while the second screen (AOC) is disconnected 
Here the touch works as expected

xinput list-props 11
Device 'Weida Hi-Tech CoolTouch® System':
Device Enabled (169):   1
Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Calibration Matrix (308):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Calibration Matrix Default (309):  1.00, 0.00, 
0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Send Events Modes Available (291): 1, 0
libinput Send Events Mode Enabled (292):0, 0
libinput Send Events Mode Enabled Default (293):0, 0
Device Node (294):  "/dev/input/event4"
Device Product ID (295):9589, 49920

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

Title:
  Touchscreen controls both screens in dual-monitor setup

Status in GNOME Settings Daemon:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Trusty:
  Confirmed
Status in unity-settings-daemon source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  Laptops and all-in-one systems with touchscreens don't currently map
  the touch input device onto the internal display. As a result, when
  the screen changes (e.g. the main output is rotated or an external
  output is connected), the touch input device maps onto the entire
  screen, regardless of the only relevant area, thus making the
  touchscreen completely useless.

  [Impact]
   * The touchscreen becomes unusable if an external output is connected or if 
the main output is rotated.

  [Test Case]
   * Either plug in an external monitor or rotate the internal monitor
  - Expected: the touchscreen should respond to touch as usual.
  - Bad behavior: the touchscreen is unusable and responds by selecting 
areas other than the one the user actually selects.

  [Regression Potential]
   * Low, it only affects the main touchscreen (tablets or multiple 
touchscreens are not supported) and it only adds a feature that is currently 
missing.

  [Other Info]
   * N/A

  ---

  My laptop has a touchscreen. It works fine in 14.04 until I plug in an
  external monitor. When using an external monitor, input from the
  touchscreen is remapped so that the touchscreen provides input to both
  monitors. The result is that there is no longer a 1:1 correspondence
  between moving your finger and the cursor. This is confusing and
  difficult to use.

  A touchscreen is a direct input device (vs an indirect one like a
  mouse/touchpad); input from the touchscreen should be bound to the
  physical display that it's attached to.

  To reproduce:
  1) On a computer with a touchscreen, use the touchscreen to move a window 
around, including to the edges of the screen. Note that the window moves 
exactly with your finger.
  2) Plug in an external monitor
  3) Try the same actions as in step 1

  Expected results:
  The touchscreen continues to operate as in step 1, allowing you to manipulate 
items on the display that contains the touchscreen. The touchscreen does not 
interact with windows, etc on the external monitor

  Actual results:
  The touchscreen is remapped across both displays. The result is that touch 
events no longer happen 'under the finger'. Assuming the two displays are the 
same size and resolution, moving your finger 1cm will cause the window or other 
objects to move 2cm onscreen. It becomes impossible to use the touchscreen to 
interact with widgets (menus, buttons, etc).

  This is described in couple places:
  
http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system
  
http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xinput 1.6.1-1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar  3 14:41:14 2014
  DistUpgraded: 2014-02-12 13:40:42,704 DEBUG e

[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup

There is a workaround via

xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1

There needs to be some kind of detection to do this automatically and
create a systemD systemctl file.

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

Title:
  Touchscreen controls both screens in dual-monitor setup

Status in GNOME Settings Daemon:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Trusty:
  Confirmed
Status in unity-settings-daemon source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  Laptops and all-in-one systems with touchscreens don't currently map
  the touch input device onto the internal display. As a result, when
  the screen changes (e.g. the main output is rotated or an external
  output is connected), the touch input device maps onto the entire
  screen, regardless of the only relevant area, thus making the
  touchscreen completely useless.

  [Impact]
   * The touchscreen becomes unusable if an external output is connected or if 
the main output is rotated.

  [Test Case]
   * Either plug in an external monitor or rotate the internal monitor
  - Expected: the touchscreen should respond to touch as usual.
  - Bad behavior: the touchscreen is unusable and responds by selecting 
areas other than the one the user actually selects.

  [Regression Potential]
   * Low, it only affects the main touchscreen (tablets or multiple 
touchscreens are not supported) and it only adds a feature that is currently 
missing.

  [Other Info]
   * N/A

  ---

  My laptop has a touchscreen. It works fine in 14.04 until I plug in an
  external monitor. When using an external monitor, input from the
  touchscreen is remapped so that the touchscreen provides input to both
  monitors. The result is that there is no longer a 1:1 correspondence
  between moving your finger and the cursor. This is confusing and
  difficult to use.

  A touchscreen is a direct input device (vs an indirect one like a
  mouse/touchpad); input from the touchscreen should be bound to the
  physical display that it's attached to.

  To reproduce:
  1) On a computer with a touchscreen, use the touchscreen to move a window 
around, including to the edges of the screen. Note that the window moves 
exactly with your finger.
  2) Plug in an external monitor
  3) Try the same actions as in step 1

  Expected results:
  The touchscreen continues to operate as in step 1, allowing you to manipulate 
items on the display that contains the touchscreen. The touchscreen does not 
interact with windows, etc on the external monitor

  Actual results:
  The touchscreen is remapped across both displays. The result is that touch 
events no longer happen 'under the finger'. Assuming the two displays are the 
same size and resolution, moving your finger 1cm will cause the window or other 
objects to move 2cm onscreen. It becomes impossible to use the touchscreen to 
interact with widgets (menus, buttons, etc).

  This is described in couple places:
  
http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system
  
http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xinput 1.6.1-1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar  3 14:41:14 2014
  DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, 
x86_64: installed
   virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1886075] Re: Switch app windows using mouse wheel over dock icon

2020-07-18 Thread crysman

https://github.com/micheleg/dash-to-dock/issues/1274

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1274
   https://github.com/micheleg/dash-to-dock/issues/1274

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

Title:
  Switch app windows using mouse wheel over dock icon

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

Bug description:
  Hello, this is not a BUG, rather a feature request, which possibly
  shall be placed elsewhere (where?)

  I'm used to very useful behavior from XFce and that is hovering over various 
icons in system bars and using the wheel actually performs actions immediately 
like e.g.:
  1) in/decreasing volume while on sound icon
  2) switching app windows while on app icon - would be extreme useful here in 
GNOME since more apps windows are already marked by small dots sou user is very 
aware that there are more windows... I know there is ALT+~ but when using mouse 
only its not an option...
  ...

  I've searched event through GNOME tweaks, but no luck - have not found
  it.

  Any way how to add this behavior?

  Thanks a lot #McZ

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  2 19:02:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1835644] Re: CRL files are not accessible for the Verify CRL options

2020-07-18 Thread Mike

(Voila)[https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/issues/57]

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues #57
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/57

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

Title:
  CRL files are not accessible for the Verify CRL options

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  The Network Manager GUI options 'Verify CRL from file' and 'Verify CRL
  from directory' won't work because the openvpn process cannot access
  the files since being run with chroot, so the connection fails:

  nm-openvpn[5069]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded
  nm-openvpn[6135]: Options error: --crl-verify fails with 
'/var/lib/openvpn/chroot//home/steve/VPN/config/crl.rsa.4096.pem': No such file 
or directory (errno=2)

  Thanks.

  Ubuntu 19.04
  network-manager-openvpn, network-manager-openvpn-gnome 1.8.10-1
  openvpn 2.4.6-1ubuntu3.1

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

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

[Desktop-packages] [Bug 1888050] [NEW] Add UFW application profile

2020-07-18 Thread Fred

Public bug reported:

Downloads with Transmission is slow when the UFW firewall is enabled.

Add a UFW application profile.
Here is one: 
https://github.com/ageis/ufw-application-profiles/blob/master/applications.d/Transmission

Seems port 51413 needs to be allowed.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: transmission-gtk 3.00-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Jul 18 12:52:26 2020
InstallationDate: Installed on 2013-12-26 (2395 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: transmission
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy third-party-packages

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

Title:
  Add UFW application profile

Status in transmission package in Ubuntu:
  New

Bug description:
  Downloads with Transmission is slow when the UFW firewall is enabled.

  Add a UFW application profile.
  Here is one: 
https://github.com/ageis/ufw-application-profiles/blob/master/applications.d/Transmission

  Seems port 51413 needs to be allowed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: transmission-gtk 3.00-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Jul 18 12:52:26 2020
  InstallationDate: Installed on 2013-12-26 (2395 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1802039] Re: Firefox without titlebar has visual glitches when maximizing/unmaximizing

2020-07-18 Thread Adolfo Jayme

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

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

Title:
  Firefox without titlebar has visual glitches when
  maximizing/unmaximizing

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  There is a relatively new feature in Firefox that allows you to hide
  the title bar (I'm running Firefox 63.0), which is very helpful when
  you have a low resolution screen.  However, when changing the
  maximization state, some visual gitches occur.  I didn't notice this
  glitching when running Kubuntu or Ubuntu Budgie on two separate
  systems.

  To try this, go to your Firefox Menu, click Customize, and uncheck
  "Title Bar" at the bottom left.  Then unmaximize the window and then
  remaximize it.

  What it's supposed to look like: https://pasteboard.co/HM0h8oB.png
  Unmaximized (note the large transparent section): 
https://pasteboard.co/HM0hpud.png
  Remaximized (note the duplicate set of close buttons): 
https://pasteboard.co/HM0hCf5.png

  Also another interesting bug I noticed...if you try to use Firefox in
  the no titlebar state with the global menu enabled (e.g. Contemporary,
  Cupertino, or Mutiny panel layouts), the window buttons are not placed
  correctly, being on the window border.

  Systems tried on:

  Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with 
hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 
1366x768 (screenshots from this system)
  Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 
Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900

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

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

[Desktop-packages] [Bug 1792910] Re: Firefox doesn't use the session's theme

2020-07-18 Thread Adolfo Jayme

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

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

Title:
  Firefox doesn't use the session's theme

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox doesn't use Adwaita's theme for it. See the screenshot.

  I don't use vanilla GNOME on other distributions so I'm not entirely
  sure what the correct behaviour is but pretty sure Firefox is not
  supposed to be using the Yaru(?) theme? I have the communitheme snap
  (0.1 (1171)) installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 17 11:17:45 2018
  InstallationDate: Installed on 2017-08-03 (409 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (148 days ago)

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

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

[Desktop-packages] [Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

2020-07-18 Thread L3P3

Hello, I am using amdgpu and mate on debian, but I have the very same
issue. The only way to fix it was to downgrade the Kernel to 5.3.0. I
already wrote to the amdgpu devs but got no response... My message was,
back then:

Hi, on my netbook (debian bullseye, AMD A4, Sea Islands), after
updating the kernel to version 5.4.6 and logging into mate desktop, my
screen looked like this (see attached picture).
If you look at the image, do you have any idea what is happening
there? To me it looks like the framebuffer data is misinterpreted at
some stage. The picture looks good on the lightdm login screen, it is
only corrupted when I start a user session and when I then switch to a
console (ctrl+1), the screen looks correct for a second before it
switches. When I switch back (ctrl+7), it looks correct for a second
and afterwards, it turns corrupted again. I was looking into these
commits a bit but I don't have any idea... Maybe mate/marco is doing
something it shouldn't but then, much more people would have problems
now...
I took a screenshot but on that, everything looked fine, that is why I
took a picture. I assume it came by one of these commits, since these
were the only amdgpu changes between a working and a non-working
kernel:

commit 9375fa3799293da82490f0f1fa1f1e7fabae2745
Author: changzhu 
Date:   Tue Dec 10 22:00:59 2019 +0800

drm/amdgpu: add invalidate semaphore limit for SRIOV and picasso in
gmc9

commit 90f6452ca58d436de4f69b423ecd75a109aa9766 upstream.

It may fail to load guest driver in round 2 or cause Xstart problem
when using invalidate semaphore for SRIOV or picasso. So it needs avoid
using invalidate semaphore for SRIOV and picasso.

Signed-off-by: changzhu 
Reviewed-by: Christian König 
Reviewed-by: Huang Rui 
Signed-off-by: Alex Deucher 
Signed-off-by: Greg Kroah-Hartman 

commit bf8ae461a23577a9884f993b31b31f15dd7d6c0a
Author: changzhu 
Date:   Tue Dec 10 10:23:09 2019 +0800

drm/amdgpu: avoid using invalidate semaphore for picasso

commit 413fc385a594ea6eb08843be33939057ddfdae76 upstream.

It may cause timeout waiting for sem acquire in VM flush when using
invalidate semaphore for picasso. So it needs to avoid using invalidate
semaphore for piasso.

Signed-off-by: changzhu 
Reviewed-by: Huang Rui 
Signed-off-by: Alex Deucher 
Signed-off-by: Greg Kroah-Hartman 

commit f45858245286fa901e8abf36776df7e99d9a9581
Author: Xiaojie Yuan 
Date:   Wed Nov 20 14:02:22 2019 +0800

drm/amdgpu/gfx10: re-init clear state buffer after gpu reset

commit 210b3b3c7563df391bd81d49c51af303b928de4a upstream.

This patch fixes 2nd baco reset failure with gfxoff enabled on
navi1x.

clear state buffer (resides in vram) is corrupted after 1st baco reset,
upon gfxoff exit, CPF gets garbage header in CSIB and hangs.

Signed-off-by: Xiaojie Yuan 
Reviewed-by: Hawking Zhang 
Signed-off-by: Alex Deucher 
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman 

commit eebab68448a6bbb9b899216b6e889057f6f4498d
Author: Xiaojie Yuan 
Date:   Thu Nov 14 16:56:08 2019 +0800

drm/amdgpu/gfx10: explicitly wait for cp idle after halt/unhalt

commit 1e902a6d32d73e4a6b3bc9d7cd43d4ee2b242dea upstream.

50us is not enough to wait for cp ready after gpu reset on some navi
asics.

Signed-off-by: Xiaojie Yuan 
Suggested-by: Jack Xiao 
Acked-by: Alex Deucher 
Signed-off-by: Alex Deucher 
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman 

commit 69e0a0d5bcc4dd677ea460b172a1bec4127c650d
Author: changzhu 
Date:   Tue Nov 19 11:13:29 2019 +0800

drm/amdgpu: invalidate mmhub semaphore workaround in gmc9/gmc10

commit f920d1bb9c4e77efb08c41d70b6d442f46fd8902 upstream.

It may lose gpuvm invalidate acknowldege state across power-gating off
cycle. To avoid this issue in gmc9/gmc10 invalidation, add semaphore acquire
before invalidation and semaphore release after invalidation.

After adding semaphore acquire before invalidation, the semaphore
register become read-only if another process try to acquire semaphore.
Then it will not be able to release this semaphore. Then it may cause
deadlock problem. If this deadlock problem happens, it needs a semaphore
firmware fix.

Signed-off-by: changzhu 
Acked-by: Huang Rui 
Signed-off-by: Alex Deucher 
Cc: sta...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman 

commit b23e536fc4d58308e3e1ae0569327995995ee378
Author: changzhu 
Date:   Tue Nov 19 10:18:39 2019 +0800

drm/amdgpu: initialize vm_inv_eng0_sem for gfxhub and mmhub

commit 6c2c8972374ac5c35078d36d7559f64c368f7b33 upstream.

SW must acquire/release one of the vm_invalidate_eng*_sem around the
invalidation req/ack. Through this way,it can avoid losing invalidate
acknowledge state across power-gating off cycle.
To use vm_invalidate_eng*_sem, it needs to initialize
vm_invalidate_eng*_sem firstly.

[Desktop-packages] [Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

2020-07-18 Thread L3P3

And for completeness, here is what my screen looks like:

** Attachment added: "IMG_20200212_225243.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1882525/+attachment/5393710/+files/IMG_20200212_225243.jpg

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

Status in marco package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu 
boots normally to the display manager (login screen) as expected. But once I 
log in, everything on the screen is cut up into horizontal slices, with each 
slice offset farther right than the slice above, and squares of random colors 
running diagonally across the screen. I've attached a picture of my monitor 
showing the issue for reference.
  My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 
3 2200G APU, and using that APU's integrated graphics.
  In terms of software I'm running Ubuntu 20.04, which I just upgraded to and 
did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems 
fixed in the new kernel. I don't believe they're related but I figure it's 
worth mentioning.
  I tried adding the nomodeset kernel option at boot, and it's an effective 
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if 
this was caused by some quirk of my particular software setup, and successfully 
reproduced the bug, proving it wasn't.
  If you'd like me to, I can provide log files, system information, etc. or 
help narrow it down by testing workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun  8 06:41:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
  InstallationDate: Installed on 2019-10-20 (231 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450M-A
  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.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A: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.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/marco/+bug/1882525/+subscriptions

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

[Desktop-packages] [Bug 1837318] Re: Cannot store password. Password prompt never ends

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

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

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

Title:
  Cannot store password. Password prompt never ends

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Cannot store password using secret-tool.

  I do the following:

  $ secret-tool store --label='MyService' service myservice
  Password: 
  sf
  ^C

  The thing is when I hit ENTER and inserting the password, the password
  prompt never end. So I have to hit Ctrl+C to quit the program, and
  hence the password is not saved.

  Here are my system details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  $ apt-cache policy libsecret-tools
  libsecret-tools:
Installed: 0.18.6-1
Candidate: 0.18.6-1
Version table:
   *** 0.18.6-1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2020-07-18 Thread teo1978

I'm having this issue. I googled for the name of the process that was
eating up 100% of CPU and, surprise! A bug reported in 20-fucking-12 and
still not fixed!

Great job, Ubuntu!

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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

[Desktop-packages] [Bug 1837318] Re: Cannot store password. Password prompt never ends

2020-07-18 Thread Gernot Leitgab

It is working on my actual workstation:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS (beaver-three-eyed-raven X92)
Release:18.04
Codename:   bionic

$ apt-cache policy libsecret-tools
libsecret-tools:
  Installiert:   0.18.6-1
  Installationskandidat: 0.18.6-1
  Versionstabelle:
 *** 0.18.6-1 500
500 http://at.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

But I have the same problem on my fresh installed workstation:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename:   focal

$ apt-cache policy libsecret-tools
libsecret-tools:
  Installiert:   0.20.3-0ubuntu1
  Installationskandidat: 0.20.3-0ubuntu1
  Versionstabelle:
 *** 0.20.3-0ubuntu1 500
500 http://at.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 0.20.2-1 500
500 http://at.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

So maybe it has to do with a (missing) setting or it is the result of an
incomplete setup?

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

Title:
  Cannot store password. Password prompt never ends

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Cannot store password using secret-tool.

  I do the following:

  $ secret-tool store --label='MyService' service myservice
  Password: 
  sf
  ^C

  The thing is when I hit ENTER and inserting the password, the password
  prompt never end. So I have to hit Ctrl+C to quit the program, and
  hence the password is not saved.

  Here are my system details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  $ apt-cache policy libsecret-tools
  libsecret-tools:
Installed: 0.18.6-1
Candidate: 0.18.6-1
Version table:
   *** 0.18.6-1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1886626] Re: after login to gnome with snd_hda_intel 0000:00:1f.3: No response from codec

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  after login to gnome with snd_hda_intel :00:1f.3: No response from
  codec

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After login to gnome, login takes an unsual amount of time.
  Goes back to login screen.
  On second login, works normally but audio sliders are not showing correctly. 
After a while, it operates normally.
  Logs are showing a lot of
  snd_hda_intel :00:1f.3: No response from codec, resetting bus:last 
cmd0x20a70500
  +pci::00:1f.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-1063.68-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1063-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  killian68   1816 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 08:56:11 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  InstallationDate: Installed on 2020-04-02 (96 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.11
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886626/+subscriptions

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

[Desktop-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade (LANG=de_AT.UTF-8)

2020-07-18 Thread Marcello Bassani

I feel so sorry, but I did NOT continue with 20.04 - Focal Fossa, yet 
downgraded to 18.04 via backup.
I couldn't even find out, where GnomeTweaks > Fonts is because EVERY SYSTEM 
FONT was unreadable. I won't try to upgrade this machine furthermore. Please, 
mark this thread as solved / unsolved. 
Best Regards

P.S.: "  'journalctl -b 0'  " might have been possible, yet my efforts
had been overdue, in my eyes.

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

Title:
  Square rectangles instead of system fonts after upgrade
  (LANG=de_AT.UTF-8)

Status in pango1.0 package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my room mate's Fujitsu Esprimo Desktop PC  to 20.04
  Focal Fossa (from Bionic 18.04):

  Any system font line is being displayed distorted / erroneous / in
  sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set
  wouldn't be installed at all... Tthe 'gsettings'-procedure from some
  link mentioned on askubuntu-com wouldn't help either (with copy&paste
  into unreadable terminal display font output) Gnome-tweak didn't help,
  BUT I can copy text from terminal into libreoffice document and thus
  make it readable afterwards. I cannot find any information about
  "system font output/printing" on the whole internet leaving me with a
  mysrltery about how that stuff works from xserver to gnome, Wayland-
  session login IMPOSSIBLE in order to print the correct display font
  ... I will attach some screenshots later on if possible.

  P.S.: firefox/libreoffice fonts are being displayed correctly inside
  any homepage

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 12 10:55:08 2020
  DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed
   nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed
   rtlwifi-new, 0.10: added
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801]
  InstallationDate: Installed on 2017-08-28 (1048 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  LightdmLog:
   [+6033.49s] DEBUG: Seat seat0 changes active session to 
   [+6033.53s] DEBUG: Seat seat0 changes active session to c5
   [+6033.53s] DEBUG: Session c5 is already active
  MachineType: FUJITSU SIEMENS ESPRIMO P
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago)
  dmi.bios.date: 10/11/2007
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.12.2312.A3
  dmi.board.name: D2312-A3
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D2312-A3
  dmi.chassis.type: 2
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: ESPP
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP:
  dmi.product.name: ESPRIMO P
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
  xserver.bootTime: Sat Jul 11 20:24:02 2020
  xserver.config

[Desktop-packages] [Bug 1888060] [NEW] Update to 3.36.4 and SRU it

2020-07-18 Thread Treviño

Public bug reported:

[ Impact ]

That's the current GNOME stable update, including some fixes and translation 
updates
https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.4

[ Test case ]

The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

GNOME Shell and its components should continue working

[ Regression potential ]

Calendar server received a major change, so need to ensure that events
are still properly populating the gnome-shell calendar.

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Affects: gnome-shell (Ubuntu Focal)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

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

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

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

** Changed in: gnome-shell (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Update to 3.36.4 and SRU it

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  Calendar server received a major change, so need to ensure that events
  are still properly populating the gnome-shell calendar.

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

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

[Desktop-packages] [Bug 1871868] Re: Shell dialog text is truncated and ellipsized

2020-07-18 Thread Treviño

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

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  Shell dialog text is truncated and ellipsized

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  Fix Committed

Bug description:
  When trying to start a virtual machine with Gnome Boxes, I get a
  prompt about keyboard shortcuts. The prompt text is localized, but
  translated back to English (I think, based on [1]) it says:

  Boxes wants to inhibit shortcuts

  You can restore shortcuts by pressing Super+Escape.

  In my locale (Finnish), it says

  Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

  Voit palauttaa pikanäppäinten toiminnan painamalla Super...

  (sic; see attached photo)

  So the actual key combination is truncated, defeating the point of
  that part of the text.

  This isn't a localization error (AFAICT; see [2]). It's caused by the
  text being forced to fit on a single line of an arbitrarily fixed
  width, instead of wrapping to span as many lines as needed.

  (I'm reporting this against gnome-shell as opposed gnome-boxes based
  on [3]. Feel free to reassign as necessary.)

  * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
  * [2] 
https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10&show=all&search=pikan%C3%A4pp%C3%A4inten
  * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 18:29:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-13 (1274 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)

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

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

[Desktop-packages] [Bug 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days

2020-07-18 Thread Treviño

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

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  gnome-shell-calendar-server leaks GBs of memory every few days

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Focal:
  Fix Committed
Status in gnome-shell package in Debian:
  New

Bug description:
  It's been happening repeatedly over the last maybe week? I have to
  manually kill it about once a day, when I start to feel everything
  slow down as the OS starts to swap.

  Actually, I tracked down and fixed a few leaks in the code, and it
  looks stable so far. I'll submit a patch soon, as well as send the fix
  upstream to Gnome.

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

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

[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2020-07-18 Thread Shashwat Mehta

+1

On a fresh 20.04 LTS machine. Saw the dialog after waking up from suspend. 
Exact same behavior as described earlier.
Alt+F2 followed by 'r' did the trick.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Desktop-packages] [Bug 1888062] [NEW] autopkgtest became very flaky in Groovy

2020-07-18 Thread Balint Reczey

Public bug reported:

https://autopkgtest.ubuntu.com/packages/u/udisks2/groovy/amd64

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/amd64/u/udisks2/20200710_213220_c8468@/log.gz

...
SMART status of first internal hard disk ... Failed to query whether SMART is 
available: Operation not supported
[N/A] ok

==
ERROR: test_0_create_teardown (__main__.Luks)
LUKS create/teardown
--
Traceback (most recent call last):
  File "src/tests/integration-test", line 1361, in test_0_create_teardown
self.setup_crypto_device()
  File "src/tests/integration-test", line 1330, in setup_crypto_device
self.fs_create(None, 'ext4', GLib.Variant('a{sv}', {
  File "src/tests/integration-test", line 354, in fs_create
block.call_format_sync(fs_type, options, None)
gi.repository.GLib.GError: udisks-error-quark: 
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error synchronizing after 
initial wipe: Timed out waiting for object (0)

...

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


** Tags: update-excuse

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

Title:
  autopkgtest became very flaky in Groovy

Status in udisks2 package in Ubuntu:
  New

Bug description:
  https://autopkgtest.ubuntu.com/packages/u/udisks2/groovy/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  groovy/groovy/amd64/u/udisks2/20200710_213220_c8468@/log.gz

  ...
  SMART status of first internal hard disk ... Failed to query whether SMART is 
available: Operation not supported
  [N/A] ok

  ==
  ERROR: test_0_create_teardown (__main__.Luks)
  LUKS create/teardown
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 1361, in test_0_create_teardown
  self.setup_crypto_device()
File "src/tests/integration-test", line 1330, in setup_crypto_device
  self.fs_create(None, 'ext4', GLib.Variant('a{sv}', {
File "src/tests/integration-test", line 354, in fs_create
  block.call_format_sync(fs_type, options, None)
  gi.repository.GLib.GError: udisks-error-quark: 
GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error synchronizing after 
initial wipe: Timed out waiting for object (0)

  ...

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

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

[Desktop-packages] [Bug 1888065] [NEW] Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt

Public bug reported:

I upgraded to 20.04 over a month ago and it's been working fine. I have
one monitor (external). I tried turning on fractional scaling in the
display settings and the screen immediately turned black. I waited,
expecting the "confirm changes" prompt to timeout and restore the
display. It never did.

Next I hard rebooted, but as soon as I'd entered my password to login,
the screen went black again. Tried this a few more times. I then booted
to a root console and `apt update/upgrade` to get all updates.
Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
to get a virtual console, then back to F2, and a few other things. At
some point I was able to log back in.

Foolishly I assumed the issue was just with fractional scaling, and back
in Display settings I for some reason decided to experiment further and
flipped the display orientation to portrate. Immediately I got a black
screen and ended back in the same reboot loop, always getting a black
screen as soon as I tried to log back in. Searching online I couldn't
seem to find a way to revert the display orientation. From another
virtual console I was unable to run xrandr or start a wayland session to
get to the settings panel. To do that I was trying to run:

  dbus-run-session -- gnome-shell --display-server --wayland

But that's just something I found on the Web, I have no idea what I'm
doing there. It just gave the error:

(gnome-shell:) mutter-warning: **:  Failed to open 
gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted
(gnome-shell:) mutter-warning: **:  Failed to 
create backend: No GPUs found

Eventually I found a suggestion on the Web to unplug the cable to the
display, and after experimenting with that a bit and switching between
virtual consoles, at some point it was logged in with a working display
... well, sort of. The colors and icons are weird like it's lost theming
or something. Going into the Display settings it seems that the
orientation has also been reset to landscape.

I'm filing this bug before restarting the machine so I can report the
system scan it has taken. At this point I've no idea whether I'll be
able to log back in again after a reboot. I'll try that now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:21: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  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 18 17:21:56 2020
DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
InstallationDate: Installed on 2019-11-03 (257 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Z4 G4 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
dmi.bios.date: 03/21/2019
dmi.bios.vendor: HP
dmi.bios.version: P62 v01.75
dmi.board.name: 81C5
dmi.board.vendor: HP
dmi.board.version: MVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z4 G4 Workstation
dmi.product.sku: 5FN34US#ABA
dmi.sys.vendor: HP
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

[Desktop-packages] [Bug 1866381] Re: evince no longer remembers last used folder/directory when saving

2020-07-18 Thread clubsoda

Nice find, thank-you. It's good at least to know why it's broken.

scenario:
A firefox downloaded PDF comes up in evince from /tmp/mozilla_user0
I want to save a copy to $HOME/preferred/directory using ctrl-s

As a test, I added a soft link from ~/Documents to ~/preferred/directory
and tried the same procedure with evince 3.28.4 but it still wants to
save to $HOME.

The newer version also removes the menu bar and the hotkey hints so for
now I'm sticking with evince 3.18.2

I guess this is a WONTFIX but thanks again.

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

Title:
  evince no longer remembers last used folder/directory when saving

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  On upgrading from Xubuntu 16.04 (xenial) to Xubuntu 18.04.2 LTS
  (bionic), evince no longer saves a copy of a downloaded document to
  the previously used directory for saving documents but defaults to
  $HOME every time.

  As a workaround, downgrading evince, evince-common, libevdocument3-4
  and libevview3-3 from their bionic version 3.28.4-0ubuntu1 to their
  xenial version 3.18.2-1ubuntu4.6 restores the expected behaviour.

  For users unfamiliar, those old packages may be obtained for example from:-
  https://launchpad.net/ubuntu/xenial/amd64/evince/

  Regards.

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

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

[Desktop-packages] [Bug 1888066] [NEW] groovy nautilus right click compress option missing

2020-07-18 Thread corrado venturini

Public bug reported:

On Groovy nautilus window i right click on a text file and I don't see
the 'compress' option like in Focal

Open a nautilus window
right click on a file
expected: drop-down menu including 'compress' option
What happened instead: drop-down menu NO 'compress' option

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.37.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu42
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 18 18:41:41 2020
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'186'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(653, 550)'
InstallationDate: Installed on 2020-07-14 (4 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200714)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug groovy

** Attachment added: "groovy.png"
   https://bugs.launchpad.net/bugs/1888066/+attachment/5393826/+files/groovy.png

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

Title:
  groovy nautilus right click compress option missing

Status in nautilus package in Ubuntu:
  New

Bug description:
  On Groovy nautilus window i right click on a text file and I don't see
  the 'compress' option like in Focal

  Open a nautilus window
  right click on a file
  expected: drop-down menu including 'compress' option
  What happened instead: drop-down menu NO 'compress' option

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: nautilus 1:3.37.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 18 18:41:41 2020
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'186'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(653, 550)'
  InstallationDate: Installed on 2020-07-14 (4 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200714)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1888065] Re: Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt

The issue seems gone after a reboot. Theming and colors are back to
normal.

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

Title:
Screen dies/black after changing display orientation or enabling
fractional scaling

Status in xorg package in Ubuntu:
New

Bug description:
I upgraded to 20.04 over a month ago and it's been working fine. I
have one monitor (external). I tried turning on fractional scaling in
the display settings and the screen immediately turned black. I
waited, expecting the "confirm changes" prompt to timeout and restore
the display. It never did.

Next I hard rebooted, but as soon as I'd entered my password to login,
the screen went black again. Tried this a few more times. I then
booted to a root console and `apt update/upgrade` to get all updates.
Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
to get a virtual console, then back to F2, and a few other things. At
some point I was able to log back in.

Foolishly I assumed the issue was just with fractional scaling, and
back in Display settings I for some reason decided to experiment
further and flipped the display orientation to portrate. Immediately I
got a black screen and ended back in the same reboot loop, always
getting a black screen as soon as I tried to log back in. Searching
online I couldn't seem to find a way to revert the display
orientation. From another virtual console I was unable to run xrandr
or start a wayland session to get to the settings panel. To do that I
was trying to run:

dbus-run-session -- gnome-shell --display-server --wayland

But that's just something I found on the Web, I have no idea what I'm
doing there. It just gave the error:

(gnome-shell:) mutter-warning: **: Failed to
open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not
permitted
(gnome-shell:) mutter-warning: **: Failed to
create backend: No GPUs found

Eventually I found a suggestion on the Web to unplug the cable to the
display, and after experimenting with that a bit and switching between
virtual consoles, at some point it was logged in with a working
display ... well, sort of. The colors and icons are weird like it's
lost theming or something. Going into the Display settings it seems
that the orientation has also been reset to landscape.

I'm filing this bug before restarting the machine so I can report the
system scan it has taken. At this point I've no idea whether I'll be
able to log back in again after a reboot. I'll try that now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:21: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 435.21 Sun Aug 25 08:17:57
CDT 2019
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 18 17:21:56 2020
DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
InstallationDate: Installed on 2019-11-03 (257 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Z4 G4 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
dmi.bios.date: 03/21/2019
dmi.bios.vendor: HP
dmi.bios.version: P62 v01.75
dmi.board.name: 81C5
dmi.board.vendor: HP
dmi.board.version: MVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z4 G4 Workstation
dmi.product.sku: 5FN34US#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A

[Desktop-packages] [Bug 1750098] Re: Ubuntu software shows snaps as installed even if it failed to install

2020-07-18 Thread Danilo Alculete

this can be considered fixed

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

Title:
  Ubuntu software shows snaps as installed even if it failed to install

Status in gnome-software package in Ubuntu:
  New

Bug description:
  As stated on https://forum.snapcraft.io/t/ubuntu-software-shows-snaps-
  as-installed-even-if-it-failed-to-install/4054

  When a snap fails to install, Software center still shows the download
  as completed

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

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

[Desktop-packages] [Bug 1888077] [NEW] No startup sound played with gnome-session-canberra

2020-07-18 Thread Yousuf 'Jay' Philips

Public bug reported:

Tested on Xubuntu 20.04 with gnome-session-canberra and yaru-theme-sound
packages installed

The gnome-session-canberra package has a /usr/share/gnome/autostart
/libcanberra-login-sound.desktop but it will not run. I disabled all of
the below entries in the file and it still wouldn't run.

OnlyShowIn=GNOME;Unity;
AutostartCondition=GSettings org.gnome.desktop.sound event-sounds
X-GNOME-Autostart-Phase=Application
X-GNOME-Provides=login-sound
X-GNOME-Autostart-enabled=false
NoDisplay=true

The shutdown script /usr/share/gnome/shutdown/libcanberra-logout-
sound.sh in the same package worked fine.

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

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

Title:
  No startup sound played with gnome-session-canberra

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Tested on Xubuntu 20.04 with gnome-session-canberra and yaru-theme-
  sound packages installed

  The gnome-session-canberra package has a /usr/share/gnome/autostart
  /libcanberra-login-sound.desktop but it will not run. I disabled all
  of the below entries in the file and it still wouldn't run.

  OnlyShowIn=GNOME;Unity;
  AutostartCondition=GSettings org.gnome.desktop.sound event-sounds
  X-GNOME-Autostart-Phase=Application
  X-GNOME-Provides=login-sound
  X-GNOME-Autostart-enabled=false
  NoDisplay=true

  The shutdown script /usr/share/gnome/shutdown/libcanberra-logout-
  sound.sh in the same package worked fine.

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

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

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

2020-07-18 Thread Abhishek Roy

I am facing same problem as the problem mentioned. My keyboard is
getting freeze for few minutes after which it is again working fine. I
have checked in linux mint too, I am facing same problem. Any help in
this regard will be highly helpful in this regard.

-- 
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 1888088] [NEW] [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

Public bug reported:

Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
Similarly, selecting Fractional Scaling and then picking a scale factor has no 
effect.

This is a recently installed Ubuntu 20.04, fully updated, on a recently
released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU.
It is possible that the GPU is not being detected by Ubuntu and that is
the root cause of the problem.  I couldn't find an easy explanation
online about how to tell whether a GPU was detected or is in use.  I did
try running "tlp-stat -g" to get graphics status, but it returns without
printing anything except its version number (1.3.1).

When I choose an orientation, such as Portrait Right, the setting
changes and an "Apply" button appears in the top of the Settings window.
When I press it, up pops up a dialog asking whether I want to "Keep
these display settings?" with two options, keep or revert.  The rest of
the screen goes grey behind the dialog box, but I can already see that
the "Orientation" setting back in the Settings->Display window has been
reverted to "Landscape" without me doing anything.  Whether I choose
keep or revert, or merely let it time out after 20 seconds, the result
remains the same -- the display stays in Landscape mode and the setting
that I had made is reverted.

Regarding scaling, I can set the display scale to 100% (default) or
200%, successfully.  When I turn on the "Fractional Scaling" slider, the
graphics around the edge of the screen increase in size (the icons in
the left-hand dock, the text in the top bar), but the Scale settings do
not change (they remain "100%" and "200%").  However, if I switch to a
different setting (for example, "Mouse & Touchpad") and then back to
"Displays", the Scale settings have changed.  I have included three
screenshots (original screen, Fractional Scaling on, and after switching
to and from Displays.

When I attempt to set a fractional scale such as 125%, the "Apply"
button appears in the upper right corner.  When I press that, the
display does not scale, a pop-up asks if I want to keep or revert the
setting, but looking back at the Displays settings, the Scale has
already reverted to 100% (as above with the Orientation).

The display has been rock-solid before this, but now it started showing 
artifacts, such as 
previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sat Jul 18 14:00:38 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo Renoir [17aa:3f1a]
InstallationDate: Installed on 2020-07-16 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81X2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: EECN20WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Flex 5 14ARE05
dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
dmi.product.family: IdeaPad Flex 5 14ARE05
dmi.product.name: 81X2
dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
dmi.product.version: IdeaPad Flex 5 14ARE05
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you

[Desktop-packages] [Bug 1879742]

2020-07-18 Thread Duncan-e-chung

Hi Saeed.

Just letting you know the fix seems to work for me.

I've tried both on Firefox Developer (version 79.0b6) and Firefox
(version 78.0.2).

Thanks for your effort here.

Duncan.

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879742]

2020-07-18 Thread Docfaraday-u

Awesome! Thanks!

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879742]

2020-07-18 Thread Achronop

*** Bug 1651955 has been marked as a duplicate of this bug. ***

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879742]

2020-07-18 Thread Mitsch-r

Hi Saeed,

I can confirm that Meet is now working fine on Firefox Nightly, 80.0a1
(2020-07-12) on MacOS.

Thanks for taking care of the issue!

Best regards,
   Henrik

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879742] Re: When using Google Meet on Firefox, delay sending sound from microphone

2020-07-18 Thread Bug Watch Updater

** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  When using Google Meet on Firefox, delay sending sound from microphone

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

Bug description:
  When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for
  the first 5-10 seconds of the meeting, nobody can hear anything that I
  am saying. After that, I have no issues. I also have no issues joining
  with Chromium.

  The sound indicator on my end (the little green bars that flash when
  you are talking) start immediately, but nobody on the call hears
  anything from me.

  The only info I could find from Googling was somebody else talking about a 
similar problem:
  
https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   1813 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:05:20 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2020-05-03 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1888091] [NEW] Deform switch in the Livepatch tab

2020-07-18 Thread MadsRH

Public bug reported:

When the user isn't signed in, the switch looks deform / squeezed. See
the attached screenshot.

Maybe the blue spinner is somehow calculated into the padding and when
the spinner is gone (after "Checking availability"), the padding does
not match and the switch gets squeezed.

This is only a visual bug, non critical, but should be low hanging
fruit.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1888091/+attachment/5393946/+files/screenshot.jpg

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

Title:
  Deform switch in the Livepatch tab

Status in software-properties package in Ubuntu:
  New

Bug description:
  When the user isn't signed in, the switch looks deform / squeezed. See
  the attached screenshot.

  Maybe the blue spinner is somehow calculated into the padding and when
  the spinner is gone (after "Checking availability"), the padding does
  not match and the switch gets squeezed.

  This is only a visual bug, non critical, but should be low hanging
  fruit.

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

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

[Desktop-packages] [Bug 1888092] [NEW] package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version:

2020-07-18 Thread Edson Canganjo

Public bug reported:

I have problems while install ubuntu 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ibus-data 1.5.22-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jul 18 22:43:47 2020
DuplicateSignature:
 package:ibus-data:1.5.22-2ubuntu2
 Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
  unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: ibus
Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  New

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1883054] Re: Built-in audio device not available until alsa is reloaded

2020-07-18 Thread Stephen Warren

For me, this issue has now been resolved; I assume due to the pulseaudio
package updates that I installed yesterday, but it might have been fixed
for a few days longer.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Fix Released

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

Title:
  Built-in audio device not available until alsa is reloaded

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and
  audio worked fine, using either the built-in speakers/mic on the
  laptop or via a USB headset when that was plugged in.

  However, after upgrading to 20.04, the built-in audio device is no
  longer available until I run "sudo alsa force-reload". Wthhout that
  WAR, all I see is a dummy audio device. Luckily the USB headset works
  fine, if plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  swarren7664 F pulseaudio
   /dev/snd/controlC0:  swarren7664 F pulseaudio
   /dev/snd/pcmC0D0c:   swarren7664 F...m pulseaudio
   /dev/snd/pcmC0D0p:   swarren7664 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Jun 10 23:57:08 2020
  InstallationDate: Installed on 2016-03-03 (1561 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to focal on 2020-06-07 (4 days ago)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1DETA6W (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ERCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1DETA6W(2.32):bd08/28/2019:svnLENOVO:pn20ERCTO1WW:pvrThinkPadP70:rvnLENOVO:rn20ERCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P70
  dmi.product.name: 20ERCTO1WW
  dmi.product.sku: LENOVO_MT_20ER_BU_Think_FM_ThinkPad P70
  dmi.product.version: ThinkPad P70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883054/+subscriptions

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

[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen just after I slide the Fractional 
Scaling slider.  The icons in the left margin, and the text at the top of the 
screen, have changed size (despite me not picking any new scale) and nothing 
else has scaled."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393947/+files/Screenshot%20from%202020-07-18%2014-21-41%20-%20fractional%20scaling%20with%20large%20dock%20and%20top%20bar%20but%20nothing%20else%20scaled.png

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

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700

[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen before I slide the "Fractional Scaling" 
slider."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393945/+files/Screenshot%20from%202020-07-18%2014-21-25%20-%20before%20fractional%20scaling.png

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

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14AR

[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Attachment added: "This is my screen after I chose "125%" as a fractional 
scale, then pressed Apply.  The pop-up has dimmed the underlying windows, but 
you can see that the Scale setting in the underlying Displays window has 
reverted to "100%", and nothing on the screen has changed its scale to 125%."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888088/+attachment/5393948/+files/Screenshot%20from%202020-07-18%2014-27-40%20-%20attempted%20125%25%20with%20popup.png

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

Title:
  [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.

  This is a recently installed Ubuntu 20.04, fully updated, on a
  recently released laptop/tablet that uses an AMD Ryzen 4500U
  integrated CPU/GPU.  It is possible that the GPU is not being detected
  by Ubuntu and that is the root cause of the problem.  I couldn't find
  an easy explanation online about how to tell whether a GPU was
  detected or is in use.  I did try running "tlp-stat -g" to get
  graphics status, but it returns without printing anything except its
  version number (1.3.1).

  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings
  window.  When I press it, up pops up a dialog asking whether I want to
  "Keep these display settings?" with two options, keep or revert.  The
  rest of the screen goes grey behind the dialog box, but I can already
  see that the "Orientation" setting back in the Settings->Display
  window has been reverted to "Landscape" without me doing anything.
  Whether I choose keep or revert, or merely let it time out after 20
  seconds, the result remains the same -- the display stays in Landscape
  mode and the setting that I had made is reverted.

  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider,
  the graphics around the edge of the screen increase in size (the icons
  in the left-hand dock, the text in the top bar), but the Scale
  settings do not change (they remain "100%" and "200%").  However, if I
  switch to a different setting (for example, "Mouse & Touchpad") and
  then back to "Displays", the Scale settings have changed.  I have
  included three screenshots (original screen, Fractional Scaling on,
  and after switching to and from Displays.

  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).

  The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700

[Desktop-packages] [Bug 1888092] Re: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: In

2020-07-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  New

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880570] Re: Dock - running applications are not/delayed updated

2020-07-18 Thread Adam Barton

If it helps I got the behaviour mostly fixed by disabling show-mounts
and clearing out some of the desktop files in ~/.gnome/apps

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

Title:
  Dock - running applications are not/delayed updated

Status in Dash to dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  The running applications, displayed in the dock are sometimes not
  updated, or only updated with a long delay (after 20-30 seconds).
  However restarting with `alt`+`F2` -> "r" -> `enter`, fixes the
  problem temporarily, just to come back shortly after. At first I
  thought it was something caused by my update to 20.04, but it even
  happens with a fresh install (dock location is at the bottom). I think
  there are multiple ways to trigger this behavior, but what worked
  reliably so far is to close the last running application, so that the
  dock is completely empty (no favorite applications in the dock - only
  the "Show applications" button on the dock). So far this triggered the
  bug every time, but I'm quite sure there were also other ways to get
  into this "dock no longer/delayed updating" state with other means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 16:36:18 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1880570/+subscriptions

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

[Desktop-packages] [Bug 1886075] Re: Switch app windows using mouse wheel over dock icon

2020-07-18 Thread Alexey Kulik

This option does exist in Ubuntu Dock. It's just disabled by default. It can be 
activated using Dconf Editor. Set the parameter 
'org.gnome.shell.extensions.dash-to-dock' to be equal to 'cycle-windows'.
It can also be easily done by running this command:

gsettings set org.gnome.shell.extensions.dash-to-dock scroll-action
'cycle-windows'

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

Title:
  Switch app windows using mouse wheel over dock icon

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

Bug description:
  Hello, this is not a BUG, rather a feature request, which possibly
  shall be placed elsewhere (where?)

  I'm used to very useful behavior from XFce and that is hovering over various 
icons in system bars and using the wheel actually performs actions immediately 
like e.g.:
  1) in/decreasing volume while on sound icon
  2) switching app windows while on app icon - would be extreme useful here in 
GNOME since more apps windows are already marked by small dots sou user is very 
aware that there are more windows... I know there is ALT+~ but when using mouse 
only its not an option...
  ...

  I've searched event through GNOME tweaks, but no luck - have not found
  it.

  Any way how to add this behavior?

  Thanks a lot #McZ

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  2 19:02:17 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-06-19 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888088] Re: [Lenovo IdeaPad Flex 5 14ARE05] Display won't rotate, nor do fractional scaling

** Description changed:

  Opening Settings -> Display and selecting an orientation other than Landscape 
doesn't work.
  Similarly, selecting Fractional Scaling and then picking a scale factor has 
no effect.
  
  This is a recently installed Ubuntu 20.04, fully updated, on a recently
  released laptop/tablet that uses an AMD Ryzen 4500U integrated CPU/GPU.
  It is possible that the GPU is not being detected by Ubuntu and that is
  the root cause of the problem.  I couldn't find an easy explanation
  online about how to tell whether a GPU was detected or is in use.  I did
  try running "tlp-stat -g" to get graphics status, but it returns without
  printing anything except its version number (1.3.1).
  
  When I choose an orientation, such as Portrait Right, the setting
  changes and an "Apply" button appears in the top of the Settings window.
  When I press it, up pops up a dialog asking whether I want to "Keep
  these display settings?" with two options, keep or revert.  The rest of
  the screen goes grey behind the dialog box, but I can already see that
  the "Orientation" setting back in the Settings->Display window has been
  reverted to "Landscape" without me doing anything.  Whether I choose
  keep or revert, or merely let it time out after 20 seconds, the result
  remains the same -- the display stays in Landscape mode and the setting
  that I had made is reverted.
  
  Regarding scaling, I can set the display scale to 100% (default) or
  200%, successfully.  When I turn on the "Fractional Scaling" slider, the
  graphics around the edge of the screen increase in size (the icons in
  the left-hand dock, the text in the top bar), but the Scale settings do
  not change (they remain "100%" and "200%").  However, if I switch to a
  different setting (for example, "Mouse & Touchpad") and then back to
  "Displays", the Scale settings have changed.  I have included three
  screenshots (original screen, Fractional Scaling on, and after switching
  to and from Displays.
  
  When I attempt to set a fractional scale such as 125%, the "Apply"
  button appears in the upper right corner.  When I press that, the
  display does not scale, a pop-up asks if I want to keep or revert the
  setting, but looking back at the Displays settings, the Scale has
  already reverted to 100% (as above with the Orientation).
  
- The display has been rock-solid before this, but now it started showing 
artifacts, such as 
+ The display has been rock-solid before this, but now it started showing 
artifacts, such as
  previous copies of the Displays window.  I've enclosed a screen shot.  Merely 
taking a screen shot also wiped out parts of the display to white; I took 
another shot to show that.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog:
-  
+ 
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 14:00:38 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
-Subsystem: Lenovo Renoir [17aa:3f1a]
+  Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 
00 [VGA controller])
+    Subsystem: Lenovo Renoir [17aa:3f1a]
  InstallationDate: Installed on 2020-07-16 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81X2
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EECN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Flex 5 14ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEECN20WW:bd04/08/2020:svnLENOVO:pn81X2:pvrIdeaPadFlex514ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrIdeaPadFlex514ARE05:
  dmi.product.family: IdeaPad Flex 5 14ARE05
  dmi.product.name: 81X2
  dmi.product.sku: LENOVO_MT_81X2_BU_idea_FM_IdeaPad Flex 5 14ARE05
  dmi.product.version: IdeaPad Flex 5 14ARE05
  dmi.sys.vendor: LENOVO
  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
  ve

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

audio-log.txt:


> pulseaudio_ps_do
jorge2  1831  0.0  0.2 1149508 20100 ?   S which pulseaudio
/usr/bin/pulseaudio

> pidof pulseaudio
1831

> pulseaudio --version
pulseaudio 13.99.1

> pactl info
Server String: /run/user/1002/pulse/native
Library Protocol Version: 33
Server Protocol Version: 33
Is Local: yes
Client Index: 79
Tile Size: 65472
User Name: jorge2
Host Name: jorge-Mate-20-4
Server Name: pulseaudio
Server Version: 13.99.1
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: alsa_input.usb-KYE_Systems_Corp._FaceCam_VGA-02.mono-fallback
Cookie: da6d:375c

> pactl list
Module #0
Name: module-device-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "13.99.1"

Module #1
Name: module-stream-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "13.99.1"

Module #2
Name: module-card-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "13.99.1"

Module #3
Name: module-augment-properties
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "13.99.1"

Module #4
Name: module-switch-on-port-available
Argument: 
Usage counter: n/a
Properties:
module.author = "David Henningsson"
module.description = "Switches ports and profiles when devices 
are plugged/unplugged"
module.version = "13.99.1"

Module #5
Name: module-switch-on-connect
Argument: 
Usage counter: n/a
Properties:
module.author = "Michael Terry"
module.description = "When a sink/source is added, switch to it 
or conditionally switch to it"
module.version = "13.99.1"

Module #6
Name: module-udev-detect
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Detect available audio hardware and load 
matching drivers"
module.version = "13.99.1"

Module #7
Name: module-alsa-card
Argument: device_id="1" name="usb-KYE_Systems_Corp._FaceCam_VGA-02" 
card_name="alsa_card.usb-KYE_Systems_Corp._FaceCam_VGA-02" namereg_fail=false 
tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"
Usage counter: 0
Properties:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "13.99.1"

Module #8
Name: module-alsa-card
Argument: device_id="0" name="pci-_00_1b.0" 
card_name="alsa_card.pci-_00_1b.0" namereg_fail=false tsched=yes 
fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes 
avoid_resampling=no card_properties="module-udev-detect.discovered=1"
Usage counter: 0
Properties:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "13.99.1"

Module #9
Name: module-native-protocol-unix
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Native protocol (UNIX sockets)"
module.version = "13.99.1"

Module #10
Name: module-default-device-restore
Argument: 
Usage counter: n/a
Properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the default sink 
and source"
module.version = "13.99.1"

Module #11
Name: module-always-sink
Argument: 
Usage counter: n/a
Properties:
module.author = "Colin Guthrie"
module.description = "Siempre tenga al menos un sumidero 
cargado aunque sea uno nulo"
module.version = "13.99.1"

Module #12
Name: module-null-sink
Argument: sink_name=auto_null 
sink_properties='device.description="Salida Ficticia"'

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

** Attachment added: "audio-log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610/+attachment/5393960/+files/audio-log.txt

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

And please also upload the dmesg. BTW, how did you update, only update the 
pulseaudio or upgrade many packages? And what is the pulseaudio version now 
(checking it by running dpkg -s pulseaudio | grep Version).
jorge2@jorge-Mate-20-4:~$ dpkg -s pulseaudio | grep Version
Version: 1:13.99.1-1ubuntu3.2lp1869819
jorge2@jorge-Mate-20-4:~$ 
I update from http://ppa.launchpad.net/kaihengfeng/fix-lp1869819/ubuntu
I'm sorry, I don't understand what you mean by "upload the dmesg. BTW", I know 
the command dmesq, what do you want me to do?

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1888098] [NEW] Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen

Public bug reported:

Ubuntu 20.04 LTS

gnome-shell:
  Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2

What I expected to happen:
When clicking a button on the primary screen to open a new window in any 
application, that window should always open on the same monitor. 

What happened instead:
Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary 
monitor.

Why this is a problem:
My setup are Point of Sale terminals and the primary (a touchscreen) and 
secondary monitors are back to back. When the cashier presses the payment type 
button, the payment type pop-up is opening on the secondary screen which is 
displayed to the customer and not accessible to the cashier who needs to 
complete the transaction. The cashier can't move the pop-up on their own as 
there is no keyboard access (all buttons needed are in the application it 
self), and the touchscreen touches on itself (most of the time).   

In the past I was able to fix this with devilspie. As this problem has been 
around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell.
 But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps 
opening all the windows on the secondary screen. 

I've tried various gnome extensions and gnome-tweaks but none of them
will open all windows (except the customer display) on the primary
monitor only.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 19 01:21:39 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-14 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ubuntu 20.04 gnome-shell places windows on second screen when started
  from primary screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04 LTS

  gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2

  What I expected to happen:
  When clicking a button on the primary screen to open a new window in any 
application, that window should always open on the same monitor. 

  What happened instead:
  Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary 
monitor.

  Why this is a problem:
  My setup are Point of Sale terminals and the primary (a touchscreen) and 
secondary monitors are back to back. When the cashier presses the payment type 
button, the payment type pop-up is opening on the secondary screen which is 
displayed to the customer and not accessible to the cashier who needs to 
complete the transaction. The cashier can't move the pop-up on their own as 
there is no keyboard access (all buttons needed are in the application it 
self), and the touchscreen touches on itself (most of the time).   

  In the past I was able to fix this with devilspie. As this problem has been 
around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell.
   But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps 
opening all the windows on the secondary screen. 

  I've tried various gnome extensions and gnome-tweaks but none of them
  will open all windows (except the customer display) on the primary
  monitor only.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.3-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 19 01:21:39 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-14 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1888092] Re: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing new version: In

2020-07-18 Thread Gunnar Hjalmarsson

That sounds as a hardware glitch. If you haven't already, can you please
try:

sudo apt install --reinstall ibus-data

and let us know if it helps.

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

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

Title:
  package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to
  make backup link of './usr/share/ibus/dicts/emoji-af.dict' before
  installing new version: Input/output error

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  I have problems while install ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ibus-data 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul 18 22:43:47 2020
  DuplicateSignature:
   package:ibus-data:1.5.22-2ubuntu2
   Unpacking ibus-data (1.5.22-2ubuntu2.1) over (1.5.22-2ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-W4DEHL/31-ibus-data_1.5.22-2ubuntu2.1_all.deb (--unpack):
unable to make backup link of './usr/share/ibus/dicts/emoji-af.dict' before 
installing new version: Input/output error
  ErrorMessage: unable to make backup link of 
'./usr/share/ibus/dicts/emoji-af.dict' before installing new version: 
Input/output error
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-data 1.5.22-2ubuntu2 failed to install/upgrade: unable to 
make backup link of './usr/share/ibus/dicts/emoji-af.dict' before installing 
new version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

dmesg>demsg.txt

** Attachment added: "the output"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610/+attachment/5393973/+files/demsg.txt

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-18 Thread Hui Wang

I planned to let you run "dmesg > dmesg.txt", then upload it to
launchpad, but now no need to upload the dmesg.

Your issue has nothing to do with this SRU, this SRU will update the
pulseaudio to 1:13.99.1-1ubuntu3.5 while the version on your machine is
ubuntu3.2lp1869819.

And According to the log in the #15, there is no any problem:
The output is null or dummy because all output device are unavailable at that 
moment:
Default Sink: auto_null
analog-output-lineout: LÃnea de salida (priority: 9000, 
latency offset: 0 usec, not available)
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo
analog-output-headphones: Auriculares analÃ³gicos (priority: 
9900, latency offset: 0 usec, not available)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:analog-stereo, 
output:analog-stereo+input:analog-stereo

After you plugging in the headphone or lineout, the output device will
not be null or dummy.


For input device, it is usb input, there is no problem too.


So how do you expect the audio to work?

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

A pair of headphones was always plugged  at the front.
Now I  connected speakers in the connector line on the back, and it works 
effectively.
The front headphones also work with the speakers connected behind. Apparently 
it requires a connector put on the back.
Thank you very much for your contribution, it has solved my problem.
Greetings from Argentina.
This text was automatically translated by google

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Desktop-packages] [Bug 1888108] [NEW] Fresh install 20.04

2020-07-18 Thread sdaigle

Public bug reported:

My Graphics are like a slide show.

Its almost as if the display drivers are not installed?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Sat Jul 18 22:08:11 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [17aa:30a3]
InstallationDate: Installed on 2020-07-17 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 10AB004DUS
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=cd7df6ea-b877-481a-9eee-6d5e2b5d770a ro quiet splash nomodeset 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKTB9AUS
dmi.board.name: SHARKBAY
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB9AUS:bd11/13/2015:svnLENOVO:pn10AB004DUS:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50510WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ThinkCentre M93p
dmi.product.name: 10AB004DUS
dmi.product.sku: LENOVO_MT_10AB
dmi.product.version: ThinkCentre M93p
dmi.sys.vendor: LENOVO
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
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Fresh install 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  My Graphics are like a slide show.

  Its almost as if the display drivers are not installed?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sat Jul 18 22:08:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated 
Graphics Controller [17aa:30a3]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 10AB004DUS
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=cd7df6ea-b877-481a-9eee-6d5e2b5d770a ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB9AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB9AUS:bd11/13/2015:svnLENOVO:pn10AB004DUS:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50510WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ThinkCentre M93p
  dmi.product.name: 10AB004DUS
  dmi.product.sku: LENOVO_MT_10AB
  dmi.product.version: ThinkCentre M93p
  dmi.sys.vendor: LENOVO
  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
  version.xserver-xorg-input-evdev: xserver-xorg-in

[Desktop-packages] [Bug 1879461] Re: Fails to play netflix or amazon music on ubuntu 20.04

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

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

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

Title:
  Fails to play netflix or amazon music on ubuntu 20.04

Status in firefox package in Ubuntu:
  Expired

Bug description:
  the extension does not work to play netflix and it does not play songs
  from amazon music in ubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 76.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richi  1603 F pulseaudio
  BuildID: 20200507114007
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 03:57:29 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-05-18 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.19 metric 600
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:738
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=76.0.1/20200507114007 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1425
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 54.57
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.35:bd02/08/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr059813202710010010100:rvnHewlett-Packard:rn1425:rvr54.57:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=G42
  dmi.product.name: HP G42 Notebook PC
  dmi.product.sku: LE642LA#ABM
  dmi.product.version: 059813202710010010100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1879326] Re: DNS resolution ceased to work after update

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  DNS resolution ceased to work after update

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  Hi

  I did a Focal install on 14th of May 2020, could work until in the
  night of 16th of May 2020 and in the morning of the 18th of May 2020 I
  could not resolve domain names anymore. I can ping DNS servers but the
  resolution to IP addresses fails. I have switched on automatic
  installation of security relevant updates.

  I can reproduce the behaviour with a fresh install accepting all the
  updates there are. I did not try to find out which update is the
  cause.

  See the behaviour below where I even have tried to work around by removing 
the DNS server of my router:
  thiemo @ Fujitsu-HO ~ :-( % systemd-resolve --status  
20-05-18 12:54
  Global
 LLMNR setting: no
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp0s25)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 139.18.25.33
139.18.25.34
77.59.232.36
62.167.241.5
62.2.107.35
62.2.121.84
62.2.121.88
fd00::7eff:4dff:feaa:2528
2001:638:902:1::10
DNS Domain: ~.
  thiemo @ Fujitsu-HO ~ % host -v myworkspaceinet.post.ch   
20-05-18 12:54
  Trying "myworkspaceinet.post.ch"
  ;; connection timed out; no servers could be reached

  thiemo @ Fujitsu-HO ~ :-( % alias pong
20-05-18 12:55
  pong='ping -c3'
  thiemo @ Fujitsu-HO ~ % pong 139.18.25.33 
20-05-18 12:58
  PING 139.18.25.33 (139.18.25.33) 56(84) bytes of data.
  64 bytes from 139.18.25.33: icmp_seq=1 ttl=246 time=39.9 ms
  64 bytes from 139.18.25.33: icmp_seq=2 ttl=246 time=39.0 ms
  64 bytes from 139.18.25.33: icmp_seq=3 ttl=246 time=39.4 ms

  --- 139.18.25.33 ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 39.000/39.431/39.868/0.354 ms

  Kind regards

  Thiemo

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon May 18 13:03:40 2020
  InstallationDate: Installed on 2020-05-15 (3 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 192.168.178.1 dev enp0s25 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000 
   192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.33 
metric 100
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP

[Desktop-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Laptop drops connection to the Internet after reboot, forcing me to
  reset by turning Wi-Fi off and then back on.

Status in linux package in Ubuntu:
  Expired
Status in network-manager package in Ubuntu:
  Expired

Bug description:
  When I was trying to connect to the network after rebooting the
  computer, and I disabled verification before the reboot, the laptop
  connected, but then, even though no other computers had this problem,
  the speed of the wi-fi shut down, and then the connection with the
  router dropped. All this until I turned Airplane Mode on and Wi-Fi on
  my PC for a brief second before disabling airplane mode and reenabling
  Wi-Fi.

  Ubuntu 18.04.4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.4
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Thu Apr  2 18:25:30 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  wifi  
1585866147  Thu 02 Apr 2020 06:22:27 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  0c4f5994-e9fb-3218-9aa5-d46003ebcd5a  ethernet  
1585865851  Thu 02 Apr 2020 06:17:31 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   6fbfa44b-461e-4067-b37a-26f63bc54f88  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CasperVersion: 1.394.3
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  nmcli-con:
   NAMEUUID

[Desktop-packages] [Bug 1870442] Re: Laptop drops connection to the Internet after reboot, forcing me to reset by turning Wi-Fi off and then back on.