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

[kilroy]

Fresh install of Ubuntu 20.04 with a TT BH060 (TaoTronics):

Device E8:AB:FA:*:*:* (public)
Name: TAOTRONICS SoundSurge 60
Alias: TAOTRONICS SoundSurge 60
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: bluetooth:v000Apd

Also, kernel messages (hundreds):
[149342.549626] Bluetooth: hci0: SCO packet for unknown connection handle 0
[149342.549628] Bluetooth: hci0: SCO packet for unknown connection handle 12289

Switching to HSP/HFP just deactivates it completely. Only A2DP works as
expected.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

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

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

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

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

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

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Desktop-packages] [Bug 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled

[Manuel J.]

The update fixed it for me as well. Thanks for the effort to everyone
involved in fixing, reporting, etc.

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

Title:
  Display scale not remembered when X11 Fractional Scaling is enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

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

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

[Desktop-packages] [Bug 1880086] [NEW] [nvidia+xorg] Poor desktop performance while running gtk4 demos like Fishbowl

[Daniel van Vugt]

Public bug reported:

Poor desktop performance while running gtk4 demos like Fishbowl, using
the Nvidia driver (on Xorg)

** Affects: mutter (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: focal groovy nvidia performance

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

Title:
  [nvidia+xorg] Poor desktop performance while running gtk4 demos like
  Fishbowl

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Poor desktop performance while running gtk4 demos like Fishbowl, using
  the Nvidia driver (on Xorg)

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

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

[Desktop-packages] [Bug 1880086] Re: [nvidia+xorg] Poor desktop performance while running gtk4 demos like Fishbowl

[Daniel van Vugt]

Upstream fix:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1263

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

Title:
  [nvidia+xorg] Poor desktop performance while running gtk4 demos like
  Fishbowl

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Poor desktop performance while running gtk4 demos like Fishbowl, using
  the Nvidia driver (on Xorg)

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

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

[Desktop-packages] [Bug 1879876] Re: Screen should not rotate automatically on a laptop

[Che Cheng]

** Bug watch added: gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues #306
   https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/306

** Also affects: iio-sensor-proxy via
   https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/306
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen should not rotate automatically on a laptop

Status in IIO Sensor Proxy:
  Unknown
Status in OEM Priority Project:
  New
Status in iio-sensor-proxy package in Ubuntu:
  New

Bug description:
  There are recently more machines shipped with an accelerometer to
  bring about the automatic rotation feature on pad-like or 2in1
  products. However, manufacturers sometimes share designs between
  platforms; a laptop may mount an accelerometer on its panel. The user
  experience on laptops with a fixed keyboard/touchpad that rotates
  automatically is somehow annoying, and the touchpad motion is
  confusing.

  The SMBIOS specification defines chassis type in section 7.4.1. Softwares can 
determine to rotate automatically or not by checking this value, or at least 
not to rotate on a laptop(0x09) and notebook(0x0A).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-05 (15 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: gdm3 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1879876/+subscriptions

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

[Daniel van Vugt]

Yeah actually I have no idea how:

  Option "SWCursor" "true"

is expected to work with compositors.

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1870956] Re: Desktop Icons Remain Highlighted when Mouse Cursor Leaves Them via Taskbar

[Daniel van Vugt]

** Also affects: gnome-shell-extension-desktop-icons via
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/193
   Importance: Unknown
   Status: Unknown

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

Title:
  Desktop Icons Remain Highlighted when Mouse Cursor Leaves Them via
  Taskbar

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

Bug description:
  Default Gnome desktop, the taskbar touches the desktop icon highlight
  square. If the mouse cursor over the icon leaves the icon by moving
  over the taskbar, the icon remains highlighted.  The highlight remains
  when another icon is highlighted or a window activated.  Multiple
  icons may be left in the highlighted state. The highlight is turned
  off by moving the mouse over the icon and then off the icon onto the
  desktop.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  Note the two libgnome-desktop packages, 3.18 and 3.19
  This installation was started about a week ago, just before the beta release.
  $dpkg -l |grep gnome |grep desk
  ii  gir1.2-gnomedesktop-3.0:amd64  3.36.0-1ubuntu1
amd64Introspection data for GnomeDesktop
  ii  gnome-calculator   1:3.36.0-1ubuntu1  
amd64GNOME desktop calculator
  ii  gnome-control-center   1:3.36.1-1ubuntu3  
amd64utilities to configure the GNOME desktop
  ii  gnome-control-center-faces 1:3.36.1-1ubuntu3  
all  utilities to configure the GNOME desktop - faces images
  ii  gnome-desktop3-data3.36.0-1ubuntu1
all  Common files for GNOME desktop apps
  ii  gnome-menus3.36.0-1ubuntu1
amd64GNOME implementation of the freedesktop menu 
specification
  ii  gnome-online-accounts  3.36.0-1ubuntu1
amd64service to manage online accounts for the GNOME desktop
  ii  gnome-power-manager3.32.0-2   
amd64power management tool for the GNOME desktop
  ii  gnome-shell3.36.0-2ubuntu2
amd64graphical shell for the GNOME desktop
  ii  gnome-shell-extension-desktop-icons19.10.2+git20200223-1  
all  desktop icon support for GNOME Shell
  ii  gnome-todo 3.28.1-5   
amd64minimalistic personal task manager designed to fit 
GNOME desktop
  ii  libgnome-desktop-3-18:amd643.34.2-2ubuntu1
amd64Utility library for loading .desktop files - runtime 
files
  ii  libgnome-desktop-3-19:amd643.36.0-1ubuntu1
amd64Utility library for loading .desktop files - runtime 
files
  ii  libgnome-menu-3-0:amd643.36.0-1ubuntu1
amd64GNOME implementation of the freedesktop menu 
specification
  ii  yaru-theme-gnome-shell 20.04.4
all  Yaru GNOME Shell desktop theme from the Ubuntu 
Community

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 09:41:19 2020
  InstallationDate: Installed on 2020-02-29 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Timo Aaltonen]

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

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

[Aleksander Miera]

Fair point, but question is if it's software cursor from Xserver's
perspective. NVidia driver might be blending the cursor in, while
"emulating HW cursor" on the Xorg's end, right?

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1872276] Re: Gnome shell huge app's icon size in the app folder

[Daniel van Vugt]

Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/2738

but there's also: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/2824

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

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

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

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

Title:
  Gnome shell huge app's icon size in the app folder

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

Bug description:

  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872276/+subscriptions

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Daniel van Vugt]

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/1268
   Importance: Unknown
   Status: Unknown

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Adam Dingle]

OK - reported upstream at

  https://gitlab.gnome.org/GNOME/mutter/issues/1268


** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1268
   https://gitlab.gnome.org/GNOME/mutter/issues/1268

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

[Daniel van Vugt]

I think the other bug must be using SW cursor, because otherwise it's
impossible for it to affect framebuffer contents.

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Daniel van Vugt]

Please report the bug upstream and mention that you are using mutter 3.36.2:
  
  https://gitlab.gnome.org/GNOME/mutter/issues

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

[Aleksander Miera]

A recording would preferably be better, a screenshot might not give the
full picture. Anyway, sure, I shall post it. The case I'm describing is
more extreme, the squares are way bigger and flickering constantly, most
of the time effectively preventing usage of the machine, such messy it
gets.

Plus, is the other user also using SW cursor? In the case described here
it's related purely to that.

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https:/

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Daniel van Vugt]

** Tags added: hybrid nvidia prime

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 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-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Adam Dingle]

By the way this bug, like the previous copy/paste issues, is specific to
X11.  I just logged into Ubuntu 20.04 in a Wayland session and could not
reproduce this bug there, either using Ctrl-C/Ctrl-V or the Copy/Paste
context menu items.

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen ...") from xf86VTEnter() from systemd_logind_vtenter()

[Daniel van Vugt]

Maybe fixed in bug 1879893?

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
  systemd_logind_vtenter()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 14:15:46 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:3102]
  InstallationDate: Installed on 2018-05-26 (81 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 7 
-core
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic 
root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   ()
   ()
   xf86VTEnter ()
   ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.93-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1879159] Re: Boot Problem

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Boot Problem

Status in xorg package in Ubuntu:
  New

Bug description:
  It shows graphics problem during booting and unable to operate mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May 17 13:19:12 2020
  DistUpgraded: 2020-03-29 23:06:17,899 DEBUG /openCache(), new cache size 56855
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0555]
  InstallationDate: Installed on 2020-03-24 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic 
root=UUID=2e048bbe-fc79-442e-ae8d-aac97ebb2938 ro quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2020-03-29 (48 days ago)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 17 13:15:51 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Alex Murray]

One more thing - I expect your phone has USB Tethering enabled - and so
presents itself as an rndis USB/ethernet device - and then network
manager uses this as a preferred interface to route traffic through
rather than the wireless interface.

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1787337] Re: Xorg() crashed with SIGBUS in OsSigHandler (signo=7) from xf86VTEnter() from systemd_logind_vtenter() from message_filter() from dbus_connection_dispatch()

[Daniel van Vugt]

Maybe fixed in bug 1879893?

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

Title:
  Xorg() crashed with SIGBUS in OsSigHandler (signo=7) from
  xf86VTEnter() from systemd_logind_vtenter() from message_filter() from
  dbus_connection_dispatch()

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1787338] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from xf86VTSwitch()

[Daniel van Vugt]

Maybe fixed in bug 1879893?

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
  xf86VTSwitch()

Status in xorg-server package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Alex Murray]

This doesn't seem like a security issue to me - I believe this is the
default behaviour when using network manager for tethering - it will
route traffic via the tethered device. I am reassigning this against
network-manager which is likely doing the route setup.

** Information type changed from Private Security to Public

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

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from WakeupHandler()

[Daniel van Vugt]

Maybe fixed in bug 1879893?

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
  WakeupHandler()

Status in xorg-server package in Ubuntu:
  Confirmed

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

  The error is reported on boot up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:

  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1866217] Re: Mouse pointer vanished on Wayland (okay on X)

[Launchpad Bug Tracker]

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

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

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

Title:
  Mouse pointer vanished on Wayland (okay on X)

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Running 20.04 with all the repos enabled (including focal-proposed)

  A recent update (apt-get dist-upgrade) made the mouse point disappear.

  
  The mouse worked on a text console... and lsusb etc showed the presence of 
the mouse.
  In Wayland, pressing control key showed the pointer location.

  
  Resolution
  Edited /etc/gdm3/custom.conf and uncommented "WaylandEnable=false"
  Rebooted a mouse pointer is now back.

  Wayland device driver problem?

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

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

[Desktop-packages] [Bug 1741114] Re: [Launcher API] Progress bar / count stops responding after small progress changes

[Launchpad Bug Tracker]

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

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

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

Title:
  [Launcher API] Progress bar / count stops responding after small
  progress changes

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

Bug description:
  I've made an extension for Firefox that makes use of Unity Laucher API
  and that way integrates with Ubuntu Dock. The interesting part for
  this extension is a python3 script. I'm attaching a simple one here to
  demonstrate the issue.

  The attached script makes a change to "progress" every second - adds
  0.01. Progress bar and counter is created first and a few progress
  changes are reflected but after a short time the visual updating
  stops. But as you can see from generated launcher_api_test.log the
  updating should continue.

  If you play with line 33 (progress_addition) and set it to a bigger
  number (e.g. 0.1) it works fine till the end of the test.

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

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

[Desktop-packages] [Bug 1868405] Re: Untranslatable "Monitor of ..."

[Launchpad Bug Tracker]

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

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

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

Title:
  Untranslatable "Monitor of ..."

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  It is impossible to translate string "Monitor of %s". Please add
  gettext call here and export the string into the .pot template.

  
https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373

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

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

[Desktop-packages] [Bug 1879234] Re: Xorg freeze

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when i was my computer on and start blinking middle of screen please
  solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  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: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

[Adam Dingle]

Davide, that's a very interesting discovery that every other copy/paste
fails when you use the menu caommands.  I see that on my machine too.
Hopefully that will make it easier to debug the problem, since it is a
much more direct way to reproduce the problematic behavior.

(On the other hand, there is no guarantee that this copy/paste failure
with menu commands is actually the same bug as the occasional copy/paste
failures when you use keyboard shortcuts, since the observed behavior is
pretty different.)

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1879211] [NEW] Charging my cellphone through usb breaks internet connection.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I don't know what package is responsible for this. I entered iptables
because the ip command was not recognized as a package.

I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
#ip route
default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 

Here it is after I plug my cellphone
#ip route
default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 

So my computer is trying to access all ips using my cellphone as a
router, which of course fails.

the command "sudo ip route del default" followed by "sudo ip route add
default via 192.168.0.1 dev wlp2s0" restores my connection.

Thank you for your attention. I'm available to answer any questions and
fix this bug. Reporting this bug was already effort diverted from my
other tasks, so let's make this count no matter how deep it cuts.

P.S: I went ahead and marked this bug as a security vulnerability
because I can think of ways this can be exploited, especially if the
cellphone can trigger the bug and route traffic so that the user doesn't
suspect it. If you feel the security impact is small and that there are
other more important security issues, feel free to unmark it and we can
deal with it's usability impact, which is probably more impactful.

Regards,
Tomás.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: iptables 1.6.1-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 17 22:59:02 2020
InstallationDate: Installed on 2019-02-08 (464 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: iptables
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ip
-- 
Charging my cellphone through usb breaks internet connection.
https://bugs.launchpad.net/bugs/1879211
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Daniel van Vugt]

xorg-server (2:1.20.8-2ubuntu3) groovy; urgency=medium

  * modesetting-do-not-stop-on-entervt.diff: Don't crash if connectors
go missing. (LP: #1879893)

 -- Timo Aaltonen   Thu, 21 May 2020 11:22:15 +0300

** Changed in: xorg-server (Ubuntu Groovy)
   Status: Confirmed => Fix Committed

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 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-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Daniel van Vugt]

Also tracking in
https://errors.ubuntu.com/problem/fcbe67a6b9fb16b72a224659bed6947a9b603651
(bug 1880068) ... I think?

** Also affects: xorg-server (Ubuntu Groovy)
   Importance: Undecided
   Status: Confirmed

** Also affects: xorg-server-hwe-18.04 (Ubuntu Groovy)
   Importance: Undecided
   Status: Invalid

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 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-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Launchpad Bug Tracker]

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

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

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 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-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock

[Daniel van Vugt]

Can we say which of bug 1421808 / bug 1787332 / bug 1787338 this might
be?

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

Title:
  GNOME crashed when resuming from sleep in NVIDIA performance mode with
  disconnecting dell-wd19tb-dock

Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Fix Committed
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid
Status in xorg-server source package in Groovy:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Groovy:
  Invalid

Bug description:
  1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, 
xserver-xorg-hwe-18.04 and nvidia-driver-440.
  2. Select the performance mode in NVIDIA settings and reboot the system.
  3. Connect dell-wd19tb-dock to the system.
  4. Connect external HDMI monitor to dell-wd19tb-dock.
  5. Open a terminal, some GUI applications and then execute `systemctl 
suspend` in the terminal.
  6. Disconnect dell-wd19tb-dock after the system fell asleep.
  7. Resume the system and login the GNOME desktop environment.

  Expected result:
  The terminal and other GUI applications will still exist.

  Actual result:
  All opened GUI applications in GNOME are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1052-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 03:31:41 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-gilly+X33
  InstallationDate: Installed on 2020-05-06 (14 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg-server-hwe-18.04
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

[Prashant Deva]

seeing same issue with gtx 1080 after upgrading to ubuntu 20.04. worked
fine in 19.10

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

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

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

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

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1878327] Re: [Dell Inspiron 1525] Pulse audio update made internal speakers as Dummy Output

[Rajasekharan N]

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

To anyone landing on this page:

Current version is pulseaudio 1:13.99.1-1ubuntu3.2.

There is a fix/patch in this PPA that you can use it for now until the
next update/release (Version: pulseaudio 1:13.99.1-1ubuntu3.2lp1869819):

https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

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

Title:
  [Dell Inspiron 1525] Pulse audio update made internal speakers as
  Dummy Output

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I had already reported bug #1876238 where internal speakers are not
  detected but shown as Dummy Output after upgrading Ubuntu from 19.10
  to 20.04 LTS Focal.

  It was solved by this patch:
  https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819

  The current PulseAudio update today reversed that again. Internal
  speakers are not being detected and are shown as Dummy Output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2016 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 13 09:02:53 2020
  InstallationDate: Installed on 2016-12-20 (1239 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Rajasekharan N]

@Kai-Heng Feng (kaihengfeng)

Downloaded the patch and updated the PulseAudio.

The internal speakers, both the headphone jacks and the internal mic,
all are working fine now. (Didn't test the external mic jack.)

Thanks a gazillion.

I can return the borrowed laptop to my neighbor and start working with
mine.

You are a god-sent angel to save me from trouble. May God bless you.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

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

[Daniel van Vugt]

Looks like there's an assertion failure in Xorg (in XorgLogOld.txt) but
that stack trace is almost certainly wrong. Please follow the above
instructions.

** Package changed: xorg (Ubuntu) => xorg-server (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/1879977

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.90
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_

[Daniel van Vugt]

** Description changed:

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from
  _systemd_session_is_graphical() from _find_graphical_systemd_session()

Status in accountsservice package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8
  https://errors.ubuntu.com/problem/bd6ce0ebb5afe5054592e605660dff1d41db4f34

  ---

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

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

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

[Desktop-packages] [Bug 1879665] Re: Xorg freeze - Cursor flicker

[Daniel van Vugt]

Yeah the extensions panel in gnome-tweaks is broken (bug 1718850).

Please try using 'gnome-shell-extension-prefs' instead. Now disable all
non-Ubuntu extensions, and reboot. Does the problem still happen?

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

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

Title:
  Xorg freeze - Cursor flicker

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When searching any term in my file explorer the cursor blinks rapidly
  and has an old windows 98 shadow cursor when moving it before it
  freezes and no keyboard functions work and the system locks up

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  Files - From Sofware Center
  Version : 1:3.36.2-0ubuntu1

  nautilus:
Installed: 1:3.36.2-0ubuntu1
Candidate: 1:3.36.2-0ubuntu1
Version table:
   *** 1:3.36.2-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.36.1.1-1ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages


  Expected outcome, regular search function like previous 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 23:37:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
   virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD3H-BK
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=f1ff3586-408b-4da3-8047-ff8b674432b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD3H-BK-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd10/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-BK-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z97X-UD3H-BK
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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
  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/gnome-shell/+bug/1879665/+subscriptions

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

[Desktop-packages] [Bug 1879665] [NEW] Xorg freeze - Cursor flicker

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When searching any term in my file explorer the cursor blinks rapidly
and has an old windows 98 shadow cursor when moving it before it freezes
and no keyboard functions work and the system locks up

Description:Ubuntu 20.04 LTS
Release:20.04


Files - From Sofware Center
Version : 1:3.36.2-0ubuntu1

nautilus:
  Installed: 1:3.36.2-0ubuntu1
  Candidate: 1:3.36.2-0ubuntu1
  Version table:
 *** 1:3.36.2-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1.1-1ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages


Expected outcome, regular search function like previous 18.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 19 23:37:36 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
 virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD3H-BK
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=f1ff3586-408b-4da3-8047-ff8b674432b6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD3H-BK-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd10/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H-BK:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-BK-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z97X-UD3H-BK
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug focal freeze nouveau ubuntu
-- 
Xorg freeze - Cursor flicker
https://bugs.launchpad.net/bugs/1879665
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1879203] Re: combination Super + Space do not switch to another language

[Daniel van Vugt]

It's in official updates now so run:

  sudo apt update
  sudo apt full-upgrade

and reboot.

Now make sure you're using the new version 3.36.2 by running:

  dpkg -s libmutter-6-0 | grep Version

Does this bug still happen after that?

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

Title:
  combination Super + Space do not switch to another language

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding
  to the switching command.

  gnome-shell (3.36.1-5ubuntu2)

  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Daniel van Vugt]

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

If that was true then bug 1878194 would be a duplicate of this one
because this one is older.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1876978] Re: gnome-screenshot clipboard image incomplete

[Daniel van Vugt]

Screenshotting for gnome-shell is implemented by libmutter

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

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

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

Title:
  gnome-screenshot clipboard image incomplete

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When running `gnome-screenshot` via terminal (or bash script) with
  both the `--clipboard` and `--file ...` options the screenshot copied
  to the clipboard is incomplete/corrupted while the screenshot saved to
  disk is fine. I'm able to reproduce this reliably via the following
  command:

  gnome-screenshot --clipboard --file "${HOME}/Pictures/Screenshot
  $(date +'%F %T').png" --window

  When running this command I expect to have one copy of the screenshot
  saved to disk and a (complete) copy of the screenshot copied to the
  clipboard automatically.

  Additional information:

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

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

  I've attached the incomplete/corrupted screenshot to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-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: ubuntu:GNOME
  Date: Tue May  5 13:00:43 2020
  InstallationDate: Installed on 2020-04-23 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870512] Re: forced software cursor with PageFlip enabled triggers artifacts on screen

[Daniel van Vugt]

Can you attach a photo/screenshot of the problem? Is it similar to bug
1874856?

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

Title:
  forced software cursor with PageFlip enabled triggers artifacts on
  screen

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The following Xorg configuration triggers faulty behaviour, like
  blinking cursor, corrupt graphics around it etc.:

1 Section "Device"
2   Identifier "graphicsdriver"
3   Driver  "modesetting"
4   Option "SWCursor" "true"
5   #Option "PageFlip" "off"
6   #Option "AccelMethod" "none"
7 EndSection

  Either switching SWCursor to false or uncommenting line 5 or 6 makes the 
issue disappear.
  Disabling accelleration is naturally the least recommended way of resolving 
the issue.
  As far as I've analyzed Xorg's source code shipped with 20.04, I can see that 
https://gitlab.freedesktop.org/xorg/xserver/commit/0aaac8d783e78c040a70a55ba8d67809abd7e625
  which should probably automatically handle the issue (haven't tried to build 
with those changes yet) is not included. If it ever should be in (as it looks 
like a workaround only), reamains an open question.

  I am not entirely sure which package to attach this bug to, Xorg seems
  the most viable at the moment. My reason for the uncertainty
  originates from the fact, that I have also tested other distros, e.g.
  SuSE tumbleweed (build from this week, exact versions to be added if
  needed) with KDE plasma, which happens to reproduce the bug only with
  OpenGL set as compositor's backend; XRender operates perfectly fine
  there; hence it is a bit unclear to me which compoment is the "owning
  interface" and which one is actually buggy, be it Xorg, mesa or
  compositor; please reassign the bug accordingly if needed.

  My plan for the nearest future is to verify whether the aforementioned
  change actually circumvents the issue. If anything else should be
  looked at to fix the problem, I am open for suggestions.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 09:41:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2020-03-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=1b7a03b4-95ff-4d1b-9897-848a0dc6f8b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1880031] Re: Thumbnail is stretched if its aspect ratio is less than that of the container

[Daniel van Vugt]

Please include a screenshot/photo of the problem and report it to the
developers at:

  https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues

** Tags added: focal

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

Title:
  Thumbnail is stretched if its aspect ratio is less than that of the
  container

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

Bug description:
  This was discovered when investigating fix for bug #1868529.

  Aspect ratio is still not correct for images that are more narrow than
  the container. To reproduce, create an image that has aspect ratio,
  e.g., ~0.5 (e.g. width = 250 and height = 500).

  Line in fileItem.js where we calculate icon width does not count the
  margins (zero is used instead of actual margins):

  let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0);

  Here is how the margins are being calculated in desktopGrid.js:

  this._extra_width = themeNode.get_margin(St.Side.LEFT) +
   themeNode.get_margin(St.Side.RIGHT) +
   themeNode.get_border_width(St.Side.LEFT) +
   themeNode.get_border_width(St.Side.RIGHT) +
   themeNode.get_horizontal_padding();
  this._extra_height = themeNode.get_margin(St.Side.TOP) +
   themeNode.get_margin(St.Side.BOTTOM) +
   themeNode.get_border_width(St.Side.TOP) +
   themeNode.get_border_width(St.Side.BOTTOM) +
   themeNode.get_vertical_padding();

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

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

[Desktop-packages] [Bug 1311568] Re: [desktoptouch] Cannot scroll content through touch

[gur111]

Bug still there. More than 6 years later

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

Title:
  [desktoptouch] Cannot scroll content through touch

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  It is not possible to scroll the content gnome-terminal with touch
  gestures. I tried one and two fingers scroll and the scrollbar doesn't
  work with touch either.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 11:44:04 2014
  InstallationDate: Installed on 2014-04-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878408] Re: Gnome 3.36 Ubuntu 20.04 workspace changing using a combo of 4 finger gesture and hotcorner kinda bugged

[Daniel van Vugt]

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

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2784 => 
gitlab.gnome.org/GNOME/gnome-shell/-/issues #2259

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

Title:
  Gnome 3.36 Ubuntu 20.04 workspace changing using a combo of 4 finger
  gesture and hotcorner kinda bugged

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

Bug description:
  I am using ubuntu 20.04.

  Laptop : 
  Lenovo Legion y520
  nvidia gtx1060 maxq
  intel i5

  I am not using my nvidia card with ubuntu.

  I have tested this on ubuntu-gnome and vanilla gnome without
  extensions as well. So when I am in overview and change workspace
  using 4 finger gesture and mid animation or just after animation ends
  I close the over view either the workspace change doesnt happen or I
  can see a part of the previous workspace for a second or two. I have
  include a video here. It doesnt clearly shows the bug I have stated. I
  can upload another one if anyone wants

  
https://drive.google.com/file/d/1GllnObuW6qjOtVzubH_K_WyCS6Z99U-S/view?usp=sharing

  This my first bug report here so if there was any shortcoming in the report 
plz tell
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-11-09 (187 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal wayland-session
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-08 (5 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04

[Daniel van Vugt]

Can someone please also open a new upstream bug?

  https://gitlab.gnome.org/GNOME/mutter/issues

** Tags added: focal

** Summary changed:

- copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04
+ copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

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

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Hui Wang]

We have a private bug which is similar to it. #1875597

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Hui Wang]

We have a private bug which is similar to it.

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1

[Hui Wang]

snd_use_case_parse_ctl_elem_id() is defined in the latest libasound2
(>=1.2.1), maybe reinstall the libaousnd2 and pulseaudio could help.

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

Title:
  ALSA sees my intel soundcards but pulseaudio does not.  Error is :
  "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-
  card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined
  symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  ALSA sees my intel soundcards but pulseaudio does not.

  'pavucontrol' sees only a "Dummy" device.

  #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open
  module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so:
  /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol:
  snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

  Making pulseaudio from source fixes the problem/

  (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29
  14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 20 12:48:07 2020
  InstallationDate: Installed on 2015-04-29 (1848 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.00L21
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFC2-2
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFC2-2
  dmi.product.name: CF-C2CQAZXCM
  dmi.product.sku: CF-C2CQAZXCM
  dmi.product.version: 002
  dmi.sys.vendor: Panasonic Corporation
  mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45

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

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

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

[Sly Gryphon]

Not working for me with Chromium 81, snap version, on Ubuntu 20.04.
(Testing with music.youtube.com and twitter.com)

Icon is created on the desktop, but:

* Not executable (need to mark it)
* Just opens empty browser page (app does not run); work around from 
@coeur-noir above, to replace the version-specific path in Exec with 
/snap/bin/chromium, gets it working
* Icon is not displayed (just red box with no entry circle)

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

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

Status in chromium-browser package in Ubuntu:
  Triaged

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

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

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

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

[Desktop-packages] [Bug 1868529] Re: Stretched image previews on desktop

[riu]

See bug #1880031.

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

Title:
  Stretched image previews on desktop

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

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. The regular previews in Nautilus have normal sizes.
  See attached pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1880031] Re: Thumbnail is stretched if its aspect ratio is less than that of the container

[riu]

** Description changed:

  This was discovered when investigating fix for bug #1868529.
  
  Aspect ratio is still not correct for images that are more narrow than
  the container. To reproduce, create an image that has aspect ratio,
  e.g., ~0.5 (e.g. width = 250 and height = 500).
  
  Line in fileItem.js where we calculate icon width does not count the
  margins (zero is used instead of actual margins):
  
- let iconWidth = Prefs.getDesiredWidth(scaleFactor, 0);
+ let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0);
  
  Here is how the margins are being calculated in desktopGrid.js:
  
  this._extra_width = themeNode.get_margin(St.Side.LEFT) +
   themeNode.get_margin(St.Side.RIGHT) +
   themeNode.get_border_width(St.Side.LEFT) +
   themeNode.get_border_width(St.Side.RIGHT) +
   themeNode.get_horizontal_padding();
  this._extra_height = themeNode.get_margin(St.Side.TOP) +
   themeNode.get_margin(St.Side.BOTTOM) +
   themeNode.get_border_width(St.Side.TOP) +
   themeNode.get_border_width(St.Side.BOTTOM) +
   themeNode.get_vertical_padding();

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

Title:
  Thumbnail is stretched if its aspect ratio is less than that of the
  container

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

Bug description:
  This was discovered when investigating fix for bug #1868529.

  Aspect ratio is still not correct for images that are more narrow than
  the container. To reproduce, create an image that has aspect ratio,
  e.g., ~0.5 (e.g. width = 250 and height = 500).

  Line in fileItem.js where we calculate icon width does not count the
  margins (zero is used instead of actual margins):

  let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0);

  Here is how the margins are being calculated in desktopGrid.js:

  this._extra_width = themeNode.get_margin(St.Side.LEFT) +
   themeNode.get_margin(St.Side.RIGHT) +
   themeNode.get_border_width(St.Side.LEFT) +
   themeNode.get_border_width(St.Side.RIGHT) +
   themeNode.get_horizontal_padding();
  this._extra_height = themeNode.get_margin(St.Side.TOP) +
   themeNode.get_margin(St.Side.BOTTOM) +
   themeNode.get_border_width(St.Side.TOP) +
   themeNode.get_border_width(St.Side.BOTTOM) +
   themeNode.get_vertical_padding();

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

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

[Desktop-packages] [Bug 1880031] [NEW] Thumbnail is stretched if its aspect ratio is less than that of the container

[riu]

Public bug reported:

This was discovered when investigating fix for bug #1868529.

Aspect ratio is still not correct for images that are more narrow than
the container. To reproduce, create an image that has aspect ratio,
e.g., ~0.5 (e.g. width = 250 and height = 500).

Line in fileItem.js where we calculate icon width does not count the
margins (zero is used instead of actual margins):

let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0);

Here is how the margins are being calculated in desktopGrid.js:

this._extra_width = themeNode.get_margin(St.Side.LEFT) +
 themeNode.get_margin(St.Side.RIGHT) +
 themeNode.get_border_width(St.Side.LEFT) +
 themeNode.get_border_width(St.Side.RIGHT) +
 themeNode.get_horizontal_padding();
this._extra_height = themeNode.get_margin(St.Side.TOP) +
 themeNode.get_margin(St.Side.BOTTOM) +
 themeNode.get_border_width(St.Side.TOP) +
 themeNode.get_border_width(St.Side.BOTTOM) +
 themeNode.get_vertical_padding();

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


** Tags: 20.04

** Description changed:

- This was discovered when investigating fox for bug 1868529.
+ This was discovered when investigating fix for bug #1868529.
  
  Aspect ratio is still not correct for images that are more narrow than
  the container. To reproduce, create an image that has aspect ratio,
  e.g., ~0.5 (e.g. width = 250 and height = 500).
  
  Line in fileItem.js where we calculate icon width does not count the
  margins (zero is used instead of actual margins):
  
  let iconWidth = Prefs.getDesiredWidth(scaleFactor, 0);
  
  Here is how the margins are being calculated in desktopGrid.js:
  
- this._extra_width = themeNode.get_margin(St.Side.LEFT) +
-  themeNode.get_margin(St.Side.RIGHT) +
-  themeNode.get_border_width(St.Side.LEFT) +
-  themeNode.get_border_width(St.Side.RIGHT) +
-  themeNode.get_horizontal_padding();
- this._extra_height = themeNode.get_margin(St.Side.TOP) +
-  themeNode.get_margin(St.Side.BOTTOM) +
-  themeNode.get_border_width(St.Side.TOP) +
-  themeNode.get_border_width(St.Side.BOTTOM) +
-  themeNode.get_vertical_padding();
+ this._extra_width = themeNode.get_margin(St.Side.LEFT) +
+  themeNode.get_margin(St.Side.RIGHT) +
+  themeNode.get_border_width(St.Side.LEFT) +
+  themeNode.get_border_width(St.Side.RIGHT) +
+  themeNode.get_horizontal_padding();
+ this._extra_height = themeNode.get_margin(St.Side.TOP) +
+  themeNode.get_margin(St.Side.BOTTOM) +
+  themeNode.get_border_width(St.Side.TOP) +
+  themeNode.get_border_width(St.Side.BOTTOM) +
+  themeNode.get_vertical_padding();

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

Title:
  Thumbnail is stretched if its aspect ratio is less than that of the
  container

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

Bug description:
  This was discovered when investigating fix for bug #1868529.

  Aspect ratio is still not correct for images that are more narrow than
  the container. To reproduce, create an image that has aspect ratio,
  e.g., ~0.5 (e.g. width = 250 and height = 500).

  Line in fileItem.js where we calculate icon width does not count the
  margins (zero is used instead of actual margins):

  let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0);

  Here is how the margins are being calculated in desktopGrid.js:

  this._extra_width = themeNode.get_margin(St.Side.LEFT) +
   themeNode.get_margin(St.Side.RIGHT) +
   themeNode.get_border_width(St.Side.LEFT) +
   themeNode.get_border_width(St.Side.RIGHT) +
   themeNode.get_horizontal_padding();
  this._extra_height = themeNode.get_margin(St.Side.TOP) +
   themeNode.get_margin(St.Side.BOTTOM) +
   themeNode.get_border_width(St.Side.TOP) +
   themeNode.get_border_width(St.Side.BOTTOM) +
   themeNode.get_vertical_padding();

To manage notifications about this bug go to:
https://bugs.launchpad.net

[Desktop-packages] [Bug 1868529] Re: Stretched image previews on desktop

[riu]

It is much better with the fix. We don't count margins, so the aspect
ratio is still not valid for narrow images.

Line in fileItem.js

let width = Prefs.getDesiredWidth(scaleFactor, 0)

was also erroneous, because margins are not 0 (at least, with default
theme).

Here is how the margins are being calculated:

this._extra_width =  themeNode.get_margin(St.Side.LEFT) +
 themeNode.get_margin(St.Side.RIGHT) +
 themeNode.get_border_width(St.Side.LEFT) +
 themeNode.get_border_width(St.Side.RIGHT) +
 themeNode.get_horizontal_padding();
this._extra_height = themeNode.get_margin(St.Side.TOP) +
 themeNode.get_margin(St.Side.BOTTOM) +
 themeNode.get_border_width(St.Side.TOP) +
 themeNode.get_border_width(St.Side.BOTTOM) +
 themeNode.get_vertical_padding();

(they are used in Prefs.getDesiredWidth and Prefs.getDesiredHeight
functions)

Aspect ratio is still not correct for narrow images. To reproduce,
create an image that has aspect ratio ~0.5 (e.g. width = 250 and height
= 500).

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

Title:
  Stretched image previews on desktop

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

Bug description:
  After upgrade to 20.04 desktop previews of pictures and documents
  became stretched. The regular previews in Nautilus have normal sizes.
  See attached pic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 23 11:44:13 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working

[Sebastien Bacher]

Thanks, closing the bug then, it was probably due some leftover
configuration and we are not likely to figure it out now that it has
been resolved

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

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

Title:
  Ubuntu 20.04 Focal Fossa desktop launchers not working

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

Bug description:
  Using the procedure here = 
  
https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux
 

  AND OTHERWISE

  I have successfully created launchable desktop app shortcuts.  But
  they stop working: (1) no launch; (2) no right click context to make
  launchable; and (3) no app icon.  They can even remain in ~/Desktop
  but disappear from the desktop view.  A logout kills them. Creating
  another new launcher is successful and peculiarly triggers the
  temporary reactivation of all the others.  But euphoria soon dies as
  they all revert to inertia later.

  My work around at present is to install PCManFM 1.3.1. Navigating to
  ~/Desktop on PCManFM, my Nautilus created launchers are all visible,
  launchable and have the usual colourful app icon features. But they
  remain inert in Nautilus.

  My Gnome version is: 3.36.1

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

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

[Desktop-packages] [Bug 1871377] Re: URW Nimbus font issue

[Sebastien Bacher]

Thanks you Till!

** Changed in: fonts-urw-base35 (Ubuntu)
   Importance: Undecided => Low

** Changed in: fonts-urw-base35 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  URW Nimbus font issue

Status in fonts-urw-base35 package in Ubuntu:
  Triaged

Bug description:
  It seems that cyrillic small letter `te` (afii10084) has wrong glyph in 
italic and bold Italic style: width is too big.
  This issue presented in OpenType and Type1 URW Nimbus Sans fonts distribution.

  I suggest to replace with the glyph of greek small `tau` letter.

  Attaching here the screenshots of some example words contain small
  letter `te` with original (wide) and replaced glyph.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions

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

[Desktop-packages] [Bug 1879287] Re: System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system

[Sebastien Bacher]

** Package changed: nvidia-prime (Ubuntu) => linux (Ubuntu)

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

Title:
  System sometimes starts with a black screen with Nvidia PRIME setup on
  Ryzen+Nvidia system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Desktop-packages] [Bug 1879850] Re: kpsepath missing

[Sebastien Bacher]

Thank you for your bug report, it has been fixed in the most recent version
https://launchpad.net/ubuntu/+source/texlive-base/2020.20200417-1
https://github.com/debian-tex/texlive-nonbin/commit/90a4c3e4

** Changed in: texlive-base (Ubuntu)
   Importance: Undecided => Low

** Changed in: texlive-base (Ubuntu)
   Status: New => Fix Released

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

Title:
  kpsepath missing

Status in texlive-base package in Ubuntu:
  Fix Released

Bug description:
  The /usr/bin/kpsepath executable is effectively missing: it's a
  symlink to a file that's only included in another package, which
  texlive-base doesn (and probably shouldn't) depend on:

  me@host:~$ dpkg -s texlive-base | grep Version
  Version: 2019.20200218-1
  me@host:~$ ls -l /usr/bin/kpsepath 
  lrwxrwxrwx 1 root root 8 Feb 17 14:37 /usr/bin/kpsepath -> kpsetool
  me@host:~$ kpsetool

  Command 'kpsetool' not found, but can be installed with:

  sudo apt install texlive-extra-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1879850/+subscriptions

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

[Desktop-packages] [Bug 1879905] Re: Can no longer connect to Ubuntu WPA hotspot after upgrade to 20.04

[Sebastien Bacher]

Thanks

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/450
   Importance: Unknown
   Status: Unknown

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

Title:
  Can no longer connect to Ubuntu WPA hotspot  after upgrade to 20.04

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  I upgraded my Ubuntu client to 20.04 and could continue to connect to
  my WPA Hotspot running on an Ubuntu server. Upon update of the server
  to 20.04 I could no longer connect with any of my various client OSs.

  After using the updated network-manager from
  https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/1870359, I can now connect to the hotspot from all of my
  machines running many flavors of OS (Windows, MacOS, Android, Ubuntu
  19.10), but I cannot connect from my machine running Ubuntu 20.04.

  If I turn off the encryption on the hotspot or turn on WEP encryption
  (using nm-connection-editor), then I can connect.

  Seeing that my client running 19.10 can connect, I'm not sure if this
  is a problem specif to my particular laptop running 20.04, or if it is
  rather a problem that any client updating to 20.04 will have. I will
  update my other 19.10 machine, that is currently working with the WPA
  hotspot, to help differentiate between these two possibilities.

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 10:51:00 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   #dns-nameservers 8.8.8.8 8.8.4.4
  IpRoute:
   default via 192.168.0.1 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
   192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.17 metric 600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-10-31T09:47:24.831648
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1880000] Re: impossible de monter le partage windows

[Sebastien Bacher]

could be similar to bug #1879776 , could you read the comments on the
other bug and provide the informations requested there?

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

Title:
  impossible de monter le partage windows

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Oups ! Quelque chose de mal s'est passé.

  Message d'erreur non géré : impossible de monter le partage Windows :
  Le logiciel a provoqué l'abandon de la connexion

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  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: Thu May 21 19:22:46 2020
  InstallationDate: Installed on 2020-04-25 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-05-09 (12 days ago)
  usr_lib_nautilus:

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

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

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

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.90
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 PC MATE (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1879982] Re: No grid lines and time indication in "High contrast" mode

[Sebastien Bacher]

Thank you for your bug report, indeed that's an issue

Could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-
calendar/issues ?

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

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

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

Title:
  No grid lines and time indication in "High contrast" mode

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  this is my first bug report, I guess, so it might not be perfect -
  excuses.

  I love gnome-calendar as well as I love the very reduced look of gnome in 
"high contrast"-mode (→ Universal Access → High Contrast), which renders the 
icons in the dock as white (and minimalistic) as they are in the top panel. 
  But in this mode, I don't see neither grid lines nor time and date 
indications in gnome calendar - the only thing I am able to see are scheduled 
meetings. This renders gnome calendar fairly unusable, when "High Contrast" is 
switched on (→ screenshot).

  Even in high contrast mode, I would expect to see
  - indications of date and day 
  - some kind of grid
  - time indications on the left

  Thank you for the great and beautiful work,

  Michael

  * * *
  Ubuntu 20.04 (freshly updated from 19.10)
  Gnome calendar: 3.36.1

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

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

[Desktop-packages] [Bug 1880000] Re: impossible de monter le partage windows

[Sebastien Bacher]

Thank you for taking the time to report this bug and help make Ubuntu
better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read 'How to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

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

Title:
  impossible de monter le partage windows

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Oups ! Quelque chose de mal s'est passé.

  Message d'erreur non géré : impossible de monter le partage Windows :
  Le logiciel a provoqué l'abandon de la connexion

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  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: Thu May 21 19:22:46 2020
  InstallationDate: Installed on 2020-04-25 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-05-09 (12 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1879776] Re: ubuntu 20 error mounting smb drive

[Sebastien Bacher]

The directory issue sounds like bug #1872476 , could you try if the
update listed there helps?

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

Title:
  ubuntu 20 error mounting smb drive

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  nautilus->other locations>windows network lists the shared disk I want
  to access. When I click on the name I get an errorbox: Unable to
  access location. Failed to mount windows share: Software caused
  connection abort.

  nautilus->other locations>Connect to server: smb://192.168.nnn.nnn
  gives the same errorbox.

  The shared disk is attached to my FritzBox router/modem.
  This works without problems in ubuntu 18 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 21:04:29 2020
  InstallationDate: Installed on 2020-04-20 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1879776/+subscriptions

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

[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer

[Stefano Dall'Agata]

You can remove the print queue (cancel the job) and then disconnect and 
reconnect the printer.
A new print queue is not automatically recreated.

~$ lpstat -v
dispositivo per DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
dispositivo per HP_DeskJet_3630_series: 
dnssd://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f439099b20bb

~$ driverless
ipp://DeskJet%203630%20series%20%5BCN8AM7H3230658%5D._ipp._tcp.local/
ipp://HP%20DeskJet%203630%20series%20%5B9B20BB%5D._ipp._tcp.local/

~$ ps auxwww | grep ippusbxd
root   72414  0.0  0.0 565272  5712 ?Sl   22:10   0:00 
/usr/sbin/ippusbxd --bus-device 001:009 --from-port 6 --logging
stefano72551  0.0  0.0  19756   760 pts/0S+   22:13   0:00 grep 
--color=auto ippusbxd


** Attachment added: "ippusbxd  appears in red"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5375328/+files/hplip%20cups.png

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  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: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

[Pablo San Martín]

Thanks! This fixed it for me! Glad to be able to use Clipboard Indicator
and LibreOffice at the same time again"

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

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

Status in LibreOffice:
  Won't Fix
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released
Status in mutter source package in Groovy:
  Fix Released

Bug description:
  [ Impact ]

  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  [ Test case ]

  1. Use use libreoffice writer/calc
  2. Copy text around
  3. Paste it and ensure it always work

  [ Regression potential ]

  Copy/paste won't work as expected, for non-text types

  -

  
  I use LibreOffice Writer a lot, and I now see this problem very often, i.e. 
many times every day.

  There is some discussion of the problem here:

     https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

     https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04

[Tim Passingham]

Oh dear.  Davide, you are right.  I habitually use keyboard control keys
for cut, copy and paste, and had to try quite hard to get the problem.

Using the context menu (within one writer document) it fails for almost
every other try.

Using the main menu it rarely fails, but it did occasionally.

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

Title:
  copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel

[Francis Ginther]

Not a kernel issue, moving to invalid for 'linux'.

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

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

Title:
  Focal uses the exfat fuse filesystem even though there is support in
  the kernel

Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  When a storage device formatted with exfat is automatically mounted on
  a system it is mounted with a fuse filesystem instead of a native,
  kernel filesystem. The kernel now has support for exfat.

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

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

[Desktop-packages] [Bug 1879741] Re: Unable to read system logs

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-logs - 3.36.0-2

---
gnome-logs (3.36.0-2) unstable; urgency=medium

  * debian/patches/git_log_permissions.patch:
- Improve the check for reading system journal, fixes the misleading
  warning displayed as a banner (lp: #1879741)

 -- Sebastien Bacher   Thu, 21 May 2020 15:26:10
+0200

** Changed in: gnome-logs (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to read system logs

Status in gnome-logs package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  A warning 'Unable to read system logs' is always displayed even when the logs 
are opened without issue

  * Test Case
  start gnome-logs, check that there is no warning displayed and that the log 
are available

  * Regression potential
  The change is in the code checking the journal files so check that if the log 
are correctly found and opened, they shouldn't be change in how they are 
handled once they are loaded

  --

  1) Ubuntu 20.04 LTS
  2) Gnome Logs 3.34.0-1
  3) Open Gnome Logs and expect to be able to read all logs from the system
  4) Gnome Logs opens and at the top there is an error message "Unable to read 
system logs" - screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-logs 3.34.0-1
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 17:04:21 2020
  InstallationDate: Installed on 2020-05-17 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-logs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04

[Davide]

I tried libreoffice (calc and writer) on two real machines.
If I use the copy command from the context menu (mouse right click),
it fails once every two (second, fourth, sixth,...).
With the other methods the error rate is approximately 1/20 (the one indicated 
by Adam)

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

Title:
  copy/paste still sometimes fails in LibreOffice on Ubuntu 20.04

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1879776] Re: ubuntu 20 error mounting smb drive

[L Sluijter]

After adding 'client min protocol = NT1' to ~/.smb/smb.conf I could
indeed mount the disk via Nautilus, but that revealed another bug: most
files are seen as Directories instead of files (pdf, txt and so on), but
give an error when I try to open them.

I tried some more: A MOUNT with the CIFS option gives access to the disk
and I can read and write all files.

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

Title:
  ubuntu 20 error mounting smb drive

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  nautilus->other locations>windows network lists the shared disk I want
  to access. When I click on the name I get an errorbox: Unable to
  access location. Failed to mount windows share: Software caused
  connection abort.

  nautilus->other locations>Connect to server: smb://192.168.nnn.nnn
  gives the same errorbox.

  The shared disk is attached to my FritzBox router/modem.
  This works without problems in ubuntu 18 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 21:04:29 2020
  InstallationDate: Installed on 2020-04-20 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1879776/+subscriptions

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

[Desktop-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1

[Phil Macias]

I purged and installed jackd1
I never had but then installed jackd
I never had but then installed timidity

Rebooted and still only the dummy device and

#journalctl |grep pulseaudio

 Failed to open module "module-alsa-card".
May 21 13:47:15 CF-C2CQAZXCM pulseaudio[3849]: Failed to open module 
/usr/lib/pulse-13.99.1/modules/module-alsa-card.so: 
/usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: 
snd_use_case_parse_ctl_elem_id, version ALSA_0.9

alsamixer sees the cards

__END__

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

Title:
  ALSA sees my intel soundcards but pulseaudio does not.  Error is :
  "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-
  card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined
  symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  ALSA sees my intel soundcards but pulseaudio does not.

  'pavucontrol' sees only a "Dummy" device.

  #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open
  module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so:
  /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol:
  snd_use_case_parse_ctl_elem_id, version ALSA_0.9"

  Making pulseaudio from source fixes the problem/

  (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29
  14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 20 12:48:07 2020
  InstallationDate: Installed on 2015-04-29 (1848 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago)
  dmi.bios.date: 09/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.00L21
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CFC2-2
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFC2-2
  dmi.product.name: CF-C2CQAZXCM
  dmi.product.sku: CF-C2CQAZXCM
  dmi.product.version: 002
  dmi.sys.vendor: Panasonic Corporation
  mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45

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

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

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Rob Robertson]

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

This is not a duplicate of bug 1576559.   It is a duplicate of #1878194

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1880000] [NEW] impossible de monter le partage windows

[Nédelka Philippe]

Public bug reported:

Oups ! Quelque chose de mal s'est passé.

Message d'erreur non géré : impossible de monter le partage Windows : Le
logiciel a provoqué l'abandon de la connexion

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.1.1-1ubuntu2
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: Thu May 21 19:22:46 2020
InstallationDate: Installed on 2020-04-25 (25 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-05-09 (12 days ago)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  impossible de monter le partage windows

Status in nautilus package in Ubuntu:
  New

Bug description:
  Oups ! Quelque chose de mal s'est passé.

  Message d'erreur non géré : impossible de monter le partage Windows :
  Le logiciel a provoqué l'abandon de la connexion

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  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: Thu May 21 19:22:46 2020
  InstallationDate: Installed on 2020-04-25 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to focal on 2020-05-09 (12 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1879203] Re: combination Super + Space do not switch to another language

[imelnyk1347]

Thanks for your help, but I don`t understood what fix bug 1871913 (((

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

Title:
  combination Super + Space do not switch to another language

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After update Ubuntu(04/20), switching the language combination stopped
  working correctly Super + Space. At one time, the switching works
  correctly, but at the same moment it may immediately stop responding
  to the switching command.

  gnome-shell (3.36.1-5ubuntu2)

  Window manager warning: Overwriting existing binding of keysym 37 with keysym 
37 (keycode 10).
  Window manager warning: Overwriting existing binding of keysym 36 with keysym 
36 (keycode f).
  Window manager warning: Overwriting existing binding of keysym 39 with keysym 
39 (keycode 12).
  Window manager warning: Overwriting existing binding of keysym 38 with keysym 
38 (keycode 11).
  Window manager warning: Overwriting existing binding of keysym 35 with keysym 
35 (keycode e).
  Window manager warning: Overwriting existing binding of keysym 34 with keysym 
34 (keycode d).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer

[Till Kamppeter]

On the machine where you still have the problem could you remove your
print queue and then unplug and re-plug the printer? Does a new print
queue get automatically created?

What is the output of the following commands and post the output here:

lpstat -v
driverless
ps auxwww | grep ippusbxd

If a queue actually got auto-created for your printer, couls you attach
the queue's PPD file from /etc/cups/ppd/ here?

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

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

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  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: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1871377] Re: URW Nimbus font issue

[Till Kamppeter]

Reported upstream:

https://github.com/ArtifexSoftware/urw-base35-fonts/issues/28

** Bug watch added: github.com/ArtifexSoftware/urw-base35-fonts/issues #28
   https://github.com/ArtifexSoftware/urw-base35-fonts/issues/28

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

Title:
  URW Nimbus font issue

Status in fonts-urw-base35 package in Ubuntu:
  Confirmed

Bug description:
  It seems that cyrillic small letter `te` (afii10084) has wrong glyph in 
italic and bold Italic style: width is too big.
  This issue presented in OpenType and Type1 URW Nimbus Sans fonts distribution.

  I suggest to replace with the glyph of greek small `tau` letter.

  Attaching here the screenshots of some example words contain small
  letter `te` with original (wide) and replaced glyph.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1871377/+subscriptions

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

[Desktop-packages] [Bug 1876978] Re: gnome-screenshot clipboard image incomplete

[Chris Kankiewicz]

I received some updates today including gnome-shell, gnome-common and
mutter and this issue is now resolved. Oddly enough gnome-screenshots
was not updated and I still have the same version as before. For the
record here are the packages that were updated:

Start-Date: 2020-05-21  08:37:34
Commandline: apt upgrade
Requested-By: chris (1000)
Upgrade: gnome-shell-extension-prefs:amd64 (3.36.1-5ubuntu2, 
3.36.2-1ubuntu1~20.04.1), gir1.2-mutter-6:amd64 (3.36.1-3ubuntu3, 
3.36.2-1ubuntu1~20.04.1), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.1, 
2:4.11.6+dfsg-0ubuntu1.2), nodejs:amd64 (14.2.0-deb-1nodesource1, 
14.3.0-deb-1nodesource1), libmutter-6-0:amd64 (3.36.1-3ubuntu3, 
3.36.2-1ubuntu1~20.04.1), mutter-common:amd64 (3.36.1-3ubuntu3, 
3.36.2-1ubuntu1~20.04.1), samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.1, 
2:4.11.6+dfsg-0ubuntu1.2), gnome-shell-common:amd64 (3.36.1-5ubuntu2, 
3.36.2-1ubuntu1~20.04.1), libsmbclient:amd64 (2:4.11.6+dfsg-0ubuntu1.1, 
2:4.11.6+dfsg-0ubuntu1.2), gnome-shell:amd64 (3.36.1-5ubuntu2, 
3.36.2-1ubuntu1~20.04.1), mutter:amd64 (3.36.1-3ubuntu3, 
3.36.2-1ubuntu1~20.04.1)
End-Date: 2020-05-21  08:37:41

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

Title:
  gnome-screenshot clipboard image incomplete

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When running `gnome-screenshot` via terminal (or bash script) with
  both the `--clipboard` and `--file ...` options the screenshot copied
  to the clipboard is incomplete/corrupted while the screenshot saved to
  disk is fine. I'm able to reproduce this reliably via the following
  command:

  gnome-screenshot --clipboard --file "${HOME}/Pictures/Screenshot
  $(date +'%F %T').png" --window

  When running this command I expect to have one copy of the screenshot
  saved to disk and a (complete) copy of the screenshot copied to the
  clipboard automatically.

  Additional information:

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

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

  I've attached the incomplete/corrupted screenshot to this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screenshot 3.36.0-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: ubuntu:GNOME
  Date: Tue May  5 13:00:43 2020
  InstallationDate: Installed on 2020-04-23 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screenshot
  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/1876978/+subscriptions

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

Re: [Desktop-packages] [Bug 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04

[Adam Novak]

I haven't upgraded to Focal yet, but it's still an open issue upstream:
https://github.com/vim/vim/issues/5237

May 20, 2020 5:49 AM, "Sebastien Bacher"  wrote:

> Is that still an issue in focal?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813679
> 
> Title:
> vim-gtk can no longer save to non-group-writable files in GVFS SFTP
> mounts in 18.04
> 
> Status in gvfs package in Ubuntu:
> Invalid
> Status in nautilus package in Ubuntu:
> Invalid
> Status in vim package in Ubuntu:
> New
> 
> Bug description:
> In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH
> mounts (by going to `ssh://wherever` in the address bar in the file
> browser and double-clicking on the file), edit them, and save them.
> 
> In Ubuntu 18.04, when I install `vim-gtk` and try to do the same
> thing, I can open the files just fine, but when I try to save them I
> get a message that Vim "Can't open file for writing".
> 
> If I check out the Vim source tree and build and install vim
> v7.4.1689, which is what Xenial is shipping now, and use *that* gvim
> on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from
> gedit.
> 
> Something is wrong with the gvim shipping with 18.04.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: vim-gtk (not installed)
> ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
> Uname: Linux 4.15.0-44-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7.5
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Mon Jan 28 15:55:56 2019
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: vim
> UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions

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

Title:
  vim-gtk can no longer save to non-group-writable files in GVFS SFTP
  mounts in 18.04

Status in gvfs package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in vim package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH
  mounts (by going to `ssh://wherever` in the address bar in the file
  browser and double-clicking on the file), edit them, and save them.

  In Ubuntu 18.04, when I install `vim-gtk` and try to do the same
  thing, I can open the files just fine, but when I try to save them I
  get a message that Vim "Can't open file for writing".

  If I check out the Vim source tree and build and install vim
  v7.4.1689, which is what Xenial is shipping now, and use *that* gvim
  on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from
  gedit.

  Something is wrong with the gvim shipping with 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim-gtk (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 15:55:56 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874461] Re: gconf2.0 crashes repeatedly on upgrade to focal fossa

[Brian Murray]

** Tags removed: rls-ff-incoming

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

Title:
  gconf2.0 crashes repeatedly on upgrade to focal fossa

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Running update-manager -p today just before the release of focal
  fossa, the install halted during package configuration with a gconf2.0
  crash. I had to dismiss about 30 dialogs before the install completed,
  each exactly the same.

  I run stock ubuntu, except that I use the standard Gnome desktop
  instead of the Ubuntu unity Gnome variant. The machine in question has
  been upgraded from 18.04 to 19.10 & now to 20.04

  Since this package is now marked as only required for legacy
  applications, perhaps it needs removing before the focal upgrade?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: GNOME
  Date: Thu Apr 23 15:43:05 2020
  InstallationDate: Installed on 2018-07-19 (643 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

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

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

[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

[Ludovic Rousseau]

Please generate a pcscd log.
See https://ccid.apdu.fr/#support

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions

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

Re: [Desktop-packages] [Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling

[norberto]

No

El jue., 21 de may. de 2020 13:25, Sebastian Astra <
1871...@bugs.launchpad.net> escribió:

> Hello, do you have any updates on this matter?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1871849
>
> Title:
>   Full screen videos suddenly change scale when using fractional scaling
>
> Status in mutter package in Ubuntu:
>   Confirmed
>
> Bug description:
>   firefox does not properly play full screen videos using fractional scale
> at 125%
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 20.04
>   InstallationDate: Installed on 2020-03-29 (17 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200329)
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: gnome-shell 3.36.1-5ubuntu1
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
>   RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
>   Tags:  focal
>   Uname: Linux 5.4.0-24-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871849/+subscriptions
>

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

Title:
  Full screen videos suddenly change scale when using fractional scaling

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  firefox does not properly play full screen videos using fractional scale at 
125%
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-29 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Yuri]

@Pierre Equoy:

It looks like you are having 2 issues. The Sound selection UI not
appearing and no sound coming out after plug-in. Can you have a look at
this question https://answers.launchpad.net/ubuntu/+question/690501. Is
this the problem you are having with sound. Should I link my question to
your bug report?

It seems like its an issue with Dell's hardware and whatever changes
were made between 19.10 -> 20.04

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Rajasekharan N]

PPA statistics

Activity

3 updates added during the past month.

Currently 0 packages building and 1 package waiting to build.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Rajasekharan N]

I'm able to get only this version: pulseaudio 1:13.99.1-1ubuntu3.2.

The following are seen as pending:

i386 build of pulseaudio 1:13.99.1-1ubuntu3.2lp1869819 in ubuntu focal RELEASE
Pending (2510)
amd64 build of pulseaudio 1:13.99.1-1ubuntu3.2lp1869819 in ubuntu focal RELEASE
Pending (2510)

Pardon me if I am going wrong somewhere.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling

[Sebastian Astra]

Hello, do you have any updates on this matter?

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

Title:
  Full screen videos suddenly change scale when using fractional scaling

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  firefox does not properly play full screen videos using fractional scale at 
125%
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-03-29 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled

[Artem P]

Update fixed it for me.

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

Title:
  Display scale not remembered when X11 Fractional Scaling is enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

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

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

[Desktop-packages] [Bug 1879758] Re: Future all-day events from Google calendar display on all days in month view

[Sebastien Bacher]

Thanks, you are still using 19.10 and the issue is supposed to be fixed
in the new focal

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

** Changed in: gnome-calendar (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Future all-day events from Google calendar display on all days in
  month view

Status in gnome-calendar package in Ubuntu:
  Fix Released

Bug description:
  I have a Google calendar defined.  In the Gnome calendar app, events
  that:

  1) Are in the future
  2) Are all-day events
  3) Are recurring (every month, every year, etc)

  Only in the month view, these events display on every day in the
  month.  This doesn't happen in the week view.

  I've attached a screen shot.  The event "Nezahat yenge's birthday" is 
supposed to occur only on June 1st, but in the Month view, it occurs everyday, 
as an event that spans an entire week all month long.  This only occurs if the 
event is visible, so we see this effect only on May and June, not any other 
month.  It also happens in May and June of 2021 and any other year.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-02 (353 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-calendar 3.34.2-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-03-29 (53 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Kai-Heng Feng]

Sorry, I re-uploaded a new one with version is greater than the current
one. Please test that instead.

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Desktop-packages] [Bug 1879758] Re: Future all-day events from Google calendar display on all days in month view

[Timur Tabi]

apport information

** Tags added: apport-collected eoan

** Description changed:

  I have a Google calendar defined.  In the Gnome calendar app, events
  that:
  
  1) Are in the future
  2) Are all-day events
  3) Are recurring (every month, every year, etc)
  
  Only in the month view, these events display on every day in the month.
  This doesn't happen in the week view.
  
- I've attached a screen shot.  The event "Nezahat yenge's birthday" is
- supposed to occur only on June 1st, but in the Month view, it occurs
- everyday, as an event that spans an entire week all month long.  This
- only occurs if the event is visible, so we see this effect only on May
- and June, not any other month.  It also happens in May and June of 2021
- and any other year.
+ I've attached a screen shot.  The event "Nezahat yenge's birthday" is 
supposed to occur only on June 1st, but in the Month view, it occurs everyday, 
as an event that spans an entire week all month long.  This only occurs if the 
event is visible, so we see this effect only on May and June, not any other 
month.  It also happens in May and June of 2021 and any other year.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.8
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-06-02 (353 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gnome-calendar 3.34.2-1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
+ Tags:  eoan
+ Uname: Linux 5.3.0-53-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2020-03-29 (53 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1879758/+attachment/5375263/+files/Dependencies.txt

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

Title:
  Future all-day events from Google calendar display on all days in
  month view

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  I have a Google calendar defined.  In the Gnome calendar app, events
  that:

  1) Are in the future
  2) Are all-day events
  3) Are recurring (every month, every year, etc)

  Only in the month view, these events display on every day in the
  month.  This doesn't happen in the week view.

  I've attached a screen shot.  The event "Nezahat yenge's birthday" is 
supposed to occur only on June 1st, but in the Month view, it occurs everyday, 
as an event that spans an entire week all month long.  This only occurs if the 
event is visible, so we see this effect only on May and June, not any other 
month.  It also happens in May and June of 2021 and any other year.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-02 (353 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-calendar 3.34.2-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-03-29 (53 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1879982] [NEW] No grid lines and time indication in "High contrast" mode

[Michael Wögerbauer]

Public bug reported:

Hi,

this is my first bug report, I guess, so it might not be perfect -
excuses.

I love gnome-calendar as well as I love the very reduced look of gnome in "high 
contrast"-mode (→ Universal Access → High Contrast), which renders the icons in 
the dock as white (and minimalistic) as they are in the top panel. 
But in this mode, I don't see neither grid lines nor time and date indications 
in gnome calendar - the only thing I am able to see are scheduled meetings. 
This renders gnome calendar fairly unusable, when "High Contrast" is switched 
on (→ screenshot).

Even in high contrast mode, I would expect to see
- indications of date and day 
- some kind of grid
- time indications on the left

Thank you for the great and beautiful work,

Michael

* * *
Ubuntu 20.04 (freshly updated from 19.10)
Gnome calendar: 3.36.1

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

** Attachment added: "Gnome High Contrast with Calendar.png"
   
https://bugs.launchpad.net/bugs/1879982/+attachment/5375262/+files/Gnome%20High%20Contrast%20with%20Calendar.png

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

Title:
  No grid lines and time indication in "High contrast" mode

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Hi,

  this is my first bug report, I guess, so it might not be perfect -
  excuses.

  I love gnome-calendar as well as I love the very reduced look of gnome in 
"high contrast"-mode (→ Universal Access → High Contrast), which renders the 
icons in the dock as white (and minimalistic) as they are in the top panel. 
  But in this mode, I don't see neither grid lines nor time and date 
indications in gnome calendar - the only thing I am able to see are scheduled 
meetings. This renders gnome calendar fairly unusable, when "High Contrast" is 
switched on (→ screenshot).

  Even in high contrast mode, I would expect to see
  - indications of date and day 
  - some kind of grid
  - time indications on the left

  Thank you for the great and beautiful work,

  Michael

  * * *
  Ubuntu 20.04 (freshly updated from 19.10)
  Gnome calendar: 3.36.1

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

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

[Desktop-packages] [Bug 1874461] Re: gconf2.0 crashes repeatedly on upgrade to focal fossa

[Steve Langasek]

** Package changed: ubuntu-release-upgrader (Ubuntu) => gconf (Ubuntu)

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

Title:
  gconf2.0 crashes repeatedly on upgrade to focal fossa

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Running update-manager -p today just before the release of focal
  fossa, the install halted during package configuration with a gconf2.0
  crash. I had to dismiss about 30 dialogs before the install completed,
  each exactly the same.

  I run stock ubuntu, except that I use the standard Gnome desktop
  instead of the Ubuntu unity Gnome variant. The machine in question has
  been upgraded from 18.04 to 19.10 & now to 20.04

  Since this package is now marked as only required for legacy
  applications, perhaps it needs removing before the focal upgrade?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: GNOME
  Date: Thu Apr 23 15:43:05 2020
  InstallationDate: Installed on 2018-07-19 (643 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

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

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

[Desktop-packages] [Bug 1879758] ProcCpuinfoMinimal.txt

[Timur Tabi]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1879758/+attachment/5375264/+files/ProcCpuinfoMinimal.txt

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

Title:
  Future all-day events from Google calendar display on all days in
  month view

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  I have a Google calendar defined.  In the Gnome calendar app, events
  that:

  1) Are in the future
  2) Are all-day events
  3) Are recurring (every month, every year, etc)

  Only in the month view, these events display on every day in the
  month.  This doesn't happen in the week view.

  I've attached a screen shot.  The event "Nezahat yenge's birthday" is 
supposed to occur only on June 1st, but in the Month view, it occurs everyday, 
as an event that spans an entire week all month long.  This only occurs if the 
event is visible, so we see this effect only on May and June, not any other 
month.  It also happens in May and June of 2021 and any other year.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-02 (353 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-calendar 3.34.2-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-53.47-generic 5.3.18
  Tags:  eoan
  Uname: Linux 5.3.0-53-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2020-03-29 (53 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1874461] [NEW] gconf2.0 crashes repeatedly on upgrade to focal fossa

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Running update-manager -p today just before the release of focal fossa,
the install halted during package configuration with a gconf2.0 crash. I
had to dismiss about 30 dialogs before the install completed, each
exactly the same.

I run stock ubuntu, except that I use the standard Gnome desktop instead
of the Ubuntu unity Gnome variant. The machine in question has been
upgraded from 18.04 to 19.10 & now to 20.04

Since this package is now marked as only required for legacy
applications, perhaps it needs removing before the focal upgrade?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: GNOME
Date: Thu Apr 23 15:43:05 2020
InstallationDate: Installed on 2018-07-19 (643 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
VarLogDistupgradeTermlog:

mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

** Affects: gconf (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug dist-upgrade focal rls-ff-incoming
-- 
gconf2.0 crashes repeatedly on upgrade to focal fossa
https://bugs.launchpad.net/bugs/1874461
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gconf in Ubuntu.

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

[Desktop-packages] [Bug 1879776] Re: ubuntu 20 error mounting smb drive

[Sebastien Bacher]

could you try adding 'client min protocol = NT1' to ~/.smb/smb.conf ?

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

Title:
  ubuntu 20 error mounting smb drive

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  nautilus->other locations>windows network lists the shared disk I want
  to access. When I click on the name I get an errorbox: Unable to
  access location. Failed to mount windows share: Software caused
  connection abort.

  nautilus->other locations>Connect to server: smb://192.168.nnn.nnn
  gives the same errorbox.

  The shared disk is attached to my FritzBox router/modem.
  This works without problems in ubuntu 18 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 21:04:29 2020
  InstallationDate: Installed on 2020-04-20 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1879776/+subscriptions

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

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

[Robert Sandell]

Public bug reported:

Fresh Ubuntu 18.04.4 LTS bionic installation.
Nouveau driver.
One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
Other programs like Firefox and Terminal seem to run fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-53-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 21 17:14:11 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
InstallationDate: Installed on 2020-05-21 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.90
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.90:bd12/06/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic crash ubuntu

** Attachment added: "crash.zip"
   https://bugs.launchpad.net/bugs/1879977/+attachment/5375228/+files/crash.zip

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Fresh Ubuntu 18.04.4 LTS bionic installation.
  Nouveau driver.
  One DVI cable attached directly to the graphics card, and one DVI + one VGA 
attached to the motherboard.
  When I attempted to open "Display" settings the x-org session crashes and 
reverts to the login screen.
  Other programs like Firefox and Terminal seem to run fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-53-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 17:14:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic 
root=UUID=ddd8f597-f590-4fc5-ac56-8ba3805b40e8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: disp

[Desktop-packages] [Bug 1879776] Re: ubuntu 20 error mounting smb drive

[L Sluijter]

~/.smb/smb.conf  is present, last change date dec 2015.

I installed the smbclient package, and indeed could get to the disk with
smbclient //192.168.178.253/fb7490a without an errormessage. At least ls
and cd are working. (I have no knowledge of smbclient (yet) so it did
not access the data yet.)

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

Title:
  ubuntu 20 error mounting smb drive

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 LTS

  nautilus->other locations>windows network lists the shared disk I want
  to access. When I click on the name I get an errorbox: Unable to
  access location. Failed to mount windows share: Software caused
  connection abort.

  nautilus->other locations>Connect to server: smb://192.168.nnn.nnn
  gives the same errorbox.

  The shared disk is attached to my FritzBox router/modem.
  This works without problems in ubuntu 18 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 21:04:29 2020
  InstallationDate: Installed on 2020-04-20 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  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/1879776/+subscriptions

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