[Desktop-packages] [Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)

[Daniel van Vugt]

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.

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

Title:
  Snap Store can't install or remove snaps on 20.04 (password prompt
  issue?)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 20.04 the older App store disappeared and the Snap Store 
appeared. 
  However this version of the snap store can't seem to install or remove any 
snaps. 
  This seems to be due to a broken step in the user password prompt pop up. 
  Because the password prompt does not come up the Snap Store does not have the 
necessary permissions to add or remove snaps.

  When I try this in the terminal I need to use sudo

  > edu@Edu-laptop:~$ snap remove gitkraken 
  > error: access denied (try with sudo)
  > edu@Edu-laptop:~$ sudo snap remove gitkraken 
  > [sudo] password for edu: 
  > gitkraken removed
  > edu@Edu-laptop:~$ 

  However as soon as I typed the password and pressed enter the screen flashed 
and my Brave browser session was killed. 
  - This seems to be an issue with many instances when the user's password is 
requested. 

  Asking for the user's password should not kill apps or the session.
  This might be related to the screen lock issue (
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866888 ).

  Since this is related to user password management I'm flagging it as
  security related, feel free to downgrade if no risk is present.

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

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

[Desktop-packages] [Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)

[Daniel van Vugt]

Does re-enabling animations avoid the bug? I am wondering if this is
related to bug 1866044.

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

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

Title:
  Snap Store can't install or remove snaps on 20.04 (password prompt
  issue?)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 20.04 the older App store disappeared and the Snap Store 
appeared. 
  However this version of the snap store can't seem to install or remove any 
snaps. 
  This seems to be due to a broken step in the user password prompt pop up. 
  Because the password prompt does not come up the Snap Store does not have the 
necessary permissions to add or remove snaps.

  When I try this in the terminal I need to use sudo

  > edu@Edu-laptop:~$ snap remove gitkraken 
  > error: access denied (try with sudo)
  > edu@Edu-laptop:~$ sudo snap remove gitkraken 
  > [sudo] password for edu: 
  > gitkraken removed
  > edu@Edu-laptop:~$ 

  However as soon as I typed the password and pressed enter the screen flashed 
and my Brave browser session was killed. 
  - This seems to be an issue with many instances when the user's password is 
requested. 

  Asking for the user's password should not kill apps or the session.
  This might be related to the screen lock issue (
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866888 ).

  Since this is related to user password management I'm flagging it as
  security related, feel free to downgrade if no risk is present.

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

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

[Desktop-packages] [Bug 1867090] [NEW] IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

[ytxmobile]

Public bug reported:

When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

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


** Tags: chinese

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

Title:
  IBus 1.5.21 Chinese input in Ubuntu 19.10 not working with Atom 1.45.0

Status in ibus package in Ubuntu:
  New

Bug description:
  When I switch to Chinese input mode (Intelligent Pinyin) and try to type 
Chinese into Atom 1.45.0, it simply doesn't work.
  When I type the letters into the window, it shall bring up the candidate list 
for me to pick words. But instead, the letters are directly typed into the 
window, but not Chinese characters.

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

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

[Desktop-packages] [Bug 1866044] Re: gnome-shell crashed with signal 5 in clutter_box_layout_allocate() when enable-animations=false

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with signal 5 in clutter_box_layout_allocate()
+ gnome-shell crashed with signal 5 in clutter_box_layout_allocate() when 
enable-animations=false

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

Title:
  gnome-shell crashed with signal 5 in clutter_box_layout_allocate()
  when enable-animations=false

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Starting this morning after updating my focal system, some GPG/SSH key
  prompts will cause the entire shell to instantly crash. I also had a
  similar shell crash happen when trying to unlock my laptop after
  having it locked for a little while (but not suspended).

  This unfortunately isn't easy reproduced on demand, but I've had 5
  gnome-shell crashes over the past 4 hours when I have had none of the
  3 months prior, so something feels quite wrong and makes getting any
  work done quite difficult.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 08:45:46 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LocalLibraries: 
/home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   clutter_actor_allocate () at 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to focal on 2018-12-17 (443 days ago)
  UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner 
sudo video
  separator:

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

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

[Desktop-packages] [Bug 1866703] Re: gnome-shell crashes on lock screen

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1866044
   gnome-shell crashed with signal 5 in clutter_box_layout_allocate()

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

Title:
  gnome-shell crashes on lock screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After latest focal updates, gnome-shell crashes and I lose my entire
  session when I lock the screen.

  c@slate:~$ dpkg -l | grep gnome-shell
  ii  gnome-shell3.35.91-1ubuntu2   
 amd64graphical shell for the GNOME desktop

  c@slate:~$ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  syslog at the time of crash shows:

  Mar  9 15:40:59 slate gnome-shell[14000]: ClutterBoxLayout child 
Gjs_ui_shellEntry_CapsLockWarning natural height: 0.00 < minimum 24.00 
for width 337.00
  Mar  9 15:40:59 slate kernel: [ 6402.118795] traps: gnome-shell[14000] trap 
int3 ip:7f7562fb60d5 sp:7fff34854e80 error:0 in 
libglib-2.0.so.0.6400.0[7f7562f7a000+84000]
  Mar  9 15:40:59 slate quasselclient[14674]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-power[14200]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[14199]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate evolution-alarm[14258]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-wacom[14211]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate update-notifier[15178]: Error reading events from 
display: Broken pipe
  Mar  9 15:40:59 slate gsd-color[14190]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate gsd-keyboard[14196]: Error reading events from display: 
Broken pipe
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-power.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-keyboard.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-media-keys.service: Failed with 
result 'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar  9 15:40:59 slate systemd[1660]: gsd-wacom.service: Failed with result 
'exit-code'.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Keyboard handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Media keys handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Power management 
handling.
  Mar  9 15:40:59 slate systemd[1660]: Stopped target GNOME Wacom handling.
  Mar  9 15:40:59 slate systemd[1660]: gnome-shell-wayland.service: Main 
process exited, code=dumped, status=5/TRAP
  Mar  9 15:40:59 slate gnome-shell[14035]: (EE) failed to read Wayland events: 
Broken pipe
  Mar  9 15:40:59 slate gsd-media-keys[16326]: X connection to :0 broken 
(explicit kill or server shutdown).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 15:49:14 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-08-26 (561 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-23 (46 days ago)

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

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

[Desktop-packages] [Bug 1866745] Re: Extreme slow Ubuntu startup

[Daniel van Vugt]

** Package changed: gnome-shell (Ubuntu) => linux (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/1866745

Title:
  Extreme slow Ubuntu startup

Status in linux package in Ubuntu:
  New

Bug description:
  With the latest live release, starting takes around 4:30 to get to the
  jingle and around 5:40 to get Ubuntu up and running. With the version
  of 24-01-2020 instead 0:47 and 1:08 respectively. The boot time with
  the latest releases is exaggerated. Please check and correct the
  problem. Thank you.

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

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

[Desktop-packages] [Bug 1866523] Re: Kernel 5.6-rc4 wont compile with nvidia 440.64

[Daniel van Vugt]

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

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kernel 5.6-rc4 wont compile with nvidia 440.64

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  According to Nvidia 440.64 should compile with kernel 5.6

  Attempted kernel install with UKUU 19.12.1

  make.log attached

  make[1]: Entering directory '/usr/src/linux-headers-5.6.0-050600rc4-generic'
  test -e include/generated/autoconf.h -a -e include/config/auto.conf || (  
\
  echo >&2; \
  echo >&2 "  ERROR: Kernel configuration is invalid.";

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.5.8-050508-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-23ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  7 21:31:57 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.5.8-050508-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU104BM [GeForce RTX 2080 Mobile] 
[1043:135f]
  InstallationDate: Installed on 2020-03-03 (4 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. ROG G703GXR_G703GXR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-050508-generic 
root=UUID=3fc82c83-da27-480b-a875-214d33bc18e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G703GXR.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G703GXR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG703GXR.302:bd07/11/2019:svnASUSTeKCOMPUTERINC.:pnROGG703GXR_G703GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG703GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: ROG G703GXR_G703GXR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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/linux/+bug/1866523/+subscriptions

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

[Desktop-packages] [Bug 1796451] Re: gjs-console crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

[Launchpad Bug Tracker]

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

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

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

Title:
  gjs-console crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in gjs package in Ubuntu:
  Confirmed

Bug description:
  in the terminal while type in, gnome-sound-recorder, the following
  messages shown and the application can load but the recording is
  problematic. The timing on the GUI seems much slower than the actual
  time. When I stopped the recording and clicked "play". The Application
  exited abruptly.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.234: Some code 
accessed the property 'Application' on the module 'application'. That property 
was defined with 'let' or 'const' inside the module. This was previously 
supported, but is not correct according to the ES6 standard. Any symbols to be 
exported from a module must be defined with 'var'. The property access will 
work as previously for the time being, but please fix your code anyway.
  Gjs-Message: 13:29:05.320: JS LOG: Sound Recorder started
  Gjs-Message: 13:29:05.321: JS WARNING: 
[resource:///org/gnome/SoundRecorder/js/application.js 84]: Too many arguments 
to function Gst.init: expected 1, got 2

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.338: Some
  code accessed the property 'MainWindow' on the module 'mainWindow'.
  That property was defined with 'let' or 'const' inside the module.
  This was previously supported, but is not correct according to the ES6
  standard. Any symbols to be exported from a module must be defined
  with 'var'. The property access will work as previously for the time
  being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.339: Some
  code accessed the property 'AudioProfile' on the module
  'audioProfile'. That property was defined with 'let' or 'const' inside
  the module. This was previously supported, but is not correct
  according to the ES6 standard. Any symbols to be exported from a
  module must be defined with 'var'. The property access will work as
  previously for the time being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.339: Some
  code accessed the property 'OffsetController' on the module
  'fileUtil'. That property was defined with 'let' or 'const' inside the
  module. This was previously supported, but is not correct according to
  the ES6 standard. Any symbols to be exported from a module must be
  defined with 'var'. The property access will work as previously for
  the time being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.339: Some
  code accessed the property 'DisplayTime' on the module 'fileUtil'.
  That property was defined with 'let' or 'const' inside the module.
  This was previously supported, but is not correct according to the ES6
  standard. Any symbols to be exported from a module must be defined
  with 'var'. The property access will work as previously for the time
  being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.340: Some
  code accessed the property 'Listview' on the module 'listview'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6
  standard. Any symbols to be exported from a module must be defined
  with 'var'. The property access will work as previously for the time
  being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.341: Some
  code accessed the property 'Record' on the module 'record'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6
  standard. Any symbols to be exported from a module must be defined
  with 'var'. The property access will work as previously for the time
  being, but please fix your code anyway.

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.341: Some code 
accessed the property 'Play' on the module 'play'. That property was defined 
with 'let' or 'const' inside the module. This was previously supported, but is 
not correct according to the ES6 standard. Any symbols to be exported from a 
module must be defined with 'var'. The property access will work as previously 
for the time being, but please fix your code anyway.
  Gjs-Message: 13:29:05.456: JS WARNING: 
[resource:///org/gnome/SoundRecorder/js/listview.js 110]: reference to 
undefined property 1

  (org.gnome.SoundRecorder:4448): Gjs-WARNING **: 13:29:05.456: Some
  code accessed the property 'displayTime' on the module 'mainWindow'.
  That property was defined with 'let' or 'const' inside the module.

[Desktop-packages] [Bug 1866419] Re: gnome-shell displays date incorrectly for nl_NL locale

[Daniel van Vugt]

Please report the bug to the gnome-shell developers here:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and then tell us the new bug ID.

** Tags added: bionic eoan focal

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

Title:
  gnome-shell displays date incorrectly for nl_NL locale

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am running the regular edition of Ubuntu. I have my system set to
  the nl_NL locale. The clock display on the top bar of gnome-shell is
  displayed as "vr mrt 6 23:45:01". While the individual parts are
  translated correctly, the order is not. It should be "vr 6 mrt
  23:45:01".

  Steps to reproduce:
  - Install in Dutch
  - Observe that the clock in the top bar shows the month name before the day.

  Other notes:
  - Bug is present in at least 18.04, 19.04, 19.10 and the upcoming 20.04
  - Adding/removing parts to the date (like weekday, seconds, etc.) using 
gnome-tweaks does not make any difference: all combinations have this wrong 
date order.

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

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

[Desktop-packages] [Bug 1866044] Re: gnome-shell crashed with signal 5 in clutter_box_layout_allocate()

[Daniel van Vugt]

** Tags added: fixed-in-3.35.92 fixed-upstream

** Information type changed from Private to Public

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

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

Title:
  gnome-shell crashed with signal 5 in clutter_box_layout_allocate()

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Starting this morning after updating my focal system, some GPG/SSH key
  prompts will cause the entire shell to instantly crash. I also had a
  similar shell crash happen when trying to unlock my laptop after
  having it locked for a little while (but not suspended).

  This unfortunately isn't easy reproduced on demand, but I've had 5
  gnome-shell crashes over the past 4 hours when I have had none of the
  3 months prior, so something feels quite wrong and makes getting any
  work done quite difficult.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 08:45:46 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LocalLibraries: 
/home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
   clutter_actor_allocate () at 
/usr/lib/x86_64-linux-gnu/mutter-6/libmutter-clutter-6.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to focal on 2018-12-17 (443 days ago)
  UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner 
sudo video
  separator:

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

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

[Desktop-packages] [Bug 1866222] Re: GNOME Shell crashed with signal 11

[Daniel van Vugt]

Stéphane, please do not comment on this bug. Instead please open a new
bug.

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

Title:
  GNOME Shell crashed with signal 11

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-shell has crashed twice on me today.

  Unfortunately there's nothing in /var/crash.

  There's nothing in the journalctl log prior to the crash that explains
  it.

  I've attached a log of everything between when the crash happened and
  when I logged back in (though I suspect most of it is not relevant).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 13:04:21 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (201 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago)

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

-- 
Mailing list: https://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 1854120] Re: Screen contents visible briefly on lock screen on resolution change

[Dushyant]

Hi,

This was very hard to replicate multiple times on my setup later. I also
have a nagging feeling, It could be possibly be an issue with AnyDesk
actually showing my host screen IDE for a fraction of a second which
matched my Ubuntu screen which brought up the confusion.

I myself can't accurately replicate this again, please feel free to close
the issue.


Thanks & Regards,

-Dushyant Min


On Wed, Mar 11, 2020 at 8:21 PM Marc Deslauriers <
marc.deslauri...@canonical.com> wrote:

> ** Changed in: lightdm (Ubuntu)
>Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1854120
>
> Title:
>   Screen contents visible briefly on lock screen on resolution change
>
> Status in lightdm package in Ubuntu:
>   Triaged
>
> Bug description:
>   I am using a remote application to AnyDesk to remote access my Ubuntu
>   16.04 LTS 64 bit. On the application we can resize the screen and have
>   the resolution of the target computer scale up and down when this is
>   done.
>
>   When the computer is locked on the login screen if the screen is
>   resized ( resolution changes ) - For a brief fraction of a second the
>   unlocked screen flashes and the login screen shows up again. I think
>   this is a security breach to be able to peek into the inside contents
>   even though the computer is locked.
>
>   Please feel free to close this issue if this is an already known issue
>   or if its already fixed in later releases.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1854120/+subscriptions
>

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

Title:
  Screen contents visible briefly on lock screen on resolution change

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  I am using a remote application to AnyDesk to remote access my Ubuntu
  16.04 LTS 64 bit. On the application we can resize the screen and have
  the resolution of the target computer scale up and down when this is
  done.

  When the computer is locked on the login screen if the screen is
  resized ( resolution changes ) - For a brief fraction of a second the
  unlocked screen flashes and the login screen shows up again. I think
  this is a security breach to be able to peek into the inside contents
  even though the computer is locked.

  Please feel free to close this issue if this is an already known issue
  or if its already fixed in later releases.

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

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

[Desktop-packages] [Bug 1866995] Re: XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1867080
   [radeon] No mouse cursor drawn in Wayland session

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

Title:
  XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The cursor is there, just invisible. If one moves the mouse around one
  can see that it's there, but not visible. Tested in both Ubuntu
  XWayland session and Gnome Vanillia session. It's working OK in Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 08:24:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-xanmod6 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1865996] Re: GDM Theme Inconsistant Init Login vs Screen Lock

[Daniel van Vugt]

Note that GDM is not graphical and has no theme. More likely you're
thinking of gnome-shell which also draws the lock screen. The theme for
that is provided by yaru-theme.


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

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

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

Title:
  GDM Theme Inconsistant Init Login vs Screen Lock

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The initial login theme of first login at machine startup is
  completely different (looks much older) than the theme used for when
  the machine is restored from screen lock (looks very new).

  Ideally the same theme is used in both circumstances for consistency.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 08:14:55 2020
  InstallationDate: Installed on 2020-02-12 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  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/1865996/+subscriptions

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

[Desktop-packages] [Bug 1867017] Re: Cursor Invisible, but there.

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1867080
   [radeon] No mouse cursor drawn in Wayland session

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

Title:
  Cursor Invisible, but there.

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  Further to my previous bug for XWayland same issue. I should probably
  note that this isn't a clean install but an upgrade from 19.10 on bare
  metal. HTH.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:37:49 2020
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1865896] Re: totem segfaults on ubuntu-mate 18.04

[Daniel van Vugt]

Those bugs don't appear to be relevant. Please try following all the
steps in comment #2 again.

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

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

Title:
  totem segfaults on ubuntu-mate 18.04

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Totem crashes on launch along with the desktop/Xorg. BTW I am not
  using any dm but only managing my desktop with openbox wm.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu6.2
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar  3 21:43:10 2020
  InstallationDate: Installed on 2018-05-11 (661 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866712] Re: Graphic glitches with Nvidia 440 on Dell XPS 15 9570

[Daniel van Vugt]

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

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Graphic glitches with Nvidia 440 on Dell XPS 15 9570

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  I am experiencing intermittent graphical glitches. I couldn't find
  where this had been reported before so please excuse the duplicate if
  this is a known issue. I tried recording my screen to demonstrate what
  is happening but, although I am seeing the issue on the desktop, it
  does not show up in the video. I am using prime-select in intel mode.

  
  System:Host: rex Kernel: 5.5.7-050507-generic x86_64 bits: 64 Desktop: 
Gnome 3.35.91 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Laptop System: Dell product: XPS 15 9570 v: N/A serial: 
 
 Mobo: Dell model: 0D0T05 v: A00 serial:  UEFI: Dell 
v: 1.15.0 date: 12/25/2019 
  CPU:   Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP 
L2 cache: 9216 KiB 
 Speed: 2057 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 2112 
2: 894 3: 1909 4: 2159 5: 2345 6: 1979 
 7: 1579 8: 2316 9: 1214 10: 988 11: 2344 12: 929 
  Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
 Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A 
 Display: x11 server: X.Org 1.20.7 driver: modesetting,nvidia 
unloaded: fbdev,nouveau,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 
Mesa 20.0.0 
  Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
 Device-2: Texas Instruments PCM2902 Audio Codec type: USB driver: 
hid-generic,snd-usb-audio,usbhid 
 Sound Server: ALSA v: k5.5.7-050507-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.5.7-050507-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  9 13:20:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.59, 5.4.0-14-generic, x86_64: installed
   nvidia, 440.59, 5.5.7-050507-generic, x86_64: installed
   v4l2loopback, 0.12.3, 5.5.7-050507-generic, x86_64: installed
   virtualbox, 6.1.4, 5.5.7-050507-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
  InstallationDate: Installed on 2020-03-03 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  MachineType: Dell Inc. XPS 15 9570
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.7-050507-generic 
root=UUID=5490caea-406b-4a4c-afee-178210995fe8 ro quiet splash 
mem_sleep_default=deep
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  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.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

FYI, the relevant changes are documented in:

https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.3
https://launchpad.net/ubuntu/+source/alsa-lib/1.1.3-5ubuntu0.4

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

** Changed in: alsa-lib (Ubuntu)
   Status: New => Fix Committed

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in alsa-lib package in Ubuntu:
  Fix Committed

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Desktop-packages] [Bug 1866552] Re: xorg crashed on totem launch on ubuntu-mate-1804

[Daniel van Vugt]

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.


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

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

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

Title:
  xorg crashed on totem launch on ubuntu-mate-1804

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  xorg crashed on totem launch on ubuntu-mate-1804.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sun Mar  8 21:47:12 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694]
   NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] 
[19da:2476]
  InstallationDate: Installed on 2018-05-11 (666 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet 
K-2024 Multimedia Keyboard
   Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=c14b0e5e-bdb0-4d30-87f0-0879253545d0 ro acpi=force iomem=relaxed 
random.trust_cpu=on initcall_debug console=tty0 console=ttyS0,115200 
earlyprintk=ttyS0,115200
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-E/M.2
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd05/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-E/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  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 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1865371] Re: Mouse Cursor or Touchpad indicator/pointer not working

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1867080
   [radeon] No mouse cursor drawn in Wayland session

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

Title:
  Mouse Cursor or Touchpad indicator/pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  after some updates this week, my mouse/touchapad
  cursor/indicator/pointer started not working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.7-050507-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 20:29:07 2020
  InstallationDate: Installed on 2017-07-14 (960 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170714)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2018-10-29T04:23:27.400327

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

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

[Desktop-packages] [Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds

[Daniel van Vugt]

Thanks. If the bug isn't in 20.04 then we can declare it fixed already.
And if we knew what change fixed it then we could propose a fix to
19.10...

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

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  When I open LibreOffce Writer and decides to resize the Style window
  on the right of the screen (press F11 to toggle this window), Gnome-
  Shell completely freezes for a few seconds.

  I already rebooted and it's 100% reproducible.

  I initially reported this bug on Gnome-Shell Gitlab:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411

  You can find more info there (journalctl logs)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-26 (150 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1865316] Re: Desktop blinks / flashes after unlocking the system ubuntu 18.04.4

[Daniel van Vugt]

And while the problem is happening run:

  journalctl -b0 > journal.txt

and attach the file 'journal.txt' here.

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

Title:
  Desktop blinks / flashes after unlocking the system ubuntu 18.04.4

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My ubuntu desktop gnome3 is started flashing after unlocking the
  machine, i tired lock and unlock twise still the problem remains.

  
  OS:   Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  System configuration

  Processor: AMD Ryzen 7-3750H processor, 2.3GHz Base speed (6MB cache, up to 
4.0 GHz)
  Memory & Storage: 8GB DDR4 2400MHz RAM upgradeable upto 32GB RAM with| NVIDIA 
GeForce GTX 1650 GDDR5 4GB VRAM Graphics| Storage: 1TB 5400RPM 2.5' HDD + PCIe 
NVMe 256GB M.2 SSD 

  
  please help me to resolve this issue
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 5.5.8-050508-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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-shell/+bug/1865316/+subscriptions

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

[Desktop-packages] [Bug 1865316] Re: Desktop blinks / flashes after unlocking the system ubuntu 18.04.4

[Daniel van Vugt]

Please also run:

  lspci -k > lspcik.txt

and then attach the file 'lspcik.txt' here.

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

Title:
  Desktop blinks / flashes after unlocking the system ubuntu 18.04.4

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  My ubuntu desktop gnome3 is started flashing after unlocking the
  machine, i tired lock and unlock twise still the problem remains.

  
  OS:   Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  System configuration

  Processor: AMD Ryzen 7-3750H processor, 2.3GHz Base speed (6MB cache, up to 
4.0 GHz)
  Memory & Storage: 8GB DDR4 2400MHz RAM upgradeable upto 32GB RAM with| NVIDIA 
GeForce GTX 1650 GDDR5 4GB VRAM Graphics| Storage: 1TB 5400RPM 2.5' HDD + PCIe 
NVMe 256GB M.2 SSD 

  
  please help me to resolve this issue
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-01 (7 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 5.5.8-050508-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  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-shell/+bug/1865316/+subscriptions

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

[Desktop-packages] [Bug 1866371] Re: Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March update

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1867080
   [radeon] No mouse cursor drawn in Wayland session

** No longer affects: wayland (Ubuntu)

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

Title:
  Mouse cursor disappears in Ubuntu 20.04 on Wayland since 5th March
  update

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu 20.04 (Gnome Shell) development version.

  Since I made the updates on 5th March, I have no more mouse cursor
  visible, on the login screen nor on the desktop session.

  Mouse is OK, as if I move it I can see some items / buttons
  highlighted, and if I click the mouse, it works well. I tried Yaru and
  DMZ Black themes, no cursor, it's completely invisible.

  I started several times, always no cursor. But if I switch to the Xorg
  (X11) session, mouse cursor is well back and visible.

  My graphic card :

  description: VGA compatible controller
 produit: Cape Verde XT [Radeon HD 7770/8760 / R7 250X]
 fabricant: Advanced Micro Devices, Inc. [AMD/ATI]
 identifiant matériel: 0
 information bus: pci@:01:00.0
 version: 00
 bits: 64 bits
 horloge: 33MHz
 fonctionnalités: pm pciexpress msi vga_controller bus_master cap_list 
rom
 configuration : driver=radeon latency=0

  Thanks !

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

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

[Desktop-packages] [Bug 1867080] Re: No mouse cursor drawn in Wayland session

[Daniel van Vugt]

** Tags added: radeon

** Summary changed:

- No mouse cursor drawn in Wayland session
+ [radeon] No mouse cursor drawn in Wayland session

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

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

** Tags added: champagne

** Tags added: fixed-in-3.36.0 fixed-upstream

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

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

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

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

Title:
  [radeon] No mouse cursor drawn in Wayland session

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1867080] Re: No mouse cursor drawn in Wayland session

[James Henstridge]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+attachment/5335924/+files/lspci.txt

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

Title:
  [radeon] No mouse cursor drawn in Wayland session

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1867080] Re: No mouse cursor drawn in Wayland session

[Daniel van Vugt]

ShellJournal.txt is showing:

[   68.636098] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.652801] scruffy gnome-shell[2974]: unset_crtc_cursor: assertion 
'cursor_plane' failed
[   68.653185] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.669752] scruffy gnome-shell[2974]: unset_crtc_cursor: assertion 
'cursor_plane' failed
[   68.670106] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.685755] scruffy gnome-shell[2974]: unset_crtc_cursor: assertion 
'cursor_plane' failed
[   68.686143] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.702795] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.703194] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed
[   68.719882] scruffy gnome-shell[2974]: set_crtc_cursor: assertion 
'cursor_plane' failed

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

** Tags added: wayland wayland-session

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

Title:
  [radeon] No mouse cursor drawn in Wayland session

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1867080] [NEW] No mouse cursor drawn in Wayland session

[James Henstridge]

Public bug reported:

When I upgraded my desktop yesterday, I could no longer see the mouse
cursor on the screen.  It still responded to mouse clicks (e.g. context
menu on right click, pushing the mouse to the top left and left clicking
went to spread mode, etc).

This only seems to affect the Wayland session: when I switched back to
X11 the mouse cursor was visible again.  I also noticed that the mouse
cursor is absent on the GDM login screen, which I understand is also a
Wayland based gnome-shell session.

I tried reproducing the bug on my laptop, but the mouse cursor shows
just fine there.  The main differences between the systems are the GPU
(radeon vs. intel) and number of monitors (dual screen vs. single).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 12 10:28:55 2020
DisplayManager: gdm3
InstallationDate: Installed on 2013-10-29 (2325 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  No mouse cursor drawn in Wayland session

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I upgraded my desktop yesterday, I could no longer see the mouse
  cursor on the screen.  It still responded to mouse clicks (e.g.
  context menu on right click, pushing the mouse to the top left and
  left clicking went to spread mode, etc).

  This only seems to affect the Wayland session: when I switched back to
  X11 the mouse cursor was visible again.  I also noticed that the mouse
  cursor is absent on the GDM login screen, which I understand is also a
  Wayland based gnome-shell session.

  I tried reproducing the bug on my laptop, but the mouse cursor shows
  just fine there.  The main differences between the systems are the GPU
  (radeon vs. intel) and number of monitors (dual screen vs. single).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 12 10:28:55 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-10-29 (2325 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago)

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

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

[Desktop-packages] [Bug 1857122] Re: New Windows are opened below other windows and require extra clicks to acees

[Daniel van Vugt]

** Tags added: focal

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

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

Title:
  New Windows are opened below other windows and require extra clicks to
  acees

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when opening new windows the new window is opened below
  other windows.

  This behaviour is not consistent. Sometimes it happens and sometimes
  it does not happen. This is rather unpredictable and very frustrating.

  The problem got horribly worde when moving to a fast computer running
  Ubuntu 19.10

  This behaviour causes typing to go to the wrong window so sometimes when I 
already start typing expected entry just to discover the actual window I am 
expecting is hidden and the actual typing goes to the wrong place.
  This can easily lead to revealing of sensitive information therefore IMHO it 
should be treated as a security issue.
  I think this is a security issue because this behaviour is in contradiction 
with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and 
typing to the wrong place can lead to all sorts of errors

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

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

[Desktop-packages] [Bug 1857122] Re: New Windows are opened below other windows and require extra clicks to acees

[Daniel van Vugt]

This sounds like a feature usually called "focus-stealing prevention". I
don't know how it's exactly implemented in Gnome Shell but you should
report it to the Gnome developers to get their opinion first:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and then tell us the new issue ID.

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

Title:
  New Windows are opened below other windows and require extra clicks to
  acees

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when opening new windows the new window is opened below
  other windows.

  This behaviour is not consistent. Sometimes it happens and sometimes
  it does not happen. This is rather unpredictable and very frustrating.

  The problem got horribly worde when moving to a fast computer running
  Ubuntu 19.10

  This behaviour causes typing to go to the wrong window so sometimes when I 
already start typing expected entry just to discover the actual window I am 
expecting is hidden and the actual typing goes to the wrong place.
  This can easily lead to revealing of sensitive information therefore IMHO it 
should be treated as a security issue.
  I think this is a security issue because this behaviour is in contradiction 
with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and 
typing to the wrong place can lead to all sorts of errors

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

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

[Desktop-packages] [Bug 1861905] Re: New terminal windows appear in the background

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1857122
   New Windows are opened below other windows and require extra clicks to acees

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

Title:
  New terminal windows appear in the background

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu release: 20.04 Focal Fossa
  Package version: gnome-shell 3.34.3-1ubuntu1, firefox 72.0.2+build1-0ubuntu1

  Expected Behavior: new Terminal window would be foregrounded/focused
  on creation via ctrl-alt-t when another terminal window not already
  focused

  Actual Behavior: if Firefox, e.g., is currently selected/focused,
  ctrl-alt-t produces a Terminal window that is backgrounded (usually
  behind the Firefox window), along with a pop-up desktop notification
  stating "Terminal is ready".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1)
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  4 09:19:33 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-29-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070] [3842:6173]
  InstallationDate: Installed on 2018-09-26 (495 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=75a21605-578a-4b4b-ac2e-14e6aa2f5b02 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0505
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS IX CODE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/08/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXCODE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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/gnome-shell/+bug/1861905/+subscriptions

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

[Desktop-packages] [Bug 1857122] Re: New Windows are opened below other windows and require extra clicks to acees

[Launchpad Bug Tracker]

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

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

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

Title:
  New Windows are opened below other windows and require extra clicks to
  acees

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when opening new windows the new window is opened below
  other windows.

  This behaviour is not consistent. Sometimes it happens and sometimes
  it does not happen. This is rather unpredictable and very frustrating.

  The problem got horribly worde when moving to a fast computer running
  Ubuntu 19.10

  This behaviour causes typing to go to the wrong window so sometimes when I 
already start typing expected entry just to discover the actual window I am 
expecting is hidden and the actual typing goes to the wrong place.
  This can easily lead to revealing of sensitive information therefore IMHO it 
should be treated as a security issue.
  I think this is a security issue because this behaviour is in contradiction 
with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and 
typing to the wrong place can lead to all sorts of errors

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

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

[Desktop-packages] [Bug 1856884] Re: not proper sound device

[Daniel van Vugt]

Since you have updated now, could you please re-run:

  apport-collect 1856884

** This bug is no longer a duplicate of bug 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  not proper sound device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  when i insert or take out my headphones , the system doesn't send signal on 
my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob1929 F pulseaudio
   /dev/snd/controlC1:  rob1929 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-01-26 (326 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: AB350 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

[Daniel van Vugt]

I know, I've asked for an update just now. Tracking more generally in:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bugs?field.tag=update-reverted

** Tags added: update-reverted

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

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

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

[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

[Daniel van Vugt]

Ivan,

Please open a new bug by running:

  ubuntu-bug linux

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "apt-cache policy linux-firmware" reports the following:
  ```
  linux-firmware:
Installed: 1.178.1
Candidate: 1.178.1
Version table:
   *** 1.178.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2314 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 12:31:07 2019
  InstallationDate: Installed on 2019-06-02 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 003: ID 5986:066d Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: PC Specialist Limited N15_17RD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N15_17RD
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N15_17RD
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1725180] Re: Shell animations are not smooth

[Daniel van Vugt]

Don't panic, those are just tags. The full set of fixes detailed in
comment #12 ARE expected to be released in Ubuntu 20.04.

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

Title:
  Shell animations are not smooth

Status in gjs:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Upstream fixes required to make all the overview/window/icon
  animations much smoother (at least halving render times):

  https://gitlab.gnome.org/GNOME/gjs/merge_requests/390
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1002

  __

  +++UBUNTU RELEASE+++

  Description:  Ubuntu 17.10
  Release:  17.10

  +++PACKAGE VERSION+++

  xwayland:
    Installed: 2:1.19.5-0ubuntu2
    Candidate: 2:1.19.5-0ubuntu2
    Version table:
   *** 2:1.19.5-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630.
  Currently using Intel HD Graphics 630 as Nvidia seems to have no
  support for xwayland.

  The window/dock/launcher animations are lagging/shaky (not smooth).

  __

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 19:09:27 2017
  DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07be]
     Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-05-24 (149 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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/gjs/+bug/1725180/+subscriptions

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

[Desktop-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Daniel van Vugt]

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/issues/1377
   Importance: Unknown
   Status: Unknown

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in Linux:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-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/linux/+bug/1767654/+subscriptions

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

[Desktop-packages] [Bug 1862087] Re: High RSS useage for gnome-software background process

[Robert Ancell]

I found a leak in snapd-glib, which is fixed in snapd-glib 1.56. It's
not clear to me how to read the heaptrack data, as that leak doesn't
look significant to me there. Perhaps try again with updated focal to
see if there's any significant difference?

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

Title:
  High RSS useage for gnome-software background process

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I've had an uptime of slightly in excess of 2 days, and the gnome-
  software --gapplication-service process is using 700M RSS (3GiB Virt,
  ~50MB SHR).

  This seems excessive. I'll try running under heaptrack to see if
  there's any obvious slow leaks.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200129.3826d9e0-1.1-generic 
5.3.13
  Uname: Linux 5.3.0+bcachefs.git20200129.3826d9e0-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 10:49:40 2020
  InstallationDate: Installed on 2019-08-29 (160 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.35.2-0ubuntu1
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-20 (16 days ago)

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

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

[Desktop-packages] [Bug 1867067] [NEW] ERROR context deadline exceeded

[Alan Pope  濾]

Public bug reported:

( Oddly, "ubuntu-bug zsys" didn't work, I clicked send and nothing
happened )

When I install new packages, or do significant updates on my laptop, I
often see the following error.

ERROR context deadline exceeded

This usually happens after "Saving system state" then a pause of some
seconds.

This feels like a bad thing?

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

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

Title:
  ERROR context deadline exceeded

Status in zsys package in Ubuntu:
  New

Bug description:
  ( Oddly, "ubuntu-bug zsys" didn't work, I clicked send and nothing
  happened )

  When I install new packages, or do significant updates on my laptop, I
  often see the following error.

  ERROR context deadline exceeded

  This usually happens after "Saving system state" then a pause of some
  seconds.

  This feels like a bad thing?

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

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

[Desktop-packages] [Bug 1867066] [NEW] tuoshpad issues

[stanislav kralik]

Public bug reported:

Good evening all
I just change the laptop from lenovo to dell and can not find out how make work 
the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and 
an external mouse neither. The bluetooth will never work again untill 
re-installing an OS from micro-horror-soft, switching up the bluetooth module 
and re-installing ubuntu back. But I still love Linux ! I will appreciate if 
you help me, in the meantime i keep searching by myself in the ubuntu's forum 
how to fix my issues.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 23:49:44 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e]
InstallationDate: Installed on 2020-03-06 (5 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. XPS M1530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash 
acpi_osi=!Windows 2012 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0D501F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1530
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1867066

Title:
  tuoshpad issues

Status in xorg package in Ubuntu:
  New

Bug description:
  Good evening all
  I just change the laptop from lenovo to dell and can not find out how make 
work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button 
and an external mouse neither. The bluetooth will never work again untill 
re-installing an OS from micro-horror-soft, switching up the bluetooth module 
and re-installing ubuntu back. But I still love Linux ! I will appreciate if 
you help me, in the meantime i keep searching by myself in the ubuntu's forum 
how to fix my issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a 

[Desktop-packages] [Bug 1867064] Re: Close buttons not rendering correctly

[Paul White]

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

** This bug has been marked a duplicate of bug 1861558
   Snap 'ed applicaitons have garbage on top of the window Close [x] button

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

Title:
  Close buttons not rendering correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not gonna lie, I'm not sure if this is the correct place to report
  this or not. In the Pick and Calculator Snaps, I noticed the close
  button is rendering incorrectly. I looked online and saw someone else
  is having the issue too and decided to report it. I haven't noticed it
  in any other applications. Nothing major, but worth submitting
  somewhere.

  Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

  Here is the link to the other person's Reddit post:
  https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 11 16:40:44 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
   Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. USB Gaming 
Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3ef07817-9408-490b-b7db-828fbd280f54 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0410
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1867064] [NEW] Close buttons not rendering correctly

[Phillip Prado]

Public bug reported:

I'm not gonna lie, I'm not sure if this is the correct place to report
this or not. In the Pick and Calculator Snaps, I noticed the close
button is rendering incorrectly. I looked online and saw someone else is
having the issue too and decided to report it. I haven't noticed it in
any other applications. Nothing major, but worth submitting somewhere.

Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

Here is the link to the other person's Reddit post:
https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Mar 11 16:40:44 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
 Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc. USB Gaming Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=3ef07817-9408-490b-b7db-828fbd280f54 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0410
dmi.board.asset.tag: Default string
dmi.board.name: Z170M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
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

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


** Tags: amd64 apport-bug eoan 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/1867064

Title:
  Close buttons not rendering correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not gonna lie, I'm not sure if this is the correct place to report
  this or not. In the Pick and Calculator Snaps, I noticed the close
  button is rendering incorrectly. I looked online and saw someone else
  is having the issue too and decided to report it. I haven't noticed it
  in any other applications. Nothing major, but worth submitting
  somewhere.

  Here is a screenshot of what I see: https://imgur.com/a/70IcsU6

  Here is the link to the other person's Reddit post:
  https://www.reddit.com/r/gnome/comments/ervfbz/strange_close_button/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 11 16:40:44 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon 

[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it

[Launchpad Bug Tracker]

This bug was fixed in the package yaru-theme - 19.10.5

---
yaru-theme (19.10.5) eoan; urgency=medium

  * gnome-shell: Sync with 3.34.2 changes (LP: #1857037)
  * debian/gbp.conf: Target ubuntu/eoan branch

 -- Marco Trevisan (Treviño)   Wed, 08 Jan 2020
13:54:22 +

** Changed in: yaru-theme (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  Fix Released

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1857037] Update Released

[Brian Murray]

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

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1850267] Update Released

[Brian Murray]

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

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

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

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

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  

[Desktop-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Desktop-packages] [Bug 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.10.6-2ubuntu1.4

---
network-manager (1.10.6-2ubuntu1.4) bionic; urgency=medium

  * d/p/start-ip-conf-when-master-carrier-goes-up.patch: device: start IP
configuration when master carrier goes up (LP: #1794478)

network-manager (1.10.6-2ubuntu1.3) bionic; urgency=medium

  * d/t/control: nm test requires dnsmasq-base (LP: #1850267)
  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)

 -- Seyeong Kim   Wed, 19 Feb 2020 14:59:10
+0900

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

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

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

[Desktop-packages] [Bug 1794478] Update Released

[Brian Murray]

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

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as 
original description.
  2. ipv6 manual, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses 
fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##
  3. ipv6 auto, ipv4 auto
  ##
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, 
miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, 
updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can 

[Desktop-packages] [Bug 1866995] Re: XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

[Stephen Allen]

I just noticed that GDM hasn't been updated to 3.26, so this shouldn't
be reported yet as the new gnome packages haven't obviously been
released yet. So pardon the interruption.

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

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Stephen Allen (stephen-d-allen)

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

Title:
  XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  The cursor is there, just invisible. If one moves the mouse around one
  can see that it's there, but not visible. Tested in both Ubuntu
  XWayland session and Gnome Vanillia session. It's working OK in Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 08:24:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-xanmod6 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1867017] Re: Cursor Invisible, but there.

[Stephen Allen]

I just noticed that GDM hasn't been updated to 3.26, so this shouldn't
be reported yet as the new gnome packages haven't obviously been
released yet. So pardon the interruption.

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

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Stephen Allen (stephen-d-allen)

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

Title:
  Cursor Invisible, but there.

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  Further to my previous bug for XWayland same issue. I should probably
  note that this isn't a clean install but an upgrade from 19.10 on bare
  metal. HTH.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:37:49 2020
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1726402] Re: No Google Chrome icons in top bar

[Roberto Leinardi]

#8 same issue here on Ubuntu 19.10.

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

Title:
  No Google Chrome icons in top bar

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

Bug description:
  After upgrade to 17.10, the Google Chrome and Hangouts icons that were
  previously in my top bar are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 09:26:48 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 1801757] Re: all app indicators disappear

[Jonathan Kamens]

If I restart gnome shell, most of the app indicators remain, but the
Google Chrome and Hangouts appindicators disappear.

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

Title:
  all app indicators disappear

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  Occasionally all of my app indicators just disappear. Right now, for
  example the only icons in my top bar are the wifi icon, the volume
  icon, and the battery charge icon. Everything else is gone. The
  applications associated with the missing indicators, e.g., Dropbox,
  Cloud Station Drive, Pritunl, Shutter, are still running, but their
  app indicators are no longer there.

  The only way I've found to get them back is to log out and log back
  in.

  I have no idea what provokes this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 11:37:47 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1726402] Re: No Google Chrome icons in top bar

[Jonathan Kamens]

Well, more accurately, I _sometimes_ see it in Focal. The icons in the
top bar come and go seemingly at random i.e. I can't currently identify
what makes them disappear.

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

Title:
  No Google Chrome icons in top bar

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

Bug description:
  After upgrade to 17.10, the Google Chrome and Hangouts icons that were
  previously in my top bar are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 09:26:48 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 1726402] Re: No Google Chrome icons in top bar

[Jonathan Kamens]

I still see it in current Focal.

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

Title:
  No Google Chrome icons in top bar

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

Bug description:
  After upgrade to 17.10, the Google Chrome and Hangouts icons that were
  previously in my top bar are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 09:26:48 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 1801757] Re: all app indicators disappear

[Treviño]

This should have been fixed by appindicator 32-1, let me know if this is
not the case

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  all app indicators disappear

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  Occasionally all of my app indicators just disappear. Right now, for
  example the only icons in my top bar are the wifi icon, the volume
  icon, and the battery charge icon. Everything else is gone. The
  applications associated with the missing indicators, e.g., Dropbox,
  Cloud Station Drive, Pritunl, Shutter, are still running, but their
  app indicators are no longer there.

  The only way I've found to get them back is to log out and log back
  in.

  I have no idea what provokes this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 11:37:47 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712532] Re: Dropbox und Gome-Encfs-Manger Icon not visible

[Treviño]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Dropbox und Gome-Encfs-Manger Icon not visible

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  Both programs are only visible when I add dbus-launch to the .desktop
  file.

  http://www.webupd8.org/2016/06/fix-dropbox-indicator-icon-and-menu-
  not.html

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

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

[Desktop-packages] [Bug 1726402] Re: No Google Chrome icons in top bar

[Treviño]

This should be fixed by now, no?

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

Title:
  No Google Chrome icons in top bar

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

Bug description:
  After upgrade to 17.10, the Google Chrome and Hangouts icons that were
  previously in my top bar are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 09:26:48 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago)

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

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

[Desktop-packages] [Bug 1740600] Re: Certain app indicators dissappear after laptop hibernates

[Treviño]

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

** This bug has been marked a duplicate of bug 1801757
   all app indicators disappear

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

Title:
  Certain app indicators dissappear after laptop hibernates

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

Bug description:
  Particularly the application indicators for Skype and Slack disappear
  after my laptop hibernates.  There does not appear to be anyway to
  bring them back unless I restart the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10.3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 10:38:57 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-10-11 (80 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-11-09 (50 days ago)

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

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

[Desktop-packages] [Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width

[Treviño]

While I suggest you to use syspeek (as it causes the shell not to use as
much CPU as indicator-multiload), this is now fixed by version 32-1

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: indicator-multiload
   Status: New => Invalid

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

Title:
  Aardvark Daily: Indicator-Multiload doesn't show full-width

Status in System Load Indicator:
  Invalid
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu Indicator-Multiload is an essential application as it shows
  that computer is actually doing something even when an application is
  giving no feedback for a long period of time. Conky is not an option
  as it gets hidden behind full screen applications.

  Unfortunately the move to Gnome has broken indicator-multiload so that it 
can't show all of the indicators.
  CPU
  Memory
  Network
  Swap
  System Load
  Disk

  I've tried the developers suggestion of installing TopIcons and
  TopIconsplus to no avail. I see that Ubuntu App-Indicator is also
  installed so maybe app-indicator extension is broken in Gnome and not
  indicator-multiload.

  Anyway steps to reproduce:
  Install Ubuntu 16.04.x LTS
  Install indicator-multiload
  Open the settings of indicator-multiload by clicking on it and choosing 
settings
  Click all of the sources on
  You will now see 6 panels showing the earlier described graphs.

  Now install Ubuntu 17.10 Daily
  Install indicator-multiload
  Mouse over the top bar to faintly get an idea where indicator-multiload is 
running
  click on it and open the settings
  Click all of the sources on
  You will now see tiny faint lines which give no clue whatsoever as to what is 
going on with the machine.

  Please fix either app-indicator extension or indicator-multiload to
  work with Gnome. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: indicator-multiload 0.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 19:12:33 2017
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-multiload
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions

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

[Desktop-packages] [Bug 1866042] Re: AppIndicator labels are not centered vertically

[Treviño]

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  AppIndicator labels are not centered vertically

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress

Bug description:
  After a recent gnome-shell + yaru-theme update, AppIndicator labels
  are now shown aligned with the top of the top bar instead of aligned
  vertically centered as previously https://imgur.com/a/jKVP5w9

  (This is the indicator-sensors snap, which creates an AppIndicator
  with a label as per https://github.com/alexmurray/indicator-
  sensors/blob/master/indicator-sensors/is-indicator.c#L211)

  Whilst this only became evident after the most recent gnome-shell
  upgrade it is not clear to me which package this should be filed
  against, and so am filing it against the appindicator extension
  initially as directed by Laney in #ubuntu-desktop :)

  Let me know if there is anything I can do to help debug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 32-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 21:26:31 2020
  InstallationDate: Installed on 2019-11-18 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to focal on 2020-01-22 (42 days ago)

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

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

[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

[Bill Miller]

Still stuck on version 7.5 3 months later.

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

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

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

[Desktop-packages] [Bug 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered

[Treviño]

This has been fixed upstream v32 version and released in ubuntu with
version 32-1

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Repeated [AppIndicatorSupport-WARN] Item
  :1.51/org/ayatana/NotificationItem/multiload is already registered

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in indicator-multiload package in Ubuntu:
  Confirmed

Bug description:
  The following message is continuously logged to /var/log/syslog (every
  few seconds):

  Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] 
Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; 
resetting instead
  Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item 
:1.51/org/ayatana/NotificationItem/multiload is already registered


  It's hard to find anything in syslog because thousands of these
  messages intermingle with everything else

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 20 10:28:49 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-13 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1525628] Re: tracker needs to be killed on every boot

[Felix Köhler]

Just to confirm: this is still very relevant in 2020 :-(

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

Title:
  tracker needs to be killed on every boot

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  At every boot, tacker-miner-fs and tracker-extract uses all of the
  processor and needs to be killed manually for computer to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: tracker 1.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 13 13:02:58 2015
  InstallationDate: Installed on 2015-04-24 (232 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: tracker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)

[Brian Murray]

** Tags added: focal

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

Title:
  usb_modeswitch does not switch modems (remain visible as mass storage)

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

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

[Desktop-packages] [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

[Christoph Reiter]

"int" maps to the same underlying type in Python 2 and Python 3. This
wasn't changed when pygobject was ported to Python 3 and can't really be
changed now. If you want be sure your numbers fit use the suggested
"GObject.TYPE_*", or just use "object" which means the Python int object
is stored as is, assuming you don't need to access it in C code
somewhere else.

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

Status in pygobject package in Ubuntu:
  New

Bug description:
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk

  This works in Python 2:

  mystore = Gtk.ListStore(long)
  mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])

  This does not work in Python 3:

  mystore = Gtk.ListStore(int)
  mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

  OverflowError: Item 0: out of range for int property

  

  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  apt-cache policy python3-gi
  python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
   *** 3.26.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  python3 -V
  Python 3.6.9

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

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

[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount")

[Pablo Copissa]

Reported upstream as issue 2062
(https://gitlab.gnome.org/GNOME/glib/issues/2062)

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

** Description changed:

+ Reported upstream as issue 2062
+ (https://gitlab.gnome.org/GNOME/glib/issues/2062)
+ 
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share
  
  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s
  
  Enumeration of files is about 29 times slower when mounted via gio mount
  than via mount -t cifs.
  
  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804
  
  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s
  
  Note that this is almost TWICE AS FAST than the "fast" mount of test #1
  and about 53 times faster than "slow" test #2 !
  
  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They use
  the same underlying infrastructure which test 3 proves is adequately
  fast. And yet, we get this slow down in test 2.
  
  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.
  
  Hope this helps
  
  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)
  
  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).
  
  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)
  
  $ gio mount smb://nas.example.com/share2
  
  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path
  
  $ time ls
  
  ... 528 subdirs approximately ...
  
  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s
  
  $ time ls | wc
- 5281631   10893
+ 5281631   10893
  
  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s
  
  Factor is about 50.

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Reported upstream as issue 2062
  (https://gitlab.gnome.org/GNOME/glib/issues/2062)

  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating 

[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

[Nicolás Abel Carbone]

I tried that to no avail. I don't see any event at all on gnome-calendar 
despite having many in my google account.
I also tried logout and then login on Online Accounts in gnome-settings, but 
calendar is still empty.

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Anatoly]

i'm sure an easier workaround is to (temporarily) use firefox for this.
i use this one when i need to open some tg:// links in telegram app

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

[Paul White]

I'm not seeing that problem here as an item that I changed elsewhere
earlier today does show in its revised form in gnome-calendar.

Does "Synchronise Calendars" on the "Manage on your calendars" menu help
to resolve the issue?

FWIW, while composing this reply I changed an item in Google Calendar,
clicked on "Synchronize Calendars" and the amended details were
displayed immediately.

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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

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

[Desktop-packages] [Bug 1867024] [NEW] Keyboard shortcuts not responding for sound.

[Rishabh]

Public bug reported:

My keyboard sound controls are not working.To adjust sound ,everytime i
have to open alsamixer from terminal.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1.3
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 12:03:49 2020
InstallationDate: Installed on 2020-03-10 (1 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Keyboard shortcuts not responding for sound.

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  My keyboard sound controls are not working.To adjust sound ,everytime
  i have to open alsamixer from terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.1-0ubuntu1.3
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 12:03:49 2020
  InstallationDate: Installed on 2020-03-10 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1867017] [NEW] Cursor Invisible, but there.

[Stephen Allen]

Public bug reported:

Further to my previous bug for XWayland same issue. I should probably
note that this isn't a clean install but an upgrade from 19.10 on bare
metal. HTH.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 11:37:49 2020
InstallationDate: Installed on 2019-02-23 (381 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cursor Invisible, but there.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Further to my previous bug for XWayland same issue. I should probably
  note that this isn't a clean install but an upgrade from 19.10 on bare
  metal. HTH.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:37:49 2020
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)

[Eduardo Aguilar Pelaez]

Hi Marc,

Thank you very much for your quick response!

Eduardo

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

Title:
  Snap Store can't install or remove snaps on 20.04 (password prompt
  issue?)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04 the older App store disappeared and the Snap Store 
appeared. 
  However this version of the snap store can't seem to install or remove any 
snaps. 
  This seems to be due to a broken step in the user password prompt pop up. 
  Because the password prompt does not come up the Snap Store does not have the 
necessary permissions to add or remove snaps.

  When I try this in the terminal I need to use sudo

  > edu@Edu-laptop:~$ snap remove gitkraken 
  > error: access denied (try with sudo)
  > edu@Edu-laptop:~$ sudo snap remove gitkraken 
  > [sudo] password for edu: 
  > gitkraken removed
  > edu@Edu-laptop:~$ 

  However as soon as I typed the password and pressed enter the screen flashed 
and my Brave browser session was killed. 
  - This seems to be an issue with many instances when the user's password is 
requested. 

  Asking for the user's password should not kill apps or the session.
  This might be related to the screen lock issue (
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866888 ).

  Since this is related to user password management I'm flagging it as
  security related, feel free to downgrade if no risk is present.

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

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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Jesse Glick]

How I managed to work around this to add a new Slack workspace:

* Click the + button in the desktop app. This opens 
https://app.slack.com/ssb/add?… in Chromium.
* Press F12 to get the Network tab. Make sure *Preserve Log* is checked.
* Type in the workspace URL and hit Enter.
* When prompted to run `xdg-open`, accept it. Nothing will happen.
* Look in the request *Name* column for the red request starting with 
`slack://` in the full URL displayed in the hover tip.
* Right-click to *Copy » Copy link address*.
* From a terminal window, type `xdg-open `, paste the link, and Enter

For Zoom it is usually less cumbersome since you can just open the Zoom
app manually and copy and paste the meeting ID from the URL displayed in
the browser, though this does not seem to work in all cases.

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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

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

[Desktop-packages] [Bug 1867001] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

Thanks for your report!

Can you please clarify which steps preceded the crash?

I see that the current desktop is "GNOME-Greeter:GNOME", while standard
Ubuntu is "ubuntu:GNOME". Which desktop environment are you using?

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

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  the Ubuntu presents an error

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-1~exp1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Mar 11 08:51:28 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2020-03-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fab42711b86) ok
   source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
   _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Desktop-packages] [Bug 1867001] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  New

Bug description:
  the Ubuntu presents an error

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-1~exp1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Mar 11 08:51:28 2020
  ExecutablePath: /usr/lib/ibus/ibus-x11
  InstallationDate: Installed on 2020-03-07 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
  ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fab42711b86) ok
   source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
   xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1
   _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Desktop-packages] [Bug 1854120] Re: Screen contents visible briefly on lock screen on resolution change

[Marc Deslauriers]

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

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

Title:
  Screen contents visible briefly on lock screen on resolution change

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  I am using a remote application to AnyDesk to remote access my Ubuntu
  16.04 LTS 64 bit. On the application we can resize the screen and have
  the resolution of the target computer scale up and down when this is
  done.

  When the computer is locked on the login screen if the screen is
  resized ( resolution changes ) - For a brief fraction of a second the
  unlocked screen flashes and the login screen shows up again. I think
  this is a security breach to be able to peek into the inside contents
  even though the computer is locked.

  Please feel free to close this issue if this is an already known issue
  or if its already fixed in later releases.

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

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

[Desktop-packages] [Bug 1857122] Re: New Windows are opened below other windows and require extra clicks to acees

[Marc Deslauriers]

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

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

Title:
  New Windows are opened below other windows and require extra clicks to
  acees

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Sometimes when opening new windows the new window is opened below
  other windows.

  This behaviour is not consistent. Sometimes it happens and sometimes
  it does not happen. This is rather unpredictable and very frustrating.

  The problem got horribly worde when moving to a fast computer running
  Ubuntu 19.10

  This behaviour causes typing to go to the wrong window so sometimes when I 
already start typing expected entry just to discover the actual window I am 
expecting is hidden and the actual typing goes to the wrong place.
  This can easily lead to revealing of sensitive information therefore IMHO it 
should be treated as a security issue.
  I think this is a security issue because this behaviour is in contradiction 
with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and 
typing to the wrong place can lead to all sorts of errors

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

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

[Desktop-packages] [Bug 1857122] [NEW] New Windows are opened below other windows and require extra clicks to acees

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Sometimes when opening new windows the new window is opened below other
windows.

This behaviour is not consistent. Sometimes it happens and sometimes it
does not happen. This is rather unpredictable and very frustrating.

The problem got horribly worde when moving to a fast computer running
Ubuntu 19.10

This behaviour causes typing to go to the wrong window so sometimes when I 
already start typing expected entry just to discover the actual window I am 
expecting is hidden and the actual typing goes to the wrong place.
This can easily lead to revealing of sensitive information therefore IMHO it 
should be treated as a security issue.
I think this is a security issue because this behaviour is in contradiction 
with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and 
typing to the wrong place can lead to all sorts of errors

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


** Tags: eoan ui
-- 
New Windows are opened below other windows and require extra clicks to acees
https://bugs.launchpad.net/bugs/1857122
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 1864948] Re: circumflex accent in a password is not hidden properly

[Marc Deslauriers]

** 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 gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1864948

Title:
  circumflex accent in a password is not hidden properly

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  The circumflex accent ^ in a password on azerty keyboard leads to the
  character being displayed transparently on screen. It happens in
  gnome-terminal but also on the user login screen.

  What is expected to happen:
  the character ^ is hidden properly 

  What actually happened:
  pressing the ^ key once displays the character, pressing it twice displays a 
dot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-terminal 3.34.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 22:08:58 2020
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2016-08-28 (1277 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to eoan on 2020-02-05 (21 days ago)

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

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

[Desktop-packages] [Bug 1865831] Re: bug

[Marc Deslauriers]

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

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  bugbugbugb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 11:05:07 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:062e]
  InstallationDate: Installed on 2020-02-26 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=bf009119-6b69-4fe9-a305-709e07c8e9fe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D8H72
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.sku: 062E
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Marc Deslauriers]

What desktop environment are you using?

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

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

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

[Desktop-packages] [Bug 1866999] [NEW] gnome-calendar does not sync with Google Calendar

[Nicolás Abel Carbone]

Public bug reported:

Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-calendar 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 09:47:25 2020
InstallationDate: Installed on 2018-02-23 (746 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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


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

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

Title:
  gnome-calendar does not sync with Google Calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my 
Google Calendar.
  Online accounts is activated and, for example, gnome-contacts does show the 
contacts I have in Google.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-calendar 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 09:47:25 2020
  InstallationDate: Installed on 2018-02-23 (746 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gnome-calendar
  UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago)

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

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

[Desktop-packages] [Bug 1866899] Re: Snap Store can't install or remove snaps on 20.04 (password prompt issue?)

[Marc Deslauriers]

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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1866899

Title:
  Snap Store can't install or remove snaps on 20.04 (password prompt
  issue?)

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to 20.04 the older App store disappeared and the Snap Store 
appeared. 
  However this version of the snap store can't seem to install or remove any 
snaps. 
  This seems to be due to a broken step in the user password prompt pop up. 
  Because the password prompt does not come up the Snap Store does not have the 
necessary permissions to add or remove snaps.

  When I try this in the terminal I need to use sudo

  > edu@Edu-laptop:~$ snap remove gitkraken 
  > error: access denied (try with sudo)
  > edu@Edu-laptop:~$ sudo snap remove gitkraken 
  > [sudo] password for edu: 
  > gitkraken removed
  > edu@Edu-laptop:~$ 

  However as soon as I typed the password and pressed enter the screen flashed 
and my Brave browser session was killed. 
  - This seems to be an issue with many instances when the user's password is 
requested. 

  Asking for the user's password should not kill apps or the session.
  This might be related to the screen lock issue (
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866888 ).

  Since this is related to user password management I'm flagging it as
  security related, feel free to downgrade if no risk is present.

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

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

[Desktop-packages] [Bug 1866995] [NEW] XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

[Stephen Allen]

Public bug reported:

The cursor is there, just invisible. If one moves the mouse around one
can see that it's there, but not visible. Tested in both Ubuntu XWayland
session and Gnome Vanillia session. It's working OK in Xorg.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland 2:1.20.7-2ubuntu2
Uname: Linux 5.5.8-xanmod6 x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 11 08:24:26 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 
OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
   Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
InstallationDate: Installed on 2019-02-23 (381 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.8-xanmod6 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal reproducible single-occurrence ubuntu

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

Title:
  XWayland both Gnome-Session and/or Ubuntu Session No Cursor Available

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The cursor is there, just invisible. If one moves the mouse around one
  can see that it's there, but not visible. Tested in both Ubuntu
  XWayland session and Gnome Vanillia session. It's working OK in Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.7-2ubuntu2
  Uname: Linux 5.5.8-xanmod6 x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 08:24:26 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 20.02.00, 5.4.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms, 20.02.00, 5.5.8-xanmod6, x86_64: installed (WARNING! 
Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (rev 81) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [148c:2356]
  InstallationDate: Installed on 2019-02-23 (381 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: 

[Desktop-packages] [Bug 1866900] Re: Javascript clipboard does not work

[Rik Mills]

I just tried this on a fully up to date install of Kubuntu focal 20.04,
using the exact example link give in comment 3 and same firefox build.

Firefox successfully copied the repo clone link to the clipboard under
KDE.

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

Title:
  Javascript clipboard does not work

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Pressing the "copy to clipboard" buttons on websites does not work. (e. g. 
Gitlab / Github)
  Manual ctrl-c is necessary.
  (Wrorks in several other browsers on same system) 

  Snap / connection ?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 74.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anders 2056 F pulseaudio
   /dev/snd/controlC0:  anders 2056 F pulseaudio
  BuildID: 20200309095159
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 19:45:10 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:729
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-03-03 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:729
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=74.0/20200304223017 (Out of date)
   Profile0 - LastVersion=74.0/20200309095159 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I1KT24AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10120
  dmi.product.sku: LENOVO_MT_1012
  dmi.product.version: IdeaCentre K450
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1866982] [NEW] xfce4-screensaver is triggering a Xorg crash, backtrace suggests a xserver-xorg-video-intel problem

[Leonardo Müller]

Public bug reported:

xfce4-screensaver is triggering a Xorg crash. The bug report I did on
xfce bugzilla against xfce4-screensaver is:
https://bugzilla.xfce.org/show_bug.cgi?id=16528

The bug report there have the steps to reproduce, log files and the full
backtrace of Xorg when the crash happened.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
Uname: Linux 5.6.0-050600rc4-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
BootLog:
 
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Mar 11 07:34:32 2020
DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
InstallationDate: Installed on 2017-06-13 (1001 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 0cf3:e360 Qualcomm Atheros Communications 
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. EasyCamera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80UG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-050600rc4-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to focal on 2019-12-22 (79 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal regression reproducible ubuntu

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

Title:
  xfce4-screensaver is triggering a Xorg crash, backtrace suggests a
  xserver-xorg-video-intel problem

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  xfce4-screensaver is triggering a Xorg crash. The bug report I did on
  xfce bugzilla against xfce4-screensaver is:
  https://bugzilla.xfce.org/show_bug.cgi?id=16528

  The bug report there have the steps to reproduce, log files and the
  full backtrace of Xorg when the crash happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
  Uname: Linux 5.6.0-050600rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Mar 11 07:34:32 2020
  DistUpgraded: 2019-12-22 18:50:28,852 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822]
  InstallationDate: Installed on 2017-06-13 (1001 days ago)
  InstallationMedia: Xubuntu 

[Desktop-packages] [Bug 1866900] Re: Javascript clipboard does not work

[Anders Magnus Andersen]

I'm, sorry I assumed it was a snap, its the deb:

i.e. https://github.com/micheleg/gnome-shell-extension-cpu-freq

Push Clone or download, and then the clipboard button, now try and paste
it in a terminal (or somewhere else.


Package: firefox
Version: 74.0+build3-0ubuntu1
Priority: optional
Section: web
Origin: Ubuntu
Maintainer: Ubuntu Mozilla Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 201 MB
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.30), 
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14), 
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12.6), libfreetype6 (>= 
2.10.1), libgcc-s1 (>= 3.3), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 
2.31.8), libgtk-3-0 (>= 3.4), libharfbuzz0b (>= 0.6.0), libpango-1.0-0 (>= 
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), 
libstdc++6 (>= 9), libx11-6, libx11-xcb1 (>= 2:1.6.9), libxcb-shm0, libxcb1, 
libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), 
libxext6, libxfixes3, libxi6, libxrender1, libxt6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Replaces: kubuntu-firefox-installer
Task: ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, kubuntu-full, 
xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop, 
ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
Supported: 9m
Download-Size: 51,6 MB
APT-Manual-Installed: no
APT-Sources: http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
Description: Safe and easy web browser from Mozilla
 Firefox delivers safe, easy web browsing. A familiar user interface,
 enhanced security features including protection from online identity theft,
 and integrated search let you get the most out of the web.

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

Title:
  Javascript clipboard does not work

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Pressing the "copy to clipboard" buttons on websites does not work. (e. g. 
Gitlab / Github)
  Manual ctrl-c is necessary.
  (Wrorks in several other browsers on same system) 

  Snap / connection ?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 74.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anders 2056 F pulseaudio
   /dev/snd/controlC0:  anders 2056 F pulseaudio
  BuildID: 20200309095159
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 19:45:10 2020
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:729
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-03-03 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:729
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=74.0/20200304223017 (Out of date)
   Profile0 - LastVersion=74.0/20200309095159 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I1KT24AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10120
  dmi.product.sku: LENOVO_MT_1012
  dmi.product.version: IdeaCentre K450
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

[Jamie Bainbridge]

After happening every day for a week, this hasn't happened again since I
logged this bug.

I also disabled Firefox WebRender so maybe that was a contributor.

I'll re-open if I can provide any useful data.

** Changed in: xserver-xorg-video-ati (Ubuntu)
   Status: New => Incomplete

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

Title:
  GPU lockup ring 0 stalled for more than X msec

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

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 [radeon]
do_vfs_ioctl+0xa9/0x640
? __schedule+0x2b0/0x670
ksys_ioctl+0x75/0x80
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x130
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
  ppa but that made no difference. It appears to be a bug in radeon.

  Nothing specific makes this happen, just regular usage with a
  compositing window manager. I'm not playing games or particularly
  exercising the GPU. The last two times I was just reading in web
  browser. It's also happened in the middle of the night while I was
  asleep. Sometimes I have a few days uptime, sometimes it happens in
  less than 24 hours from boot.

  This never happened before the radeon update mentioned on the first
  line.

  I'll attach two files of dmesg output. As per
  https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
  started apport for next time it happens.

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

-- 

[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)

[Lars Melin]

There is no SCSI attribute named ref but there is one named rev.

This is likely to be a typo from ubuntu rewrite of the original
usb_modeswitch_dispatcher.tcl which reads the rev attribute.

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

Title:
  usb_modeswitch does not switch modems (remain visible as mass storage)

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Timo Aaltonen]

** Description changed:

+ [Impact]
+ 
+ From the original bug:
+ 
+ "The result is that on my Yoga 920, in a plain X11 session (running
+ openbox in my case), the touchscreen acts like a broken mouse: there is
+ no multi-touch capability in Qt Quick applications, and clicking isn't
+ quite right either."
+ 
+ [Test case]
+ 
+ Install the update, note that the touchscreen behaviour is better.
+ 
+ [Regression potential]
+ 
+ From the upstream commit:
+ 
+ "Note that this change will effectively cause a feature regression for
+ users of other environments that do *not* have their own gesture
+ engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an
+ xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the
+ functionality."
+ 
+ but at least I (tjaalton) haven't heard of any complaints since we've
+ disabled gestures in focal (Nov 21st), so the warning might be a bit too
+ pessimistic about the impact.
+ 
+ 
+ --
+ 
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:
  
  Section "InputClass"
- Identifier "Wacom touchscreen class"
- MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
- MatchDevicePath "/dev/input/event*"
- MatchIsTouchscreen "true"
- Driver "wacom"
+ Identifier "Wacom touchscreen class"
+ MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+ MatchDevicePath "/dev/input/event*"
+ MatchIsTouchscreen "true"
+ Driver "wacom"
  EndSection
  
  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there is
  no multi-touch capability in Qt Quick applications, and clicking isn't
  quite right either.  I also verified it with Peter Hutterer's old cairo-
  based mt-touch test program.
  
  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)
  
  Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically
  been only for Wacom tablets and in-screen stylus digitizers, and IMO
  that continues to be the case.  libinput is a much better choice of
  driver for this hardware (so is evdev for that matter), so I changed it
  to Driver "libinput" and got it working.  (Wayland uses libinput, so in
  a wayland session, touch already works fine in Qt apps on this
  hardware.)
  
  I'm one of the Qt Quick maintainers, most concerned with touch handling,
  and I've also written some of the Qt xcb code for dealing with XInput
  touch and tablet devices.  So if you think that there's something wrong
  with Qt, such that it should still work anyway to use a wacom driver for
  a Wacom touchscreen, let me know.  These AES devices are still new to me
  (that's why I got a Yoga, to try it out).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Summary changed:

- Wacom touchscreens should use libinput, not wacom driver
+ Wacom touchscreens should disable gestures

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to 

[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)

[Mariusz Dykierek]

** Package changed: ubuntu => usb-modeswitch (Ubuntu)

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

Title:
  usb_modeswitch does not switch modems (remain visible as mass storage)

Status in usb-modeswitch package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
  Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
  I have a strong feeling that it may either be related to Gnome or hardware.
  On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

  /var/log/usb_modeswitch.log ends with:
  Warning: SCSI attribute "ref" not readable.
  Check class of first interface ...
  Device is in istall mode.
  No access to interface 8. Exit

  Up until and including the "ref" not readable is exactly the same as on 
Kubuntu @ Dell.
  Yet on Kubuntu I get plenty of successful config logs after that and on 
Ubuntu @ Toshiba I don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+subscriptions

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Timo Aaltonen]

backporting the upstream commit to bionic

** Also affects: xf86-input-wacom (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: xf86-input-wacom (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: xf86-input-wacom (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Wacom touchscreens should disable gestures

Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom source package in Bionic:
  In Progress

Bug description:
  [Impact]

  From the original bug:

  "The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either."

  [Test case]

  Install the update, note that the touchscreen behaviour is better.

  [Regression potential]

  From the upstream commit:

  "Note that this change will effectively cause a feature regression for
  users of other environments that do *not* have their own gesture
  engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an
  xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the
  functionality."

  but at least I (tjaalton) haven't heard of any complaints since we've
  disabled gestures in focal (Nov 21st), so the warning might be a bit
  too pessimistic about the impact.

  
  --

  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1852691] Re: Disable touchscreen gesture

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1774242
   Wacom touchscreens should use libinput, not wacom driver

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

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 
1774242), the issue can be fixed by disabling in-driver gestures for 
touchscreens.

  Config file that instructs driver to disable in-driver gestures for 
touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
Identifier "Wacom touchscreen gestures"
MatchDriver "wacom"
MatchIsTouchscreen "true"
Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger 
zoom/rotate and 3+ finger gestures) work as desired. Also check 
/var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead 
libinput driver.

  [Regression Potential]
  Low

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

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

[Desktop-packages] [Bug 1866926] [NEW] usb_modeswitch does not switch modems (remain visible as mass storage)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading to Ubuntu focal fossa development branch the usb_modeswitch 
does not seem to work any more on a Toshiba laptop.
Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay 
like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from 
the terminal.
I have a strong feeling that it may either be related to Gnome or hardware.
On another Dell laptop with Kubuntu focal fossa development, both modems 
connect automatically.

/var/log/usb_modeswitch.log ends with:
Warning: SCSI attribute "ref" not readable.
Check class of first interface ...
Device is in istall mode.
No access to interface 8. Exit

Up until and including the "ref" not readable is exactly the same as on Kubuntu 
@ Dell.
Yet on Kubuntu I get plenty of successful config logs after that and on Ubuntu 
@ Toshiba I don't.

** Affects: usb-modeswitch (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
usb_modeswitch does not switch modems (remain visible as mass storage)
https://bugs.launchpad.net/bugs/1866926
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to usb-modeswitch 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 1852691] Re: Disable touchscreen gesture

[Bin Li]

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

Here is the original bug.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242

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

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 
1774242), the issue can be fixed by disabling in-driver gestures for 
touchscreens.

  Config file that instructs driver to disable in-driver gestures for 
touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
Identifier "Wacom touchscreen gestures"
MatchDriver "wacom"
MatchIsTouchscreen "true"
Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger 
zoom/rotate and 3+ finger gestures) work as desired. Also check 
/var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead 
libinput driver.

  [Regression Potential]
  Low

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

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Bin Li]

Timo,

 Could you help SRU into bionic? Thanks!

 Here is the SRU bug link. If we SRU at lp:1774242, I think I could
duplicate lp:1852691.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1852691

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom source package in Bionic:
  In Progress

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
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/xf86-input-wacom/+bug/1774242/+subscriptions

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

[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver

[Bin Li]

I tried the upstream patch on xserver-xorg-input-wacom 1:0.36.1-0ubuntu1
on 18.04, this issue is fixed.

commit 31a5405f7d9405bc514585709161287b0c67386e
Author: Jason Gerecke 
Date:   Mon Sep 9 15:32:17 2019 -0700

Change default gesture mode: touchpad=on, touchscreen=off

A large number of users run the GNOME desktop which has its own gesture
engine that performs actions on touchscreens. These gestures are much
better than the ones we provide, so lets disable our engine by default
for touchscreens. Note that GNOME doesn't do anything with touchpad
gestures, so we leave them enabled by default.

Note that this change will effectively cause a feature regression for
users of other environments that do *not* have their own gesture
engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an
xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the
functionality.

Signed-off-by: Jason Gerecke 


** Patch added: "change-default-gesture-mode.patch"
   
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+attachment/5335647/+files/change-default-gesture-mode.patch

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

Title:
  Wacom touchscreens should use libinput, not wacom driver

Status in xf86-input-wacom package in Ubuntu:
  Fix Released
Status in xf86-input-wacom source package in Bionic:
  In Progress

Bug description:
  /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  The result is that on my Yoga 920, in a plain X11 session (running
  openbox in my case), the touchscreen acts like a broken mouse: there
  is no multi-touch capability in Qt Quick applications, and clicking
  isn't quite right either.  I also verified it with Peter Hutterer's
  old cairo-based mt-touch test program.

  I suspect we will get some users mistakenly writing up Qt bugs about
  this if you don't ship a fix.  (Seems to me that already happened at
  least once, actually.)

  Yes, the touchscreen is made by Wacom, but wacom_drv.so has
  historically been only for Wacom tablets and in-screen stylus
  digitizers, and IMO that continues to be the case.  libinput is a much
  better choice of driver for this hardware (so is evdev for that
  matter), so I changed it to Driver "libinput" and got it working.
  (Wayland uses libinput, so in a wayland session, touch already works
  fine in Qt apps on this hardware.)

  I'm one of the Qt Quick maintainers, most concerned with touch
  handling, and I've also written some of the Qt xcb code for dealing
  with XInput touch and tablet devices.  So if you think that there's
  something wrong with Qt, such that it should still work anyway to use
  a wacom driver for a Wacom touchscreen, let me know.  These AES
  devices are still new to me (that's why I got a Yoga, to try it out).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: 
usr/share/X11/xorg.conf.d/70-wacom.conf]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 30 19:40:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  

[Desktop-packages] [Bug 1852691] Re: Disable touchscreen gesture

[Bin Li]

@Timo,

 I found the xserver-xorg-input-wacom-hwe-18.04 had this patch already.
But xserver-xorg-input-wacom didn't have, when I tried to upgrade
xserver-xorg-input-wacom-hwe, found it will remove the ubuntu-desktop
and old xserver-xorg-* packages.

 So do you have any idea how we fix this issue in OEM image? Thanks!

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

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 
1774242), the issue can be fixed by disabling in-driver gestures for 
touchscreens.

  Config file that instructs driver to disable in-driver gestures for 
touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
Identifier "Wacom touchscreen gestures"
MatchDriver "wacom"
MatchIsTouchscreen "true"
Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger 
zoom/rotate and 3+ finger gestures) work as desired. Also check 
/var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead 
libinput driver.

  [Regression Potential]
  Low

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

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

[Desktop-packages] [Bug 1852691] Re: Disable touchscreen gesture

[Bin Li]

Here is the patch.

** Patch added: "change-default-gesture-mode.patch"
   
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1852691/+attachment/5335639/+files/change-default-gesture-mode.patch

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

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 
1774242), the issue can be fixed by disabling in-driver gestures for 
touchscreens.

  Config file that instructs driver to disable in-driver gestures for 
touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
Identifier "Wacom touchscreen gestures"
MatchDriver "wacom"
MatchIsTouchscreen "true"
Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger 
zoom/rotate and 3+ finger gestures) work as desired. Also check 
/var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead 
libinput driver.

  [Regression Potential]
  Low

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

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